I've created a small blog application to test out Spring DM server. For now, I've created three bundles: resources (datasources, etc), core (domain model classes, DAO's and utility classes) and services (business logic). I'll be adding a fourth bundle, a web app which will use the services bundle to manage the blog.
I ran into the problem mentioned in thread 206103 (sorry, the forum won't let me post the url) around bundle package cross-references and followed the advice to create a par project referencing all three bundles. The referencing issue went away - but now I have another problem.
It seems that the startup order for the bundles is critical in that if I deploy them individually & manually in the correct order (resources, core, services) everything works fine. If I simply deploy the par project the resources bundle starts up OK but the other two bundles fail to deploy after timing out waiting for mandatory references from the first bundle.
The puzzling part is that if I telnet in to the container and check the first bundle, it has started correctly and all the required services appear to be registered. So, even if "resources" is the last bundle to start, why don't the other two bundles see the first and resolve their references?
I've had a similar problem exporting a transaction manager service from a bundle. Other bundles look for an instance of PlatformTransactionManager which never seems to resolve despite the fact that telnetting in to the container shows that the service is available under the specified interface.
I'm not sure whether this is related to the startup order of the bundles or is something class related (as I've only had the problem with certain classes/interfaces).
Any ideas anyone?