sorry for the confusion, but the jetty.xml file that i used --
JBoss-2.4.3_Jetty-3.1.1-1/jboss/conf/jetty/jetty.xml -- was pasted (in its
entirety) in the email. i _was not_ using at all the default jetty.xml file.
i replaced the distro jetty.xml with my own, that contained two nodes: an
addWebApplication node for my .war file, and an addListener node to set up
the listener on port 8080.
when the addWebApplication node was commented out (leaving only the
addListener node), the .war file was deployed properly and my java:comp/env
entries were available.
when the addWebApplication node was *not* commented out, the .war was
deployed properly, but the java:comp/env entries were absent.
this happens even when i deploy it onto a fresh install of
JBoss-2.4.3_Jetty-3.1.1-1.
to clarify all this, i've put together a sample .war file (attached, with
source code for servlet also) which, on a fresh install of 2.4.3/3.1.1-1
works (i.e. java:comp/env entries exist) with no modifications to
jetty/jetty.xml by hitting:
http://localhost:8080/systemdump/system
but no java:comp/env entries exist when i add an addWebApplication node to
jetty/jetty.xml (attached also), as such:
<Call name="addWebApplication">
<Arg>/systemdump/*</Arg>
<Arg>C:/JBoss-2.4.3_Jetty-3.1.1-1/jboss/deploy/systemdump.war</Arg>
<Arg><SystemProperty name="jetty.home"
default="."/>/etc/webdefault.xml</Arg>
<Arg type="boolean">true</Arg>
</Call>
is this a bug? or should one simply not add a jetty.xml entry for
webapplications when running jetty in conjunction with jboss (actually, it
seems to work fine when that is the case!)?
thanks a lot!
--e--
On Thu, 4 Oct 2001 15:57:07 +0100 (BST), Julian Gosnell wrote:
>Edward,
>
>If you look at
>
>JBoss-2.4.3_Jetty-3.1.1-1/jboss/conf/jetty/jetty.xml
>
>(perhaps you were looking at
>jboss/conf/default/jetty.xml - this is not used and I
>should remove it).
>
>you will find all these entries have now been
>commented out.
>
>I used to ship JBoss/Jetty with the Jetty demo webapps
>and servlets ready installed, but then recently I
>realised that this may interfere with deployment of a
>users webapps and be confusing (especially apps being
>deployed into the '/' context).
>
>Look again at the latest release. I will be surprised
>if:
>
>1. The demo stuff is not commented out in your
>jetty.xml.
>
>2. Deployment onto a vanilla installation gives you
>the same problem again.
>
>Cheers,
>
>
>Jules
>
>
>
> --- "Edward Q. Bridges" <[EMAIL PROTECTED]> wrote:
>>
>> after some poking around, it turns out that the
>> problem is with
>> $JBOSS_HOME/conf/jetty/jetty.xml
>>
>> here is the entire file:
>>
>> <?xml version="1.0" encoding="ISO-8859-1"?>
>> <!DOCTYPE Configure PUBLIC "-//Mort Bay
>> Consulting//DTD Configure 1.1//EN"
>> "http://jetty.mortbay.com/configure_1_1.dtd";>
>>
>> <Configure class="org.mortbay.http.HttpServer">
>> <Call name="addListener">
>> <Arg>
>> <New class="org.mortbay.http.SocketListener">
>> <Set name="Port">8080</Set>
>> <Set name="MinThreads">5</Set>
>> <Set name="MaxThreads">255</Set>
>> <Set name="MaxIdleTimeMs">60000</Set>
>> <Set name="MaxReadTimeMs">60000</Set>
>> </New>
>> </Arg>
>> </Call>
>>
>> <Call name="addWebApplication">
>> <Arg>/pix/*</Arg>
>>
>>
><Arg>C:/JBoss-2.4.1_Jetty-3.1.RC9-1/jboss/deploy/pix.war</Arg>
>> <Arg><SystemProperty name="jetty.home"
>> default="."/>/etc/webdefault.xml</Arg>
>> <Arg type="boolean">true</Arg>
>> </Call>
>>
>> </Configure>
>>
>> The problem seems to come from the call to
>> addWebApplication. when that is
>> present, and i deploy to
>> $JBOSS_HOME/deploy/<mywarfile>, then java:comp/env
>> entries specified in WEB-INF/web.xml don't get
>> created. when i comment it
>> out, they do get created.
>>
>> this also happens with the JBoss-2.4.3_Jetty-3.1.1-1
>> distro.
>>
>> is this a problem? or should it just be part of
>> configuring a .war to use
>> with jboss/jetty that there is no need to edit the
>> jetty.xml file?
>>
>> thanks
>> --e--
>>
>>
>> On Tue, 02 Oct 2001 23:44:11 +0100, Julian Gosnell
>> wrote:
>>
>> >I am having reports of another JNDI related problem
>> with this release.
>> >
>> >Would it be possible for you to drop back to the
>> 2.4.0/3.1.RC8 release and let
>> >me know if that works, or shows the same problem ?
>> >
>> >Thanks,
>> >
>> >
>> >Jules
--------------------------------------------
<argo_tec gmbh>
ed.q.bridges
tel. 089-368179.552
fax 089-368179.79
osterwaldstra�e 10
(haus F eingang 21)
80805 m�nchen
</argo_tec gmbh>
--------------------------------------------
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure 1.1//EN" "http://jetty.mortbay.com/configure_1_1.dtd";>
<Configure class="org.mortbay.http.HttpServer">
<Call name="addListener">
<Arg>
<New class="org.mortbay.http.SocketListener">
<Set name="Port">8080</Set>
<Set name="MinThreads">5</Set>
<Set name="MaxThreads">255</Set>
<Set name="MaxIdleTimeMs">60000</Set>
<Set name="MaxReadTimeMs">60000</Set>
</New>
</Arg>
</Call>
<!--
<Call name="addWebApplication">
<Arg>/systemdump/*</Arg>
<Arg>C:/JBoss-2.4.3_Jetty-3.1.1-1/jboss/deploy/systemdump.war</Arg>
<Arg><SystemProperty name="jetty.home" default="."/>/etc/webdefault.xml</Arg>
<Arg type="boolean">true</Arg>
</Call>
-->
</Configure>
systemdump.war
SystemDump.java
