Major upgrade

[fspinazzi]

The issues reported here in the forum should now be fixed:
- SPRNET-227 has been closed (see http://opensource2.atlassian.com/projects/spring/browse/SPRNET-227)
Check the docs for changes (no more service.xml file but service.config instead...)

Please let me know (better on the developer list)

[erijvordt]

Great & thanks,

I have tried to get the latest version from CVS last week, but I still get some antlr error when building the release version. Besides that, we're about to go live with the current project, so I don't want to switch to the new version yet.

One other question I have about the new configuration (and the old): in my current service.xml I do some <import resource="..."/> calls to include e.g. my business object definitions (same files as are used in Web.config). Now I have to specify absolute file:// paths here, and cannot use properties from a PropertyPlaceholderConfigurer. Is it now possible to use relative paths in <import>? If not, what can be done to perform property substitution in the resource attribute of <import>?

Thanks again,
Edwin

[fspinazzi]

in service.xml try

<import resource="file://~/objects.xml"/>

The ~ character will be expanded to tha base directory of the current AppDomain.

Given tha usual setup for your service, in the above example objects.xml will be searched in the same directory of service.xml

This is a general feature of <import/> and NOT one specific to windows service

[Mark Pollack]

Hi Edwin,

The ANTLR error is most likely related to the fact that the antlr.runtime.dll is not a strongly signed assembly. I have contacted the ANTLR folks to see if they will provide one. We will have this done, one way or another, before the next release.

Cheers,
Mark