Re: [jetty-dev] Jetty 9 Context Deployer ??

--00151758850e664d8004d722191d
Content-Type: text/plain; charset=UTF-8

That make sense and works for us.   I guess it would be nice on the
downloads to have the release notes there too (for milestone and RC
versions too) so that we can see what changes are present and assess their
impact without having to download a release and install to see.

We do not use any of the supplied xml config files for the configuration of
jetty and make no changes to any file under the jetty tgz extract.
Rather, we have create own external jetty.xml config file containing what
we need from the "example" files in the install along with a customer
directory for the context deployer..   This means we are more exposed to
internal changes than the average user so seeing the deployer go was a
little shock.

Anyway, will go for version 8.1.9  now and look at a point release of
version 9 in 6 months.

Thanks


On 5 March 2013 02:57, Jesse McConnell <[email protected]> wrote:

> they were merged into one directory, so in the webapps directory you can
> place context xml files and webapps alike...
>
> directories that end in .d will not be actively deployed so you can have a
> context.xml point to stuff inside a dir like that safely....
>
> we did this to clear up the confusion we have had expressed regarding the
> split between contexts and webapps
>
> looking at the documentation I had thought this was all cleared up in the
> documentation already but apparently not...we need to get that done before
> release.
>
> anyway, the javadoc does explain it clearly:
> http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/deploy/providers/WebAppProvider.html
>
> cheers,
> jesse
>
> --
> jesse mcconnell
> [email protected]
>
>
> On Mon, Mar 4, 2013 at 4:48 AM, <[email protected]> wrote:
>
>> Just looked in to see if Jetty 9 was released yet and then had a quick
>> look at the RC2.
>>
>> Whaaa,  What happened to the context deployer?    Is there no longer
>> support for deploying via context xml files.  Is all the functionality that
>> was exposed in the context deployer still available by other means ?
>>
>> examples
>>
>>    - configuring session passivation on a per context basis
>>    - deploying a single war on multiple contexts (without duplicating
>>    the war).  (Don't ask, its legacy stuff).
>>
>> Thanks for any pointers / reasons ...
>>
>> David
>>
>>
>>
>>
>

--00151758850e664d8004d722191d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

That make sense and works for us.=C2=A0=C2=A0 I guess it would be nice on t=
he downloads to have the release notes there too (for milestone and RC vers=
ions too) so that we can see what changes are present and assess their impa=
ct without having to download a release and install to see.<br>

<br>We do not use any of the supplied xml config files for the configuratio=
n of jetty and make no changes to any file under the jetty tgz extract. =C2=
=A0 Rather, we have create own external jetty.xml config file containing wh=
at we need from the &quot;example&quot; files in the install along with a c=
ustomer directory for the context deployer..=C2=A0=C2=A0 This means we are =
more exposed to internal changes than the average user so seeing the deploy=
er go was a little shock.<br>

<br>Anyway, will go for version 8.1.9=C2=A0 now and look at a point release=
 of version 9 in 6 months.<br><br>Thanks<br><br><br><div class=3D"gmail_quo=
te">On 5 March 2013 02:57, Jesse McConnell <span dir=3D"ltr">&lt;<a href=3D=
"mailto:[email protected]" target=3D"_blank">jesse.mcconnell@gmail.=
com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">they were merged into one d=
irectory, so in the webapps directory you can place context xml files and w=
ebapps alike...<div>

<br></div><div>directories that end in .d will not be actively deployed so =
you can have a context.xml point to stuff inside a dir like that safely....=
</div>
<div><br></div><div>we did this to clear up the confusion we have had expre=
ssed regarding the split between contexts and webapps=C2=A0</div><div><br><=
/div><div>looking at the documentation I had thought this was all cleared u=
p in the documentation already but apparently not...we need to get that don=
e before release.</div>


<div><br></div><div>anyway, the javadoc does explain it clearly:=C2=A0<a hr=
ef=3D"http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/=
deploy/providers/WebAppProvider.html" target=3D"_blank">http://download.ecl=
ipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/deploy/providers/WebAppPr=
ovider.html</a></div>


<div><br></div><div>cheers,</div><div>jesse</div></div><div class=3D"gmail_=
extra"><br clear=3D"all"><div>--<br>jesse mcconnell<br><a href=3D"mailto:je=
[email protected]" target=3D"_blank">[email protected]</a></d=
iv>

<div><div>

<br><br><div class=3D"gmail_quote">On Mon, Mar 4, 2013 at 4:48 AM,  <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:[email protected]" target=3D"_blank">l=
[email protected]</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">


<div class=3D"gmail_quote">Just looked in to see if Jetty 9 was released ye=
t and then had a quick look at the RC2.<br><br>Whaaa,=C2=A0 What happened t=
o the context deployer?=C2=A0=C2=A0=C2=A0 Is there no longer support for de=
ploying via context xml files.=C2=A0 Is all the functionality that was expo=
sed in the context deployer still available by other means ?=C2=A0=C2=A0 <b=
r>



<br>examples<br><ul><li>configuring session passivation on a per context ba=
sis</li><li>deploying a single war on multiple contexts (without duplicatin=
g the war).=C2=A0 (Don&#39;t ask, its legacy stuff).<br></li></ul>Thanks fo=
r any pointers / reasons ...<br>



<br>David<br><br><br>
</div><br>
</blockquote></div><br></div></div></div>
</blockquote></div><br>

--00151758850e664d8004d722191d--