-
1. Re: JavaBean passing to a session between two different VM
tklivan Jun 30, 2004 5:47 AM (in response to tklivan)err no one ?
-
2. Re: JavaBean passing to a session between two different VM
jamesstrachan Jun 30, 2004 11:28 AM (in response to tklivan)Elementaries
1. Check that there is no transient modifier on variables in the Javabean.
2. Check that the Javabean class, and any classes that it references, are on the classpath in the remote JVM.
3. Supply sample code for servlet, Javabean and session bean to see if anybody can spot a silly.
James -
3. Re: JavaBean passing to a session between two different VM
tklivan Jun 30, 2004 10:21 PM (in response to tklivan)thanx for the reply james,
I have no transient modifiers in the javabean.
the classes are all in the classpath. I find it weird coz if I run it as a scheduled task (thru quartz) in jboss, it works fine. No code changes or anything.
but once I run the client from the commant prompt (diff vm) it can instantiate and everything and do whatever it needs on the client but once the client passes it as a parameter to the session, the session ejb reports it as null. It does not give any errors whatsoever, it just displayu null when we print out the values. -
4. Re: JavaBean passing to a session between two different VM
tklivan Jun 30, 2004 11:07 PM (in response to tklivan)if the client is a normal java class that runs from the command prompt, would i need to create stubs for it ??
I can however reference and call other ejbs but cannot pass the javabean across. weird. -
5. Re: JavaBean passing to a session between two different VM
yokivo Jul 2, 2004 12:32 AM (in response to tklivan)try it without serializing.
yokivo -
6. Re: JavaBean passing to a session between two different VM
darranl Jul 2, 2004 4:45 AM (in response to tklivan)No you do not need to create any stubs for the bean to be passed remotely.
Can you check and double check your code to make sure that you have not caught any exceptions and hidden them. The last person to ask for assistance with this problem had hidden the exception that would have said exactly what the problem was.
Additionally is there any chance of you posting the bean here or at least create a new bean that demonstrates the problem and post it here.