OK, Here is the problem : I can deploy a JBoss Remoting Service in my ear, with an embedded sar (though I have got a ClassNotFoundException at Runtime on my Marshaller, if deployer as a simple sar it works !!). In the Invoke method of my ServerInvocationHandler, I want to access my Business Layer, composed with EJB3. To resume my problem, I want the ServerInvocationHandler act as my Client Layer (originally JSF layer) to do this ; 1) telnet send a string like "ACTION;PARAM1;PARAM2" 2) ServerInvocationHandler.invoke receieve ACTION;PARAM1;PARAM2 ..... and invoke MyStatelessEJB3.action(PARAM1,PARAM2) and return String result. 3) telnet receive the result. So, the questions : A) Is it an architecture anti-pattern ??? if yes how do i design this behaviour ? B) What about Seam Integration (formally acces to Persistence Layer, Transaction, etc...) C) Why my ServerInvocationHandler don't found my Marshaller/UnMarshaller ?? Here the jboss-service.xml | <?xml version="1.0" encoding="UTF-8"?> | <server> | | <loader-repository>seam.jboss.org:loader=SelfSystem</loader-repository> | | <mbean code="org.jboss.remoting.transport.Connector" | name="jboss.remoting:service=Connector,transport=Socket" | display-name="Socket transport Connector"> | | <attribute name="Configuration"> | <config> | | <invoker transport="socket"> | <attribute name="marshaller" isParam="true"> | net.selfsystem.remoting.dispositif.TextMarshaller | </attribute> | <attribute name="unmarshaller" isParam="true"> | net.selfsystem.remoting.dispositif.TextUnMarshaller | </attribute> | <attribute name="numAcceptThreads">1</attribute> | <attribute name="maxPoolSize">40</attribute> | <attribute name="clientMaxPoolSize" isParam="true">40</attribute> | <attribute name="socketTimeout">60000</attribute> | <attribute name="serverBindAddress">127.0.0.1</attribute> | <attribute name="serverBindPort">6666</attribute> | <attribute name="enableTcpNoDelay" isParam="true">false</attribute> | <attribute name="backlog">200</attribute> | </invoker> | | <handlers> | <handler subsystem="dis">net.selfsystem.remoting.dispositif.ServerInvocationHandler</handler> | </handlers> | </config> | </attribute> | | </mbean> | </server> | The sar is at the root of the EAR, And the jboss-app.xml in teh /META-INF of the EAR : | <?xml version="1.0" encoding="UTF-8"?> | <!DOCTYPE jboss-app | PUBLIC "-//JBoss//DTD J2EE Application 4.2//EN" | "http://www.jboss.org/j2ee/dtd/jboss-app_4_2.dtd"> | | <jboss-app> | | <loader-repository>seam.jboss.org:loader=SelfSystem</loader-repository> | | <module> | <service>remoting-dispositif.sar</service> | </module> | | </jboss-app> | | Thanks for your response. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155654#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...