I managed to get this working yesterday. What I did was write a SharedHttpContext that contained a map of the HttpContexts that belonged to each bundle. These were then checked against in the SharedHttpContext that was registered across the bundles. I did have to remove the exception that was being throw in ServerModel.associateHttpContext.
I used the extender-whiteboard bundle for my registrations. I'll create a jira for this now. I would be happy to contribute this. Regarding the exception that is being throw, would it be best to keep it and just check for an instance of SharedHttpContext or should it be removed totally? Thanks, Dave > Neither could I see this request in the JIRA. Dave, could you file a JIRA > issue for it so that we remember it. > > On Thu, May 14, 2009 at 2:34 AM, Alin Dreghiciu > <adreghi...@gmail.com>wrote: > >> No, it wasn't. On a long run I'm planning to support composite web >> applications out of more bundles. But I do not make any promise ;) >> >> >> On Wed, May 13, 2009 at 12:57 AM, David Conde >> <i...@javadeveloper.eu>wrote: >> >>> I'm currently in a similar situation in that I need to be able to >>> access >>> JSP's and sessions in different bundles. Was this ever implemented in >>> the >>> pax-web-extender-whiteboard bundle? >>> >>> Thanks, >>> Dave >>> >>> >>> >>> Alin Dreghiciu >>>> Mon, 10 Mar 2008 12:55:35 -0700 >>>> >>> >Sriram, >>> > >>> >In my view the answer is in the message you replayed to. An >>> >extender/whiteboard bundle will do the trick for your requirements. As >>> >I see there is a request for such a feature and can be a good addition >>> >to pax extender "family". So, why don't you start to implement it >>> >under Pax umbrella? I'm pretty much busy right now with some other >>> >requirements so I cannot do it right away but I can "help" if >>> >necessary. And here here can be at least two approaches: >>> > >>> >1. Using an white board pattern as pax web extender whiteboard and >>> >then based on the context id (already in place) share the http context >>> >between the bundle. You can start from the current code by allowing >>> >bundles to share the context by id and changing HttpContextProxy in >>> >order to use all the bundles/registered context. >>> > >>> >2. For the ones that do not want to use the whiteboard approach and >>> >want to use something similar to HttpService approach you can have a >>> >kind of proxy bundle that registers a service with the same interface >>> >as HttpService/WebContainer (from pax web) and act as a composite >>> >service. >>> > >>> >So, when do you start? :) >>> > >>> >Alin >>> >>> _______________________________________________ >>> general mailing list >>> general@lists.ops4j.org >>> http://lists.ops4j.org/mailman/listinfo/general >>> >> >> >> >> -- >> Alin Dreghiciu >> Software Developer - Looking for new projects! >> My profile: http://www.linkedin.com/in/alindreghiciu >> My blog: http://adreghiciu.blogspot.com >> http://www.ops4j.org - New Energy for OSS Communities - Open >> Participation >> Software. >> http://www.qi4j.org - New Energy for Java - Domain Driven Development. >> >> _______________________________________________ >> general mailing list >> general@lists.ops4j.org >> http://lists.ops4j.org/mailman/listinfo/general >> >> > > > -- > -- > Thanks and Regards, > /Thomas Joseph > > LinkedIn: http://www.linkedin.com/in/ethomasjoseph > Twitter: http://twitter.com/ethomasjoseph > Blog: http://openthoughtworks.blogspot.com > > ------------------------------------------------------------ > Promote Open Source - Promote Liberty of Ideas and Software. > ------------------------------------------------------------ > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
