[jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: Exception propagation using HTTP servlet transport on 1.
martinschweigert
do-not-reply at jboss.com
Fri May 30 06:33:57 EDT 2008
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3">
| <depends>jboss.aop:service=AspectDeployer</depends>
| <!--attribute name="InvokerLocator">
| servlet://${http.rmi.host}:${http.rmi.port}/servlet-invoker/ServerInvokerServlet
| </attribute-->
|
|
| <attribute name="Configuration">
| <config>
|
| <invoker transport="servlet">
| <attribute name="serverBindAddress">${http.rmi.host}</attribute>
| <attribute name="serverBindPort">${http.rmi.port}</attribute>
| <attribute name="path">servlet-invoker/ServerInvokerServlet</attribute>
| <attribute name="return-exception" isParam="true">true</attribute>
| </invoker>
| <handlers>
| <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
| </handlers>
| </config>
| </attribute>
| </mbean>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154572#4154572
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154572
More information about the jboss-dev-forums
mailing list