Why did this behavior change with JBoss3?  Both apps can use the same 
CL, they just need to bind to 2 different contexts.  Or perhaps Jetty 
has something which will do an internal proxy (nothing on the client 
side) from one context to another.

I still believe that the app.xml I have should work... I don't 
understand why the CL has anything todo with deploying a webapp to a 
context.

--jason


On Thursday, June 20, 2002, at 03:12 AM, Jules Gosnell wrote:

>
> I see maybe two ways to achieve this (based on my understanding of our 
> ClassLoading system).
>
> 1. the second war only contains the descriptor[s] - because everything 
> shares the same ClassLoader it will share all the classes and 
> configuration of the first (I haven't tried this...)
>
> 2. you could change Jetty's Java2ClassLoadingCompliance attribute in 
> it's jboss-service.xml to false - so that Jetty gives both wars their 
> own ClassLoader (but you sacrifice calls to other services, 
> particularly EJB, being by reference, not value).
>
> Is that any help ?
>
>
> Jules
>
>
> David Jencks wrote:
>> Hmm, I would expect this to create 2 unified class loaders for the war,
>> which would indeed cause problems...
>> I bet there is a similar problem if you have 2 ejb jars with manifest
>> Class-Path: references to the same library jar, I think it will end up
>> loaded twice.
>> Is what you are doing spec compliant?
>> I think its a bug.
>> david jencks
>> On 2002.06.19 20:53:36 -0400 Jason Dillon wrote:
>>> Is there a preferred way to deploy one web app under 2 different
>>> contexts?
>>>
>>>
>>> I was using the following in an earlier version of JBoss, but not this
>>> will either deploy one or the other. and you can't really predict 
>>> which
>>> it will be:
>>>
>>>
>>>   <module>
>>>
>>>      <web>
>>>
>>>         <web-uri>listener.war</web-uri>
>>>
>>>         <context-root>/</context-root>
>>>
>>>      </web>
>>>
>>>   </module>
>>>
>>>
>>>   <!-- For compatibility -->
>>>
>>>   <module>
>>>
>>>      <web>
>>>
>>>         <web-uri>listener.war</web-uri>
>>>
>>>         <context-root>/listener/</context-root>
>>>
>>>      </web>
>>>
>>>   </module>
>>>
>>>
>>> Am I doing something wrong, or is the EAR deployer or WebApp deploy
>>> having issues?
>>>
>>>
>>> --jason
>>>
>>>
>>> <html>
>>>
>>> <head>
>>> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
>>>
>>>
>>> <meta name=Generator content="Microsoft Word 10 (filtered)">
>>>
>>> <style>
>>> <!--
>>> /* Style Definitions */
>>> p.MsoNormal, li.MsoNormal, div.MsoNormal
>>>     {margin:0in;
>>>     margin-bottom:.0001pt;
>>>     font-size:12.0pt;
>>>     font-family:"Times New Roman";}
>>> a:link, span.MsoHyperlink
>>>     {color:blue;
>>>     text-decoration:underline;}
>>> a:visited, span.MsoHyperlinkFollowed
>>>     {color:purple;
>>>     text-decoration:underline;}
>>> span.EmailStyle17
>>>     {font-family:Arial;
>>>     color:windowtext;}
>>> @page Section1
>>>     {size:8.5in 11.0in;
>>>     margin:1.0in 1.25in 1.0in 1.25in;}
>>> div.Section1
>>>     {page:Section1;}
>>> -->
>>> </style>
>>>
>>> </head>
>>>
>>> <body lang=EN-US link=blue vlink=purple>
>>>
>>> <div class=Section1>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>Is there a preferred way to deploy one web app 
>>> under 2
>>> different contexts?</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>I was using the following in an earlier version of
>>> JBoss,
>>> but not this will either deploy one or the other&#8230; and you
>>> can&#8217;t
>>> really predict which it will be:</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;&nbsp; &lt;module&gt;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>>> &lt;web&gt;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>>> &lt;web-uri&gt;listener.war&lt;/web-uri&gt;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>>> &lt;context-root&gt;/&lt;/context-root&gt;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>>> &lt;/web&gt;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;&nbsp; &lt;/module&gt;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;&nbsp; &lt;!-- For compatibility
>>> --&gt;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;&nbsp; &lt;module&gt;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>>> &lt;web&gt;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>>> &lt;web-uri&gt;listener.war&lt;/web-uri&gt;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>>> &lt;context-root&gt;/listener/&lt;/context-root&gt;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>>> &lt;/web&gt;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;&nbsp; &lt;/module&gt;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>Am I doing something wrong, or is the EAR deployer 
>>> or
>>> WebApp
>>> deploy having issues?</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>&nbsp;</span></font></p>
>>>
>>> <p class=MsoNormal><font size=2 face=Arial><span style='font-
>>> size:10.0pt;
>>> font-family:Arial'>--jason</span></font></p>
>>>
>>> </div>
>>>
>>> </body>
>>>
>>> </html>
>>>
>> -------------------------------------------------------
>>                    Bringing you mounds of caffeinated joy
>>                    >>>     http://thinkgeek.com/sf    <<<
>> _______________________________________________
>> Jboss-development mailing list
>> [EMAIL PROTECTED]
>> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
>
>
>
> -------------------------------------------------------
>                   Bringing you mounds of caffeinated joy
>                   >>>     http://thinkgeek.com/sf    <<<
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development



-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to