Hi, I just created an example and updated your issue: http://issues.ops4j.org/browse/PAXWEB-176
On Wed, Nov 25, 2009 at 11:50 AM, Stéphane Jeanjean < stephane.jeanj...@softeam.com> wrote: > Hi, > > Nobody has an idea where to put the jetty.xml file in the jar file to use a > new default configuration ? > > > Thanks, > > Stéphane > > Stéphane Jeanjean a écrit : > >> Hello, >> >> I try to find a way to configure Jetty. >> Do you think I can change the default Jetty configuration in the jar file >> ? When I try to open the pax-web-jetty-bundle-0.7.1.jar file, I can't find a >> jetty.xml configuration file :( Could I add such a file ? In which directory >> ? >> >> Thanks, >> >> Stéphane >> >> >> Stéphane Jeanjean a écrit : >> >>> >>> I tried to provision my fragment before pax web, the behaviour is the >>> same :( >>> I'm unable to change the state of the fragment, it keeps "Installed" >>> So I have created a jira issue ( >>> http://issues.ops4j.org/browse/PAXWEB-176 ) >>> >>> Alin Dreghiciu a écrit : >>> >>>> Did you tried to provision your jetty config fragment before pax web? I >>>> mean the order they are installed/started. >>>> >>>> If this doe snot work, create a jira issue for it and I wil handle this >>>> in a different way. I did not payed to much attention to this way of >>>> configuring jetty till now. It was contributed (thanks!) by community. >>>> >>>> On Thu, Oct 1, 2009 at 5:45 PM, Stéphane Jeanjean < >>>> stephane.jeanj...@softeam.com <mailto:stephane.jeanj...@softeam.com>> >>>> wrote: >>>> >>>> Hello, >>>> >>>> So, is there no way to configure Jetty with Felix today ? >>>> >>>> Stéphane >>>> >>>> >>>> Richard S. Hall a écrit : >>>> >>>> On 9/30/09 12:17, Stéphane Jeanjean wrote: >>>> >>>> Richard S. Hall a écrit : >>>> >>>> On 9/30/09 11:43, Stéphane Jeanjean wrote: >>>> >>>> Richard S. Hall a écrit : >>>> >>>> On 9/30/09 11:11, Filippo Diotalevi wrote: >>>> >>>> On Wed, Sep 30, 2009 at 11:01 AM, Stéphane >>>> Jeanjean >>>> <stephane.jeanj...@softeam.com >>>> <mailto:stephane.jeanj...@softeam.com>> >>>> wrote: >>>> >>>> With Pax Runner 1.2.0, so Felix 2.0.0, >>>> I have the same behaviour : it seems >>>> my jetty configuration is not used and >>>> I can see the log "configure using >>>> bundleresource://54/jetty.xml" >>>> >>>> I can see my Fragment in "ps" as >>>> Installed (as I can see it with the >>>> previous version) >>>> A log message is displayed >>>> "Auto-properties start: >>>> org.osgi.framework.BundleException: >>>> Fragment bundles can >>>> not be started." (as I can see it with >>>> the previous version) But I think >>>> it's normal. >>>> >>>> Hi, >>>> the message is normal (you cannot start >>>> a fragment), but the >>>> fragment should be Resolved (not just >>>> Installed). >>>> >>>> Can you try to force the fragment >>>> resolution ($ resolve<pid> ) to see >>>> if there's a problem with fragment >>>> dependencies? >>>> >>>> >>>> Make sure the host isn't already resolved >>>> before trying to resolve the fragment too, >>>> since if it is then it won't be possible to >>>> resolve the fragment. >>>> >>>> When I try to resolve it with "resolve pid" in the >>>> console, it seems that nothing happens (no >>>> message). The state in "ps" keeps to "Installed". >>>> What do you mean by "host isn't already resolved", >>>> which host we are talking about ? >>>> >>>> >>>> The host to which the fragment will attach. If its >>>> host is already resolved, then it cannot attach to it. >>>> It seems like it should print a message in that case... >>>> >>>> >>>> When I type "resolve pid" using the shell, Pax web state >>>> is "Active" >>>> >>>> Pax web is started automatically because I'm using web >>>> profile through pax runner. So perhaps when my fragment is >>>> deployed using deployURLs option, Pax Web is already started >>>> ? >>>> >>>> >>>> That is quite possibly the issue. It needs to be installed >>>> before Pax Web is resolved. >>>> >>>> I believe Equinox supports dynamic attachment of fragments, >>>> but this isn't required by the spec I believe, so relying on >>>> it is non-portable. Even then, dynamic attachment is more >>>> restricted than resolve-time attachment, so it still doesn't >>>> work in all situations that resolve-time attachment does. >>>> >>>> -> richard >>>> >>>> >>>> Stéphane >>>> >>>> _______________________________________________ >>>> general mailing list >>>> general@lists.ops4j.org <mailto:general@lists.ops4j.org> >>>> http://lists.ops4j.org/mailman/listinfo/general >>>> >>>> >>>> _______________________________________________ >>>> general mailing list >>>> general@lists.ops4j.org <mailto:general@lists.ops4j.org> >>>> http://lists.ops4j.org/mailman/listinfo/general >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> general mailing list >>>> general@lists.ops4j.org <mailto:general@lists.ops4j.org> >>>> http://lists.ops4j.org/mailman/listinfo/general >>>> >>>> >>>> >>>> >>>> -- >>>> Alin Dreghiciu >>>> Software Developer >>>> 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 >>>> >>>> >>> >>> >>> >> >> > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > -- Alin Dreghiciu Software Developer My profile: http://www.linkedin.com/in/alindreghiciu My blog: http://adreghiciu.wordpress.com http://sonatype.com - Sonatype - The Maven Company 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
