> -----Original Message-----
> From: Pedro Nevado [mailto:[EMAIL PROTECTED]
> Sent: jeudi 9 septembre 2004 16:54
> To: Cactus Users List
> Subject: RE: What to put in web.xml or cactus-web.xml, and what not.
> 
> Allow me to elaborate futher my previous e-mail.
> I know that in a production simulated environment, you must put every
> (non-test)component in your web.xml. The point of my e-mail is about the
> relevance of the web.xml in an only test environment.
> 
> From that point of view, the only thing we need is a deployment descriptor
> file with the three redirector components. No need for anything else; it
> is
> enough with precise path references to the jsp's to use and the classes to
> test in the classpath.
> Sorry for the verbosity.

Yes, this should be enough.

Thanks
-Vincent

PS: Sorry for the delay in the answer...

> 
> -----Mensaje original-----
> De: Pedro Nevado [mailto:[EMAIL PROTECTED]
> Enviado el: jueves, 09 de septiembre de 2004 16:24
> Para: [EMAIL PROTECTED]
> Asunto: What to put in web.xml or cactus-web.xml, and what not.
> 
> 
> Hi there,
> 
> As a Cactus' beginner, I find      intriguingthingsthatprobablyarenot.
> 
> For instance, in the examples in jakarta-cactus-13-1.6.1\samples\servlet:
> - the test.jsp used to assert a dispatch-forward is referenced in the
> (cactus-)web.xml.
> - the SampleServlet which defines the dispatch is not defined in either of
> the two deployment descriptors.
> 
> However, if we have a look at the example in the JUnit in Action book
> (servlet example of chapter 9), the opposite happens:
> - the securityError.jsp used in a (SecurityFilter) dispatch-forward is not
> included in the deployment descriptors.
> - the AdminServlet is included in the web.xml file. BTW, the
> SecurityFilter
> is not included.
> 
> My question is: does it matter what is included in the deployment
> descriptors?
> 
> This is my guess:
> 
> - test.jsp should be included in the deployment descriptor because it is
> not
> in the context root directory. For the same reason, securityError.jsp
> could
> not be included, because it is in the context root.
> - since the instances of the servlets and filters used in the tests are
> plain Java objects, it is irrelevant if they are included, so AdminServlet
> could be excluded of the web.xml.
> 
> Any more guesses?
> Regards,
> 
> Pedro Nevado
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]



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

Reply via email to