[
http://jira.jboss.com/jira/browse/JBREM-542?page=comments#action_12339633 ]
Tom Elrod commented on JBREM-542:
----------------------------------
The org.jboss.remoting.transport.servlet.web.ServerInvokerServlet has been changed so that
instead of looking for the 'invokerName' init-param, will now look for
'locatorUrl'. The value of the locatorUrl param should be the invoker locator url
of the servlet server invoker.
An example of the web.xml configuration within servlet-invoker.war/WEB-INF/web.xml would
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.1 2005/06/16 21:12:48 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>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>
And the service xml for deploying the servlet server invoker would look something like:
<?xml version="1.0" encoding="UTF-8"?>
<server>
<mbean code="org.jboss.remoting.transport.Connector"
name="jboss.remoting:service=Connector,transport=SSLServlet"
display-name="Servlet transport Connector">
<attribute name="InvokerLocator">
servlet://localhost:8080/servlet-invoker/ServerInvokerServlet
</attribute>
<attribute name="Configuration">
<config>
<handlers>
<handler
subsystem="test">org.jboss.test.remoting.transport.web.WebInvocationHandler</handler>
</handlers>
</config>
</attribute>
</mbean>
</server>
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)
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