-
1. Re: MarshalException
manax Jun 28, 2003 3:44 AM (in response to manax)Sorry, I get this exception when I'm creating a SSB (I had an instance of the home interface after lookup successfully, and going to create an instance of remote interface).
Please help me.
Thanks! -
2. Re: MarshalException
frito Jun 30, 2003 3:18 AM (in response to manax)If I remember right, this was a problem with an earlier release (something about 3.0.2 or 3.0.3). It should be fixed with later releases.
If this was not the problem, please provide more information (used versions, code snippets, ...)
Greetings,
Frito -
3. Re: MarshalException
jtremouroux Jul 1, 2003 4:20 PM (in response to manax)Hello,
I just have the same problem.
I'm using jboss-3.0.7_tomcat-4.1.24 on both sides.
It is a simple session EJB.
On the server side:
ejb-jar.xml:
...
[CDATA[]]
<ejb-name>DBOOProcess</ejb-name>
com.belgacom.DBOO.DBOOProcessHome
com.belgacom.DBOO.DBOOProcess
<local-home>com.belgacom.DBOO.DBOOProcessLocalHome</local-home>
com.belgacom.DBOO.DBOOProcessLocal
<ejb-class>com.belgacom.DBOO.DBOOProcessSession</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
...
jboss.xml:
....
<ejb-name>DBOOProcess</ejb-name>
<jndi-name>DBOOProcessBean</jndi-name>
<local-jndi-name>DBOOProcessLocal</local-jndi-name>
....
On the client side:
ejb-jar.xml:
...
<ejb-ref>
<ejb-ref-name>ejb/DBOOProcess</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
com.belgacom.DBOO.DBOOProcessHome
com.belgacom.DBOO.DBOOProcess
</ejb-ref>
....
jboss.xml:
...
<ejb-ref>
<ejb-ref-name>ejb/DBOOProcess</ejb-ref-name>
<jndi-name>jnp://192.168.0.185:1099/DBOOProcessBean</jndi-name>
</ejb-ref>
.... -
4. Re: MarshalException
frito Jul 2, 2003 3:03 AM (in response to manax)Sourceforge Bug #663114 fixed, but not as I expected ;-)
http://sourceforge.net/tracker/?group_id=22866&atid=376685&func=detail&aid=663114
Greetings,
Frito -
5. Re: MarshalException
jtremouroux Jul 2, 2003 11:23 AM (in response to manax)I have solved the problem by declaring my SSB A (the calling one) to not use transactions.
Just add an assembly-descriptor in ejb-ar.xml
<assembly-descriptor>
<container-transaction>
<ejb-name>Rosy</ejb-name>
<method-name>*</method-name>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
</assembly-descriptor>