[
http://jira.jboss.com/jira/browse/JBREM-542?page=all ]
Tom Elrod resolved JBREM-542.
------------------------------
Resolution: Done
I have put back in the ability to us 'invokerName' param as well as the
'locatorUrl' (which is basically a copy of the patch provided. Only change is to
not use the JBoss jmx implementation specific MBeanServerLocator. So is going to still
require the servlet have access to jmx classes, but at least won't have to be the
jboss specific implementation now (in the case they are using jdk 1.5 implementation).
Since the Connector also requires jmx implementation classes (due to imports), this seems
acceptable requirements. Also the point about not having to change config out of the box
is a compelling one.
web.xml config can now be:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC
"-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
<!-- The the JBossRemoting server invoker servlet web.xml descriptor
$Id: web.xml,v 1.2 2006/07/17 03:44:00 telrod Exp $
-->
<web-app>
<servlet>
<servlet-name>ServerInvokerServlet</servlet-name>
<description>The ServerInvokerServlet receives requests via HTTP
protocol from within a web container and passes it onto the
ServletServerInvoker for processing.
</description>
<servlet-class>org.jboss.remoting.transport.servlet.web.ServerInvokerServlet</servlet-class>
<init-param>
<param-name>invokerName</param-name>
<param-value>jboss.remoting:service=invoker,transport=servlet</param-value>
<description>The servlet server invoker</description>
<!--
<param-name>locatorUrl</param-name>
<param-value>servlet://localhost:8080/servlet-invoker/ServerInvokerServlet</param-value>
<description>The servlet server invoker locator url</description>
-->
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>ServerInvokerServlet</servlet-name>
<url-pattern>/ServerInvokerServlet/*</url-pattern>
</servlet-mapping>
</web-app>
where can swap out the 'invokerName' and 'locatorUrl' params.
change how remoting servlet finds servlet invoker
-------------------------------------------------
Key: JBREM-542
URL:
http://jira.jboss.com/jira/browse/JBREM-542
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Components: general
Affects Versions: 2.0.0.Beta2 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.0.0.CR1 (Boon)
Attachments: JBREM-542-patch.txt, ServerInvokerServlet.java
Currently the servlet deployed within servlet-invoker.war uses the servlet server
invoker's JMX Object name (provide within the init-param of web.xml) to lookup the
servlet server invoker to make calls upon. This is limited in that requires JMX be
available within the web container. Althought this will probably be available in most
J2EE app servers, might not be in other web container only deployments. Need to remove
this restriction.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira