dm Server 2.0 M2

Posted on May 19th, 2009 by Andy Wilkinson in OSGi, Open Source, dm Server.

Andy Wilkinson

dm Server 2.0.0.M2 has been released, and is now available for download. In the two sprints since 2.0.0.M1, we've made significant progress towards the final release, both in terms of new features, and in defect fixes. Take a look at the M2 release notes if you're interested in seeing everything that we've been working on. Please keep your feedback coming as comments on our blog, in the forums, and on JIRA.

New and noteworthy

Spring 3 support

In the milestone, we've upgraded dm Server to run on Spring 3. As we move towards the final release of dm Server 2.0, we'll be upgrading the version of Spring 3 as new milestones and snapshots become available.

Improvements to cloning

We've made some significant improvements in our support for auto-cloning. For example, you can now run Spring 2.5.6 and Spring 3-based applications side-by-side in the same dm Server.

Watched repositories

Support for watched repositories has been added. A watched repository is configured to watch a directory on your filesystem and, as artifacts are added to the directory, they will become available to dm Server's provisioning system. Equally, as artifacts are removed from the directory, they will no longer be available to dm Server's provisioning system.

Here's some example configuration for a watched repository:

"watched-repo" : {
    "type" : "watched",
    "watchDirectory" : "repository/watched",
    "watchInterval" : 5
}

Similar Posts

Share this Post
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • DZone
  • LinkedIn
  • Slashdot
  • Technorati
  • TwitThis
 

7 responses

  1. Anoop says:

    Added on May 22nd, 2009 at 5:08 am

    Is there a sample for a web module that exposes a "HelloWorld" RESTFUL webservice (Spring 3.0) for Spring DM Server 2.0 M2 ?

  2. Andy Wilkinson (blog author) says:

    Added on May 27th, 2009 at 5:42 am

    Take a look at Alef's blog post that includes links to a sample application that creates a RESTful service. Whilst this application is packaged as a WAR file, it should work just fine on dm Server 2. You could then look to update the app, e.g. to use shared libraries, rather than packaging all of its dependencies in WEB-INF/lib.

    Let us know on the forums (http://forum.springsource.org/forumdisplay.php?f=53) if you have any problems.

  3. Anoop says:

    Added on May 27th, 2009 at 7:49 am

    We were able to get HelloWorld RESTFUL webservice to work, lack of experience with entries to be made in manifest was the problem.

  4. shashikumar says:

    Added on August 18th, 2009 at 7:09 am

    C:\springsource-dm-server\bin>startup
    The system cannot find the path specified.
    C:\springsource-dm-server\bin\jmxPermissions.vbs(63, 2) SWbemObject: Type mismatch

  5. jeremy says:

    Added on November 26th, 2009 at 12:59 pm

    Hi, I'm trying to migrate a web module to a web bundle for dm-server 2.0, but with no success. I'm currently packaging the bundle as a jar, but when I depoly to the server there is no web context for the bundle. Is there an example/tutorial of a web bundle, including the correct packaging (e.g. jar/war)?

  6. Andy Wilkinson (blog author) says:

    Added on November 27th, 2009 at 6:28 am

    @Jeremy, It's pretty much WAR format in 2.0. Take a look at one of the samples, FormTags is probably the best one to start with.

  7. jeremy says:

    Added on December 2nd, 2009 at 7:03 am

    Hi Andy,
    Thanks for the pointer, this led me to take the following steps:

    1) Change the Web Bundle Packaging to War in the POM.

    2) I also followed the dm-server 2.x programmer guide for: "Migrating to a Web bundle from a Web Module". So removing obsolete manifest headers from the template.mf, and modifying the web.xml.

    One step not mentioned in the programmer guide was I had to configure in ServerOsgiBundleXmlWebApplicationContext, and ContextLoaderListener in the web.xml.

    3) Finally any dependency artifacts, which we are creating had to be scoped to "provided".

    Thanks again,

    Jeremy.

Leave a Reply