server.xml, Realms, and WARs

2002-07-11 Thread Mark Shaw

I don't think my problem has a solution, but let me ask anyway:

I have a web-app that I deploy as a WAR, and this web-app uses its own Realm
implementation.  In my server.xml I specify the host's realm to use my
realm so that my web-app can be dynamically deployed (I don't define a
context entry in server.xml for it).  The problem is if I want to deploy
other web-apps in this host, they too must use the custom Realm.  Is there
anyway to use a custom Realm without explicitly defining it in the
server.xml?  Is there a way to defined my web-app context in my server.xml
and still be able to dynamically deploy it (via a WAR)?

One other question: is there a way to specify classpath parameters for a
dynamically deployed web-app to reference classes that aren't in the sever,
common, web-app libraries?

Thanks for any help with any these questions, I appreciated it.
-Mark

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: server.xml, Realms, and WARs

2002-07-11 Thread Craig R. McClanahan



On Thu, 11 Jul 2002, Mark Shaw wrote:

 Date: Thu, 11 Jul 2002 14:16:24 -0700
 From: Mark Shaw [EMAIL PROTECTED]
 Reply-To: Tomcat Users List [EMAIL PROTECTED]
 To: 'Tomcat Users List' [EMAIL PROTECTED]
 Subject: server.xml, Realms, and WARs

 I don't think my problem has a solution, but let me ask anyway:

 I have a web-app that I deploy as a WAR, and this web-app uses its own Realm
 implementation.  In my server.xml I specify the host's realm to use my
 realm so that my web-app can be dynamically deployed (I don't define a
 context entry in server.xml for it).  The problem is if I want to deploy
 other web-apps in this host, they too must use the custom Realm.  Is there
 anyway to use a custom Realm without explicitly defining it in the
 server.xml?  Is there a way to defined my web-app context in my server.xml
 and still be able to dynamically deploy it (via a WAR)?


In Tomcat 4.1.x you can do this, because it supports the ability to define
a context configuration file that contains just the Context element
(and it's nested content), which can be dynamically deployed along with
your WAR.  You could nest your custom Realm element inside this
Context element, and it would only apply to this webapp.  See the docs
on the manager webapp for more info.

Tomcat 4.0.x doesn't have any way to do this.

 One other question: is there a way to specify classpath parameters for a
 dynamically deployed web-app to reference classes that aren't in the sever,
 common, web-app libraries?


Not without modifying Tomcat sources.

 Thanks for any help with any these questions, I appreciated it.
 -Mark


Craig


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: server.xml, Realms, and WARs

2002-07-11 Thread Mark Shaw

Craig,

Thanks for the quick answer (as usual).  I have a follow-up question
regarding the class loader, does it only recognize JAR files?  For example,
old Oracle driver are packed in a ZIP file instead of a JAR, it appears that
I have to explicity include the file in my classpath arg for Tomcat to
locate it (although it's in my web-app/lib).  Any ideas?

-Mark

-Original Message-
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 11, 2002 2:27 PM
To: Tomcat Users List
Subject: Re: server.xml, Realms, and WARs




On Thu, 11 Jul 2002, Mark Shaw wrote:

 Date: Thu, 11 Jul 2002 14:16:24 -0700
 From: Mark Shaw [EMAIL PROTECTED]
 Reply-To: Tomcat Users List [EMAIL PROTECTED]
 To: 'Tomcat Users List' [EMAIL PROTECTED]
 Subject: server.xml, Realms, and WARs

 I don't think my problem has a solution, but let me ask anyway:

 I have a web-app that I deploy as a WAR, and this web-app uses its own
Realm
 implementation.  In my server.xml I specify the host's realm to use my
 realm so that my web-app can be dynamically deployed (I don't define a
 context entry in server.xml for it).  The problem is if I want to deploy
 other web-apps in this host, they too must use the custom Realm.  Is there
 anyway to use a custom Realm without explicitly defining it in the
 server.xml?  Is there a way to defined my web-app context in my server.xml
 and still be able to dynamically deploy it (via a WAR)?


In Tomcat 4.1.x you can do this, because it supports the ability to define
a context configuration file that contains just the Context element
(and it's nested content), which can be dynamically deployed along with
your WAR.  You could nest your custom Realm element inside this
Context element, and it would only apply to this webapp.  See the docs
on the manager webapp for more info.

Tomcat 4.0.x doesn't have any way to do this.

 One other question: is there a way to specify classpath parameters for a
 dynamically deployed web-app to reference classes that aren't in the
sever,
 common, web-app libraries?


Not without modifying Tomcat sources.

 Thanks for any help with any these questions, I appreciated it.
 -Mark


Craig


--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: server.xml, Realms, and WARs

2002-07-11 Thread Craig R. McClanahan



On Thu, 11 Jul 2002, Mark Shaw wrote:

 Date: Thu, 11 Jul 2002 15:02:02 -0700
 From: Mark Shaw [EMAIL PROTECTED]
 Reply-To: Tomcat Users List [EMAIL PROTECTED]
 To: 'Tomcat Users List' [EMAIL PROTECTED]
 Subject: RE: server.xml, Realms, and WARs

 Craig,

 Thanks for the quick answer (as usual).  I have a follow-up question
 regarding the class loader, does it only recognize JAR files?

Yes.  That's a servlet spec rule.

  For example,
 old Oracle driver are packed in a ZIP file instead of a JAR, it appears that
 I have to explicity include the file in my classpath arg for Tomcat to
 locate it (although it's in my web-app/lib).  Any ideas?


Either rename classesXXX.zip to classesXXX.jar (the internal format is
enough the same that this works) or use unzip and jar tools to unpack and
repack.  And while you're at it, please file a bug report with Oracle to
change their packaging -- using a zip file is *so* JDK 1.1 :-).

 -Mark


Craig


 -Original Message-
 From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, July 11, 2002 2:27 PM
 To: Tomcat Users List
 Subject: Re: server.xml, Realms, and WARs




 On Thu, 11 Jul 2002, Mark Shaw wrote:

  Date: Thu, 11 Jul 2002 14:16:24 -0700
  From: Mark Shaw [EMAIL PROTECTED]
  Reply-To: Tomcat Users List [EMAIL PROTECTED]
  To: 'Tomcat Users List' [EMAIL PROTECTED]
  Subject: server.xml, Realms, and WARs
 
  I don't think my problem has a solution, but let me ask anyway:
 
  I have a web-app that I deploy as a WAR, and this web-app uses its own
 Realm
  implementation.  In my server.xml I specify the host's realm to use my
  realm so that my web-app can be dynamically deployed (I don't define a
  context entry in server.xml for it).  The problem is if I want to deploy
  other web-apps in this host, they too must use the custom Realm.  Is there
  anyway to use a custom Realm without explicitly defining it in the
  server.xml?  Is there a way to defined my web-app context in my server.xml
  and still be able to dynamically deploy it (via a WAR)?
 

 In Tomcat 4.1.x you can do this, because it supports the ability to define
 a context configuration file that contains just the Context element
 (and it's nested content), which can be dynamically deployed along with
 your WAR.  You could nest your custom Realm element inside this
 Context element, and it would only apply to this webapp.  See the docs
 on the manager webapp for more info.

 Tomcat 4.0.x doesn't have any way to do this.

  One other question: is there a way to specify classpath parameters for a
  dynamically deployed web-app to reference classes that aren't in the
 sever,
  common, web-app libraries?
 

 Not without modifying Tomcat sources.

  Thanks for any help with any these questions, I appreciated it.
  -Mark
 

 Craig


 --
 To unsubscribe, e-mail:
 mailto:[EMAIL PROTECTED]
 For additional commands, e-mail:
 mailto:[EMAIL PROTECTED]

 --
 To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:[EMAIL PROTECTED]




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]