[EJB/JBoss] - Re: Serializable no remote classloading
by ron.sigal@jboss.com
The default behavior in AS 4.0.X was to use a "legacy" remote invoker, and the default in AS 4.2 is to use a Remoting invoker. For a Remoting invoker, the ability to download classes over the network has to be enabled explicitly. For EJB3 the configuration file is .../server/default/deploy/ejb3.deployer/META-INF/jboss-service.xml (substitute your configuration for "default"), and the relevant entry is
| <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">socket://${jboss.bind.address}:3873</attribute>
| <attribute name="Configuration">
| <handlers>
| <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
| </handlers>
| </attribute>
| </mbean>
|
If you add a "loaderport" parameter to the InvokerLocator, Remoting will create a "classloader server" which, if a class cannot be found on the client side, will be contacted by the client side classloader. E.g.,
| <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">socket://${jboss.bind.address}:3873/?loaderport=4873</attribute>
| <attribute name="Configuration">
| <handlers>
| <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
| </handlers>
| </attribute>
| </mbean>
|
will create a classloader server that listens on port ${jboss.bind.address}:4873.
For more discussion see Section "5.5. Marshalling" of the Remoting Guide (http://labs.jboss.com/jbossremoting/docs/guide/index.html).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121471#4121471
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121471
18 years, 5 months
[JBoss Seam] - Re: JSF/Seam Binding and Nested Classes
by aggtecnologia
Could you find the answer? I am stuck with the same problem.
Just in case the problem is not clear:
| @Stateful
| @Entity
| @Name("mother")
| public class Mother {
|
| private Daughter daughter;
|
| ... setters and getters
| }
|
|
and the nested class is:
| public class Daughter {
|
| private String someprop;
|
| ... setters and getters
|
| }
|
|
When I try to put something in daughters property someprop
| <h:inputText value="#{mother.daughter.someprop}"/>
|
the contents of the html field are not transfered to someprop and any action invoked from the page is not even executed. It seems that the lifecycle ends when the framework tries to transfer values from the request to the properties inside the object inside the EJB.
I am using seam 1.2.1 and quite desperated.
Thaks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121467#4121467
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121467
18 years, 5 months