Re: [jetty-user] Jetty 8.0

Hi Jan,

Thanks for the quick response. I've been looking at documentation but not of it applied to my particular deployment requirements and I hadn't run into these pages so thanks for the links. The later one looks particularly useful.
On 2012-02-28, at 6:27 AM, Jan Bartel wrote:

> 
> 
> Having said that, checking the code, if you want to supply the xml
> files on the command line, then they have to be an absolute path, or
> else jetty will try to find the relative path inside $jetty.home. Not
> sure at this point if that's a difference between 6 and 7/8, but it
> seems that is your stumbling block.

With 6 start.jar read the jetty.xml file supplied without munging in the $jetty.home setting so this is a difference between 6 and 8.

What forced the move is that 6.1.24 is that I ran into a JNDI bug. Fixed in later version of 6 introduced a bottleneck on access log logging. That motivated the move to 8 but unless I can generate a work-around, this will be a complete show-stopper.

> 
> cheers
> Jan
> 
> On 28 February 2012 15:18, Kirk Pepperdine <[email protected]> wrote:
>> Hi,
>> 
>> I'm trying to upgrade from Jetty 6.1.28 to the most recent release of 8.0. I've been trying to start the server with same layout as I used with the 6.1.* version where the jetty configuration used it separate from the install. For some reason, Jetty 8 can't find the config file. I'm not seeing anything in the documentation that suggests the startup mechanism has changed so I'm wondering what I'm missing. Hardcoding the path to jetty.xml gets past this issue but isn't an option in the intended deployment environments. Trying to sort out what has changed and what I'm missing.
>> 
>> Here is the cmd line. (OSX but Linux and Windows will also be used).
>> 
>> java -Djetty.home=../bin/jetty-distribution-8.1.1.v20120215 -jar ../bin/jetty-distribution-8.1.1.v20120215/start.jar jetty/etc/jetty.xml
>> java.io.FileNotFoundException: Unable to find XML Config: jetty/etc/jetty.xml
>>        at org.eclipse.jetty.start.Main.resolveXmlConfig(Main.java:661)
>> 
>> Regards,
>> Kirk
>> 
>> 
>> On 2012-02-28, at 2:46 AM, Hugues Malphettes wrote:
>> 
>>> Hi Petr and Jesse,
>>> 
>>> In fact one of the aggregate "jetty-all-server" is OSGi-abled. Dmytro
>>> requested and assisted us with it.
>>> Here is the bug where the work was done:
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=317222
>>> 
>>> I am not sure where the import for org.mortbay would come.
>>> Please let us know if we need to change something in the build of
>>> "jetty-all-server" to fix it or accommodate your situation.
>>> 
>>> Cheers,
>>> Hugues.
>>> 
>>> On Mon, Feb 27, 2012 at 10:14 PM, Jesse McConnell
>>> <[email protected]> wrote:
>>>> if you are close with your approach I don't see it being a bad thing
>>>> 
>>>> I had thought the aggregates were 'close' for osgi and were being
>>>> adjusted for supporting that, at least at some point in their history
>>>> they were
>>>> 
>>>> since your trying to generate a large bundle of your own then I would
>>>> probably look at using the same sort of dependency setup as the
>>>> aggregate pom and roll your own manifest, no reason that wouldn't work
>>>> 
>>>> it will be 'un-osgi' but that isn't necessarily a bad thing :)
>>>> 
>>>> cheers,
>>>> jesse
>>>> 
>>>> --
>>>> jesse mcconnell
>>>> [email protected]
>>>> 
>>>> 
>>>> 
>>>> On Mon, Feb 27, 2012 at 08:07, Peter Nerg <[email protected]> wrote:
>>>>> Really!
>>>>> 
>>>>> That's odd, if I install the aggregate and a few other bundles into Felix
>>>>> and then add my own bundle it simply works...:)
>>>>> 
>>>>> However when putting the jetty bundle + a few others into my own bundle it
>>>>> fails.
>>>>> 
>>>>> Anyways I'll drop that track and take a look at the "proper" OSGi bundles
>>>>> for Jetty.
>>>>> That's what I get for trying to save time with one big happy binary..:(
>>>>> 
>>>>> --
>>>>> View this message in context: http://jetty.4.n6.nabble.com/Fail-to-embed-Jetty-in-a-bundle-tp4514503p4514912.html
>>>>> Sent from the Jetty Support mailing list archive at Nabble.com.
>>>>> 
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe from this list, please visit:
>>>>> 
>>>>>    http://xircles.codehaus.org/manage_email
>>>>> 
>>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe from this list, please visit:
>>>> 
>>>>    http://xircles.codehaus.org/manage_email
>>>> 
>>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>> 
>>>    http://xircles.codehaus.org/manage_email
>>> 
>>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>> 
>>    http://xircles.codehaus.org/manage_email
>> 
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>    http://xircles.codehaus.org/manage_email
> 
> 


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email