ramboid wrote : With JBoss 4.2.2, can I use the InvokerServlet in the
servlet-mapping section of my web.xml? With JBoss 4.0.5GA, I was able to
create war deployments with a web xml that would map the servlets as follows:
|
| servlet-nameinvoker/servlet-name
| servlet-class
|
ramboid wrote : With JBoss 4.2.2, can I use the InvokerServlet in the
servlet-mapping section of my web.xml? With JBoss 4.0.5GA, I was able to
create war deployments with a web xml that would map the servlets as follows:
|
| servlet-nameinvoker/servlet-name
| servlet-class
|
If I were to change the web.xml to map each servlet individually, I would have
to change the deployment process and design a new implementation strategy for
my team. Hence, we will probaly use the invoker for the time being. I am
upgrading an internal application to benefit from the new
If you read through the mail threads in the FAQ that i posted earlier, you will
see that the only recommended way is to map the servlets individually in your
web-application. Out of curisoity, is it that difficult to map the servlets
individually in your application? Also, is this application
JBoss-4.2.x ships with Tomcat-6. Starting Tomcat-6, to support invokerservlet
you need to specify privileged=true in the Context element. By the way, its
recommended not to use InvokerServlet. Read through these Tomcat FAQs :
If the InvokerServlet is evil, how would you suggest that I map the servlets
without having to add an entry for each one of them in the web.xml?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4138391#4138391
Reply to the post :
