Deployng war file: Using InvokerServlet in JBoss 4.2.2

[ramboid]

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-name>invoker</servlet-name>
<servlet-class>
org.apache.catalina.servlets.InvokerServlet
</servlet-class>
<load-on-startup>2</load-on-startup>

<servlet-mapping>
<servlet-name>invoker</servlet-name>
<url-pattern>/servlet/*</url-pattern>
</servlet-mapping>

But in JBoss 4.2.2 I must explicitly add a mapping for each servlet in the web.xml file instead of just using the invoker

[jaikiran]

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 :

http://wiki.apache.org/tomcat/FAQ/Miscellaneous?highlight=%28invoker%29%7C%28servlet%29#Q2

[ramboid]

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?

[jaikiran]

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 just a sample application that you are trying out or is it a production application?

[ramboid]

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 version of JBoss.
Would you consider it a lesser evil setting the privileged attribute in a context.xml in the WEB-INF folder of the web application rather than in the context of tomcat? Would this not restrict the privileged setting to the context fo the wed applicaiton?

[dilipmavireddi]

"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-name>invoker</servlet-name>
<servlet-class>
org.apache.catalina.servlets.InvokerServlet
</servlet-class>
<load-on-startup>2</load-on-startup>

<servlet-mapping>
<servlet-name>invoker</servlet-name>
<url-pattern>/servlet/*</url-pattern>
</servlet-mapping>

But in JBoss 4.2.2 I must explicitly add a mapping for each servlet in the web.xml file instead of just using the invoker

[dilipmavireddi]

"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-name>invoker</servlet-name>
<servlet-class>
org.apache.catalina.servlets.InvokerServlet
</servlet-class>
<load-on-startup>2</load-on-startup>

<servlet-mapping>
<servlet-name>invoker</servlet-name>
<url-pattern>/servlet/*</url-pattern>
</servlet-mapping>

But in JBoss 4.2.2 I must explicitly add a mapping for each servlet in the web.xml file instead of just using the invoker