Can Slices be used with M5? If not, how soon?
Can Slices be used with M5? If not, how soon?
Thanks
Dmitry
I found dms-m5 branch and that thing just worked!
If anyone is interested:
1. pull down and build dms-m5 branch from slices repo
2. build itCode:git checkout --track -b branch dms-m5 origin/dms-m5
3. modify $SERVER/config/com.springsource.kernel.propertiesCode:cd build-slices ant clean jar package
4. start dm ServerCode:#deployer.systemArtifacts= repository:plan/com.springsource.server.web deployer.systemArtifacts= repository:plan/com.springsource.server.web,repository:plan/com.springsource.osgi.slices
I ended up testing this with a petclinic sample app. To build that I had to add
in /samples/slices-petclinic/com.springsource.slices.petclinic.host/ivy.xmlCode:<dependency org="org.eclipse.osgi" name="org.eclipse.osgi" rev="${org.eclipse.osgi}" conf="compile->compile"/>
Will follow up if I see issues with my own apps.
Last edited by dsklyut; Oct 14th, 2009 at 09:53 PM.
Thanks
Dmitry
Further observations:
Application configured in a scoped plan with a host webapp and 1 slice, does not deploy right now.
Looks like slices deployer is not used to deploy a slice, but a regular web-app deployer is. Seeing msg in console:
Looks like manifest entries for slices are not picked up.Code:[2009-10-14 11:24:02.698] Thread-2 <WE0000I> Starting web bundle '****plan-1.1.0.DEV-SNAPSHOT-****.web' context path '/****.web-1.1.0.DEV-SNAPSHOT'.
I guess just dropping a slice plan into pickup is not enough.
Thanks
Dmitry
Dmitry, first of all, I should say thank you for trying this out on M5: you've pretty much written my blog post on how to use Slices on M5 for me!
Using a Slice from within a scoped plan should work. If it doesn't, then it sounds like you found a bug. Apologies for that. My guess would be that it's the scoping logic that's causing the problem. Does it work for you if the plan is not scoped?
Andy Wilkinson
SpringSource
A little further research:
1. Transformer ordering is not correct (I think).
SliceTransformer is executed before PlanResolver. So I bumped ranking of SliceTransformer by 1.
2. There is still an issue described in http://forum.springsource.org/showthread.php?t=74704.
Matching host bundle name to bundle.symbolicName is broke again.
Last edited by dsklyut; Oct 16th, 2009 at 12:15 PM.
Thanks
Dmitry