Hi Chamikara, My suggestion is to keep the RampartSecurityManagerImpl as an extension to Sandesha but in the same source tree and exclude it in the normal build. We can provide a build option which build the above class, for which it will download the rampart.jar.
May be I also did I not understand the problem correctly :)? -Jaliya ----- Original Message ----- From: Chamikara Jayalath To: [EMAIL PROTECTED] Cc: [email protected] ; [EMAIL PROTECTED] ; [email protected] Sent: Friday, January 19, 2007 8:57 PM Subject: Re: Decoupling releases from sandesha and rampart Hi Dims, Sorry think I wasnt clear previously. It is exactly the way we do it. But we still have that RampartSecurityManagerImpl within the Sandesha2 source folder. So we need the Rampart jar to build it (not to run Sandesha2). Making Sandesha2 a multi-module project and making RampartExtention a module could be a solution (so that we could do a seperate release of it). Or else if there a better way to do it in Maven2 (if so we can shift to Maven2). Chamikara On 1/19/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote: Keep it in Sandesha2 but rewrite it using Java reflection to make the rampart calls :) -- dims On 1/19/07, Chamikara Jayalath <[EMAIL PROTECTED]> wrote: > Hi Dims, Paul, > > Actually thats the way we do it currently. We hv the SecurityManager > interface and RampartSecurityManager is just an implementation of it, which > get loaded through reflection. > > The only problem is where to put this class. Currently it is in Sandesha2 > codebase and thats why we hv the dependancy for Rampart. > > Chamikara > > > > > On 1/19/07, Davanum Srinivas < [EMAIL PROTECTED]> wrote: > > > > Oops! Wrong mailing list :) > > > > On 1/19/07, Davanum Srinivas <[EMAIL PROTECTED] > wrote: > > > Paul, > > > > > > Suppose we introduce a class in Sandesha which is in charge of calling > > > rampart code and ensure that class uses pure java reflection to > > > load/call rampart code. Will that be enough? Yes, we could still use > > > versions of rampart in testing but not ship it in the dist. We could > > > also add in our documentation which rampart version(s) we support. > > > > > > thanks, > > > dims > > > > > > On 1/19/07, Paul Fremantle <[EMAIL PROTECTED]> wrote: > > > > A while back Sanjiva suggested we don't ship sandesha2 and rampart > > > > directly with Synapse. I think coming up to our 1.0 release that will > > > > be essential. There are some key changes in Sandesha2 (for example) > > > > that I'd like to incorporate, but at the same time I don't want to > > > > wait until Sandesha2 1.2 releases. > > > > > > > > If we can decouple the RM and WSS support then I think we can be more > > > > flexible with our releases. > > > > > > > > At the same time, we should make sure that we dont compromise > > > > usability. In order to make this still work, we need to just be able > > > > to drop an extension JAR plus the MAR into the right places. > > > > > > > > Paul > > > > > > > > -- > > > > Paul Fremantle > > > > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair > > > > > > > > http://bloglines.com/blog/paulfremantle > > > > [EMAIL PROTECTED] > > > > > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > -- > > > Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service > Developers) > > > > > > > > > -- > > Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
