> -----Original Message-----
> From: Marco Barcella [mailto:[EMAIL PROTECTED]]
> Sent: 07 October 2002 21:48
> To: Cactus Users List
> Subject: RE: Particular Configuration Problem
>
> Thanks Vincent,
>
> let me make sure I understand one last point:
> I should be able to add the redirector definitions
> to the global web.xml in TOMCAT and avoid modifying
> the production web.xml. Right? So far it seems to work
> but not sure about the future.
Yes, that does work (and it's quite neat!) because Tomcat does a "merge"
of both web.xml. It's a Tomcat specific feature and won't work for all
servlet containers.
-Vincent
>
> Thanks a lot for the advices,
> marco
>
> <>-----Original Message-----
> <>From: Vincent Massol [mailto:[EMAIL PROTECTED]]
> <>Sent: Monday, October 07, 2002 4:11 PM
> <>To: 'Cactus Users List'
> <>Subject: RE: Particular Configuration Problem
> <>
> <>
> <>Hi Marco,
> <>
> <>> -----Original Message-----
> <>> From: Marco Barcella [mailto:[EMAIL PROTECTED]]
> <>> Sent: 07 October 2002 20:14
> <>> To: Cactus Users List
> <>> Subject: Particular Configuration Problem
> <>>
> <>> Hi all,
> <>>
> <>> I understand that I am supposed to configure the server side
(web.xml)
> <>> and the client side (cactus.properties: contextURL).
> <>>
> <>> I am using TOMCAT 4.0.3
> <>>
> <>> In my case: I have an application that I deploy to C:/foe/bo/
> <>(deployed
> <>> application);
> <>> this application comes with a web.xml that I can modify adding the
> <>> redirectors definition, as specified by the website tutorial. If I
do
> <>that
> <>> everything works, but, ideally I should not modify that web.xml.
> <>Instead,
> <>> I should create another application (testing application) (in
webapps
> <>for
> <>> example) where I create
> <>> the web.xml which defines the redirectors (instead of modifying
the
> <>> deployed
> <>> application web.xml) and
> <>> place a build.xml that runs the tests through ANT.
> <>>
> <>
> <>Ideally, yes ... but not in the current cactus. The strategy is to
have
> <>ant scripts that create 2 wars : one for production and one for
testing.
> <>
> <>> THE PROBLEM is that in order to have the redirectors found, I have
to
> <>> specify the URLContext to be
> <>> the testing application URL. Therefore I cannot define the
URLContext
> <>to
> <>> be
> <>> the deployed application
> <>> one and therefore I cannot use some methods like
> <>> pageContext.include(relariveURL), testing some files in the
deployed
> <>> application.
> <>
> <>It won't work anyway as one webapp is completely separate from
another
> <>webapp. They live in different realms and cannot call each other. I
> <>think there is a JSR (or maybe it is the upcoming Servlet API 2.4 ?)
> <>that allows cross-webapp calls but it's definitely not in 2.2 nor
2.3.
> <>
> <>>
> <>> I could define the redirectors in the global web.xml, but I am
trying
> <>to
> <>> avoid that.
> <>> Am I missing something? Is there a way to do what I would like to
do?
> <>
> <>Yes, by having 2 web.xml and packaging 2 wars. BTW, if you're
concerned
> <>about reuse you can have only one web.xml which gets resolved
> <>differently if you're packaging the test war. See
> <>http://jakarta.apache.org/cactus/faq.html#faq2
> <>
> <>-Vincent
> <>
> <>>
> <>> Thanks in advance,
> <>> marco
> <>>
> <>>
> <>>
> <>>
> <>> --
> <>> To unsubscribe, e-mail: <mailto:cactus-user-
> <>> [EMAIL PROTECTED]>
> <>> For additional commands, e-mail: <mailto:cactus-user-
> <>> [EMAIL PROTECTED]>
> <>
> <>
> <>
> <>--
> <>To unsubscribe, e-mail:
> <><mailto:[EMAIL PROTECTED]>
> <>For additional commands, e-mail:
> <><mailto:[EMAIL PROTECTED]>
> <>
> <>
>
> --
> To unsubscribe, e-mail: <mailto:cactus-user-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:cactus-user-
> [EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
