RE: RE : Problems configuring a Context path=xx using Apache/Tomcat

2006-10-24 Thread René Schade 
Thanks, that really helped.

It works fine if I place the file Servlets#application.xml
In the CATALINA_HOME/conf/Catalina/localhost/ folder.

I would prefer to place it in the /META-INF/ folder in the application, but 
Tomcat seems to ignore files not named context.xml in this folder.

Any suggestions?

René
 

 -Original Message-
 From: LASSIEGE Hugo [mailto:[EMAIL PROTECTED]
 Sent: 24. oktober 2006 10:22
 To: Tomcat Users List
 Subject: RE : Problems configuring a Context path=xx using
 Apache/Tomcat
 
 In tomcat 5.5.17, you can't use path in context (See bug
 http://issues.apache.org/bugzilla/show_bug.cgi?id=39120)
 But you can modify the name of your context file :
 servlets#application.xml, it should work.
 
 hugo
 
 -Message d'origine-
 De : René Schade [mailto:[EMAIL PROTECTED]
 Envoyé : mardi 24 octobre 2006 10:18
 À : users@tomcat.apache.org
 Objet : Problems configuring a Context path=xx using Apache/Tomcat
 
 Hi List,
 
 
 
 I'm running Apache 2.0, Tomcat 5.5.17, jdk 1.5
 
 
 
 I'm upgrading from Apache 1.3 Tomcat 3.* jdk 1.4
 
 
 
 In my Apache log file I have the following:
 
 
 
 JkMount /manager* foo
 
 JkMount /servlets/* foo
 
 
 
 The manager application works fine, when typing the URL
 
 
 
 http://website/manager/html
 
 
 
 Everything is ok, the manager application is launched.
 
 
 
 Now I'm trying to install an application on the path
 /servlets/myapplication. The Context file looks like this:
 
 
 
 Context  reloadable=true path=/servlets/myapplication/
 docBase=${catalina.home}/home/schade/myapplication/ debug=5
 allowoverride=true
 
   Valve
 className=org.apache.catalina.valves.AccessLogValve
 
 prefix=kvisremote_by_schade. suffix=.txt
 
  pattern=common/
 
 /Context
 
 
 
 Typing a URL like http://website/servlets/myapplication/testfile.html does
 not trigger this context. I've made a similar Valve for the manager-
 application, and here every request to the manager Context is logged.
 Logging the host verifies that requests sent to
 http://website/servlets/kvisremote are sent to the host, but it does not
 seam to know which context to forward the request to.
 
 
 
 I guess it has something to do with the path-attribute. A similar solution
 worked fine on the old server...
 
 
 
 I've been struggling with this for a while now, so any kinds of
 suggestions are appreciated.
 
 
 
 Regards,
 René
 
 
 
 
 CONFIDENTIALITY:   This email (including any attachments) may contain
 confidential, proprietary and privileged information, and unauthorized
 disclosure or use is prohibited.  If you received this email in error,
 please notify the sender and delete this email from your system.  Thank
 you
 
 
 CONFIDENTIALITÉ: Ce courrier électronique (pièces jointes incluses) peut
 contenir des informations confidentielles, propriétaires et privilégiées,
 dont la divulgation ou l'utilisation non-autorisée est interdite.
 Si vous avez reçu ce courrier électronique par erreur, nous vous
 remercions de bien vouloir avertir l'expéditeur et détruire ce courrier
 électronique
 de votre système.
 Merci.
 
 
 
 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problems configuring a Context path=xx using Apache/Tomcat

2006-10-24 Thread Michael Courcy 

Hi
Can you explain where you define context.xml ?
Here is a fragment of
http://tomcat.apache.org/tomcat-5.5-doc/config/context.html
path : [...] The value of this field must not be set except when 
statically defining a Context in server.xml, as it will be infered from 
the filenames used for either the .xml context file or the docBase.


Mic


René Schade a écrit :

Hi List,

 


I'm running Apache 2.0, Tomcat 5.5.17, jdk 1.5

 


I'm upgrading from Apache 1.3 Tomcat 3.* jdk 1.4

 


In my Apache log file I have the following:

 


JkMount /manager* foo

JkMount /servlets/* foo

 


The manager application works fine, when typing the URL

 

http://website/manager/html 

 


Everything is ok, the manager application is launched.

 


Now I'm trying to install an application on the path /servlets/myapplication. 
The Context file looks like this:

 


Context  reloadable=true path=/servlets/myapplication/ 
docBase=${catalina.home}/home/schade/myapplication/ debug=5 allowoverride=true

  Valve className=org.apache.catalina.valves.AccessLogValve

prefix=kvisremote_by_schade. suffix=.txt

 pattern=common/

/Context

 


Typing a URL like http://website/servlets/myapplication/testfile.html does not 
trigger this context. I've made a similar Valve for the manager-application, and here 
every request to the manager Context is logged. Logging the host verifies 
that requests sent to http://website/servlets/kvisremote are sent to the host, but it 
does not seam to know which context to forward the request to.

 


I guess it has something to do with the path-attribute. A similar solution 
worked fine on the old server...

 

I've been struggling with this for a while now, so any kinds of suggestions are appreciated. 

 


Regards,
René


  



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problems configuring a Context path=xx using Apache/Tomcat

2006-10-24 Thread Michael Courcy 

Have a look there as well

http://issues.apache.org/bugzilla/show_bug.cgi?id=39120

René Schade a écrit :

Hi List,

 


I'm running Apache 2.0, Tomcat 5.5.17, jdk 1.5

 


I'm upgrading from Apache 1.3 Tomcat 3.* jdk 1.4

 


In my Apache log file I have the following:

 


JkMount /manager* foo

JkMount /servlets/* foo

 


The manager application works fine, when typing the URL

 

http://website/manager/html 

 


Everything is ok, the manager application is launched.

 


Now I'm trying to install an application on the path /servlets/myapplication. 
The Context file looks like this:

 


Context  reloadable=true path=/servlets/myapplication/ 
docBase=${catalina.home}/home/schade/myapplication/ debug=5 allowoverride=true

  Valve className=org.apache.catalina.valves.AccessLogValve

prefix=kvisremote_by_schade. suffix=.txt

 pattern=common/

/Context

 


Typing a URL like http://website/servlets/myapplication/testfile.html does not 
trigger this context. I've made a similar Valve for the manager-application, and here 
every request to the manager Context is logged. Logging the host verifies 
that requests sent to http://website/servlets/kvisremote are sent to the host, but it 
does not seam to know which context to forward the request to.

 


I guess it has something to do with the path-attribute. A similar solution 
worked fine on the old server...

 

I've been struggling with this for a while now, so any kinds of suggestions are appreciated. 

 


Regards,
René


  



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Problems configuring a Context path=xx using Apache/Tomcat

2006-10-24 Thread René Schade 
Hi List,

 

I'm running Apache 2.0, Tomcat 5.5.17, jdk 1.5

 

I'm upgrading from Apache 1.3 Tomcat 3.* jdk 1.4

 

In my Apache log file I have the following:

 

JkMount /manager* foo

JkMount /servlets/* foo

 

The manager application works fine, when typing the URL

 

http://website/manager/html 

 

Everything is ok, the manager application is launched.

 

Now I'm trying to install an application on the path /servlets/myapplication. 
The Context file looks like this:

 

Context  reloadable=true path=/servlets/myapplication/ 
docBase=${catalina.home}/home/schade/myapplication/ debug=5 
allowoverride=true

  Valve className=org.apache.catalina.valves.AccessLogValve

prefix=kvisremote_by_schade. suffix=.txt

 pattern=common/

/Context

 

Typing a URL like http://website/servlets/myapplication/testfile.html does not 
trigger this context. I've made a similar Valve for the manager-application, 
and here every request to the manager Context is logged. Logging the host 
verifies that requests sent to http://website/servlets/kvisremote are sent to 
the host, but it does not seam to know which context to forward the request to.

 

I guess it has something to do with the path-attribute. A similar solution 
worked fine on the old server...

 

I've been struggling with this for a while now, so any kinds of suggestions are 
appreciated. 

 

Regards,
René

RE : Problems configuring a Context path=xx using Apache/Tomcat

2006-10-24 Thread LASSIEGE Hugo 
In tomcat 5.5.17, you can't use path in context (See bug 
http://issues.apache.org/bugzilla/show_bug.cgi?id=39120)
But you can modify the name of your context file : servlets#application.xml, it 
should work.

hugo

-Message d'origine-
De : René Schade [mailto:[EMAIL PROTECTED] 
Envoyé : mardi 24 octobre 2006 10:18
À : users@tomcat.apache.org
Objet : Problems configuring a Context path=xx using Apache/Tomcat

Hi List,

 

I'm running Apache 2.0, Tomcat 5.5.17, jdk 1.5

 

I'm upgrading from Apache 1.3 Tomcat 3.* jdk 1.4

 

In my Apache log file I have the following:

 

JkMount /manager* foo

JkMount /servlets/* foo

 

The manager application works fine, when typing the URL

 

http://website/manager/html 

 

Everything is ok, the manager application is launched.

 

Now I'm trying to install an application on the path /servlets/myapplication. 
The Context file looks like this:

 

Context  reloadable=true path=/servlets/myapplication/ 
docBase=${catalina.home}/home/schade/myapplication/ debug=5 
allowoverride=true

  Valve className=org.apache.catalina.valves.AccessLogValve

prefix=kvisremote_by_schade. suffix=.txt

 pattern=common/

/Context

 

Typing a URL like http://website/servlets/myapplication/testfile.html does not 
trigger this context. I've made a similar Valve for the manager-application, 
and here every request to the manager Context is logged. Logging the host 
verifies that requests sent to http://website/servlets/kvisremote are sent to 
the host, but it does not seam to know which context to forward the request to.

 

I guess it has something to do with the path-attribute. A similar solution 
worked fine on the old server...

 

I've been struggling with this for a while now, so any kinds of suggestions are 
appreciated. 

 

Regards,
René




CONFIDENTIALITY:   This email (including any attachments) may contain
confidential, proprietary and privileged information, and unauthorized
disclosure or use is prohibited.  If you received this email in error,
please notify the sender and delete this email from your system.  Thank you


CONFIDENTIALITÉ: Ce courrier électronique (pièces jointes incluses) peut 
contenir des informations confidentielles, propriétaires et privilégiées,
dont la divulgation ou l'utilisation non-autorisée est interdite.
Si vous avez reçu ce courrier électronique par erreur, nous vous remercions de 
bien vouloir avertir l'expéditeur et détruire ce courrier électronique
de votre système.
Merci.



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]