Regarding this really nifty batch file that creates a springDM project: You still have a little coding to do, but it works great! http://www.ops4j.org/projects/pax/construct/examples/spring-osgi.html
What is really cool is you can see your service running even before using pax-exam, just type in services at the osgi> prompt Then, Maven3 broke the above batch file, so you have to employ this workaround by moving some xml around if you want to use Maven3: http://issues.ops4j.org/browse/PAXCONSTRUCT-128 What I am finding is that projects created with the Maven 2 and this batch file (and with the above workaround done anyway! ) work great, even when run later with Maven3. However, the same projects created with Maven 3 and this batch file (and the above workaround done properly) never allows the spring service to launch. I have repeated this several times with fresh artifacts just to make sure, it always seems to work - or not - the same way. Is this a familiar and expected result? It is a very sneaky bug because it leaves no traces of errors that I can find, it just doesn't work at runtime, after the artifacts are created, apparently without error. Comments? Suggestions? This actually may be a huge breakthrough for me, because I've been trying to use Maven3 (m2eclipse) for months, and never knowing why it didn't work at runtime. But a fix would be very helpful. _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
