Before to speak about a solution, maybe it could be more interesting to extend one of the example that we have to validate that we can support all the vaadin features on OSGI and next we could propose something using or not blueprint. I will work to extend the SimpleApplication to use theme, add-on based on code coming from the book ( http://demo.vaadin.com/book-examples/book)
On Sun, Nov 11, 2012 at 9:23 PM, Achim Nierbeck <bcanh...@googlemail.com>wrote: > Yeah, wouldn't have thought so, either the web-extender or pax-for-vaadin > need to take action on it, both wouldn't work > Though it might be possible to use the web-parser for parsing a web.xml > which might be available "somewhere" in the class path. > > Just an idea I'm gonna try next. > > Besides that I kind of start liking the blueprint idea actually even > better, cause that way we can go for the configuration much easier. > > > regards, Achim > > > 2012/11/11 Charles Moulliard <ch0...@gmail.com> > >> Made some tests last friday successfully but combining a web.xml file >> with solution developed for pax-vaadin is certainly not the way to go >> >> >> On Sat, Nov 10, 2012 at 10:32 PM, Achim Nierbeck <bcanh...@googlemail.com >> > wrote: >> >>> This depends on if the Manifest is containing the right "markers" >>> >>> as you can see in the activator [1], the bundlescanner looks for >>> Webapp-root >>> So if the Manifest contains this entry it's considered to be a web >>> application. >>> >>> regards, Achim >>> >>> [1] - >>> https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-extender-war/src/main/java/org/ops4j/pax/web/extender/war/internal/Activator.java#L135 >>> >>> >>> 2012/11/9 Charles Moulliard <ch0...@gmail.com> >>> >>>> Hi, >>>> >>>> Does anybody knows if WebXmlObserver will also work if we deploy a >>>> bundle (not a WAR) containing a web.xml file under WEB-INF ? >>>> >>>> Regards, >>>> >>>> -- >>>> Charles Moulliard >>>> Apache Committer / Sr. Enterprise Architect (RedHat) >>>> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com >>>> >>>> >>>> >>>> _______________________________________________ >>>> general mailing list >>>> general@lists.ops4j.org >>>> http://lists.ops4j.org/mailman/listinfo/general >>>> >>>> >>> >>> >>> -- >>> >>> Apache Karaf <http://karaf.apache.org/> Committer & PMC >>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer >>> & Project Lead >>> OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> >>> Commiter & Project Lead >>> blog <http://notizblog.nierbeck.de/> >>> >>> _______________________________________________ >>> general mailing list >>> general@lists.ops4j.org >>> http://lists.ops4j.org/mailman/listinfo/general >>> >>> >> >> >> -- >> Charles Moulliard >> Apache Committer / Sr. Enterprise Architect (RedHat) >> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com >> >> >> >> _______________________________________________ >> general mailing list >> general@lists.ops4j.org >> http://lists.ops4j.org/mailman/listinfo/general >> >> > > > -- > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & > Project Lead > OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> > Commiter & Project Lead > blog <http://notizblog.nierbeck.de/> > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > > -- Charles Moulliard Apache Committer / Sr. Enterprise Architect (RedHat) Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
