> The reason Rampart jars need to go in to Axis2 lib is the Sun Service > Provider Interface problem. rampart-core.jar and rampart-policy.jar > registers some assertion builders using Sun SPI and those builders to be > used by neethi factory classes they should be in the classpath of those > neethi classes. So the only solution we have right now is to put those two > jars in the Axis2 lib. Actually we only need those two jars (not the third > party jars) to be in the Axis2 lib and rampart-trust.jar and other third > party jars can be bundled in the module itself. Can this be solved by OSGi ? > ( With the very little knowledge OGSi bundle classpath resolution and bundle > wiring , I couldn't figure out how to do this :( ) > > Yes it is.
Thank you! Saminda ps: wouldn't wss4j needed to be in root lib as well. -- Saminda Abeyruwan Senior Software Engineer WSO2 Inc. - www.wso2.org
