Comments on: Announcing dm Server 2.0 M1

By: SpringSource dm Server Admin Console | SpringSource Team Blog

SpringSource dm Server Admin Console | SpringSource Team Blog — Fri, 24 Jul 2009 12:30:16 +0000

[...] dm Server Admin Console are available in the nightly builds. This also shows the use of Plans and the RFC66 Web container. There are two new features available, the first lets you look at any [...]

By: dm Server Repository Content via JMX | SpringSource Team Blog

dm Server Repository Content via JMX | SpringSource Team Blog — Mon, 22 Jun 2009 10:59:47 +0000

[...] on June 22nd, 2009 by Ben Hale in OSGi, dm Server. In the dm Server 2.0.0.M1 release we added support for shared repositories. As a followup to this new functionality, we've added [...]

By: Cloning in dm Server 2.0 M3 | SpringSource Team Blog

Cloning in dm Server 2.0 M3 | SpringSource Team Blog — Wed, 10 Jun 2009 15:20:46 +0000

[...] support for cloning in dm Server has progresses steadily over the last few sprints. The fundamental mechanisms were in place in M1: cloning may be [...]

By: Vorstellung des SpringSource dm Server | Von Tino Schmidt | Beitrag | Communardo Techblog

Thu, 09 Apr 2009 22:38:03 +0000

[...] Der Spring Source dm Server steht ab sofort in der Version 2.0 M1 zum Download zur [...]

By: Pierre-Henry

Pierre-Henry — Wed, 08 Apr 2009 08:29:59 +0000

I've run the test on kernel-build with ANT_OPTS='-Xmx512m -XX:MaxPermSize=512m' because there was a PermGen error.
There is one TestCase that fails:

Testcase: com.springsource.kernel.ffdc.test.FFDCServiceAspectTests:

A file not found error.

By: Chuck

Chuck — Mon, 06 Apr 2009 18:51:20 +0000

I think you guys are doing great work. I was wondering if you could provide a little more support for non-eclipse users that can't use the Spring tools by providing more documentation around implementing that same functionality outside of that environment. Worse case, can we get docs without numerous pages of eclipse screenshots. Thanks.

By: Rob Harrop

Rob Harrop — Mon, 06 Apr 2009 08:46:36 +0000

@Jaro

The biggest improvement is in the implementation. OSGi 4.2 introduces some service registry hooks that we now use to implement the scoping. Previously, we rewrote the Spring DM configuration files. The rewriting approach doesn't catch programmatic service usage and is a bit of a pain in general.

I also added some internal code to support punching through a scope when you really want to. This isn't complete yet, but once I get the semantics sorted out I'll get that fully documented.

Rob

By: Jaro

Jaro — Fri, 03 Apr 2009 07:43:32 +0000

Rob, can you post more details about service scoping improvements you have mentioned? Thanks.

By: Ben Hale

Ben Hale — Fri, 03 Apr 2009 05:42:30 +0000

@Robert,

I've updated the permissions on the dm Server project so you should now be able to open issues. I've also opened issue https://issuetracker.springsource.com/browse/DMS-456 with your problem. Thanks for the feedback.

By: Robert Beeger

Robert Beeger — Thu, 02 Apr 2009 21:15:30 +0000

Hi,

I created an account at your Jira, but somehow I'm not allowed to create new issues for dm Server.

So I'll post my bug report here:
Spring DM Server 2 M1 does not work on a German Windows XP. Running startup.bat only results in an error message complaining that read access to jmxremote.password should be restricted.
Changing
echo y|cacls %CONFIG_DIR%\management\jmxremote.* /P %USERNAME%:F > nul
to
echo j|cacls %CONFIG_DIR%\management\jmxremote.* /P %USERNAME%:F > nul
fixes the problem

Note the "j" for "Ja" instead of "y" for "Yes".

Best regards,
Robert