Serialization from Orion back to Client via Session EJB
I have a number of code tables in the database, that will only ever be read only.
Rather than creating the infrastructure of an Entity EJB for these tables I would like
to simply call a session bean to return read only versions of these codes.
A typical class has the form
public class CodeClass
implements Serializable
{
private long code;
private Stringname;
public longgetCode() { return code;}
public String getName() { return name;}
}
I've created a Session EJB that accesses the database using JDBC to return the entries
to the bean.
This bean uses these entries to construct instances of CodeClass and inserts them into
a Vector.
This vector is then returned as the result of the method call on the Session EJB.
The client receives an error from the server indicating that the CodeClass indicating
the class could not be (de-)serialized.
The Client is 1.4.0, orion is 1.3.1 (Oracle extended version), I've tested to ensure
that this simple CodeClass can be read/written between 1.3.1 and 1.4.0 and there
appears to be no problem there.
I'm a little stumped at this point, as the code seems to be very simple, compiles and
doesn't run. Is it the fact that I'm returning a Vector? Or am I missing a step,
or
RE: Werent current caller
Thanks for the hint, I'll give this a go. You must be intuitive as this parent child setting is what I'm trying to do, although I've also tried extracting the parent ID on the client side and then setting (via create) the parent key in the chils record as it's being created and this also throws the same exception. However OC4J may also be trying to reference the parent during this operation so the test is still worth conducting. I'll let you know the result. -Original Message- From: Lachezar Dobrev [SMTP:[EMAIL PROTECTED]] Sent: 08 April 2002 09:06 To: Orion-Interest Subject:Re: Werent current caller Hello. By the message, I would assume (correct me), that you have a parent/child relation. I may _guess_, that you are trying to use the parent to set something in the child (like the parent ID). If this is the case, you might _need_ to set the parent to be reentrant=true. That helped me. My code required to create the child with a parameter like: (XML_Tag)entityContext.getEJBObject() so that the child knows it's parent... That requires reentrant=true. It _may_ be a shot in the dark, because I've not come upon this exception, but rather some other (can't remember which though). However, this is no-cost test and is worth trying. Lachezar. - Original Message - From: Jeff Lowcock [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Saturday, April 06, 2002 9:56 AM Subject: RE: Werent current caller This is the stack trace from the server. java.lang.InternalError: Werent current caller, server stacktrace (to disable this message, use -Dejb.assert=false at startup): java.lang.Throwable: Werent current caller void NetNwkEjb_EntityBeanWrapper41.setEntityBean(javax.ejb.EntityBean) void com.evermind.server.ejb.EntityEJBHome.passivateAndRelease(com.evermind.serve r.ejb.EvermindEntityContext, boolean) void com.evermind.server.ejb.EntityEJBObject.releaseContext(boolean) com.neowurks.network.ejb.NetNwkEjb NetNwkEjbHome_EntityHomeWrapper57.create(long, java.lang.String, java.lang.String) java.lang.Object java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[]) void com.evermind.server.rmi.RMICallHandler.run(java.lang.Thread) void com.evermind.util.ThreadPoolThread.run() I've also received a mail that seems to indicate that the responder has only seen this in the oracle version of orion, which is the version I'm using. However OTN has been unavailable for the last day or so and I've not been able to check if there is any information there as well. This exception is being raised when I've successfully created the parent CMP and then try and create the child CMP, which then throws this. I'm working now to produce a focused piece of code to illustrate the client and server side without all of the other application baggage. -Original Message- From: Scott Farquhar [SMTP:[EMAIL PROTECTED]] Sent: 06 April 2002 02:05 To: Orion-Interest Subject: Re: Werent current caller Can you post the stack trace? Jeff Lowcock wrote: I'm getting this exception and message raised in the server when I'm attempting to create a new CMP instance. I cannot find any documentation on this message and way too much on the exception java.lang.InternalError, can anyone direct me to a source where I can identify possible sources of this error and where I'm going wrong. I've searched the Orion support site and the only mails I can find are for 0.9.4 and 0.9.6 versions, and none fo these mails actually describe the conditions I have. where to now? -- Scott Farquhar :: [EMAIL PROTECTED] Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World msg18676/bin0.bin Description: application/ms-tnef
Werent current caller
I'm getting this exception and message raised in the server when I'm attempting to create a new CMP instance. I cannot find any documentation on this message and way too much on the exception java.lang.InternalError, can anyone direct me to a source where I can identify possible sources of this error and where I'm going wrong. I've searched the Orion support site and the only mails I can find are for 0.9.4 and 0.9.6 versions, and none fo these mails actually describe the conditions I have. where to now?
RE: Werent current caller
This is the stack trace from the server. java.lang.InternalError: Werent current caller, server stacktrace (to disable this message, use -Dejb.assert=false at startup): java.lang.Throwable: Werent current caller void NetNwkEjb_EntityBeanWrapper41.setEntityBean(javax.ejb.EntityBean) void com.evermind.server.ejb.EntityEJBHome.passivateAndRelease(com.evermind.server.ejb.EvermindEntityContext, boolean) void com.evermind.server.ejb.EntityEJBObject.releaseContext(boolean) com.neowurks.network.ejb.NetNwkEjb NetNwkEjbHome_EntityHomeWrapper57.create(long, java.lang.String, java.lang.String) java.lang.Object java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[]) void com.evermind.server.rmi.RMICallHandler.run(java.lang.Thread) void com.evermind.util.ThreadPoolThread.run() I've also received a mail that seems to indicate that the responder has only seen this in the oracle version of orion, which is the version I'm using. However OTN has been unavailable for the last day or so and I've not been able to check if there is any information there as well. This exception is being raised when I've successfully created the parent CMP and then try and create the child CMP, which then throws this. I'm working now to produce a focused piece of code to illustrate the client and server side without all of the other application baggage. -Original Message- From: Scott Farquhar [SMTP:[EMAIL PROTECTED]] Sent: 06 April 2002 02:05 To: Orion-Interest Subject:Re: Werent current caller Can you post the stack trace? Jeff Lowcock wrote: I'm getting this exception and message raised in the server when I'm attempting to create a new CMP instance. I cannot find any documentation on this message and way too much on the exception java.lang.InternalError, can anyone direct me to a source where I can identify possible sources of this error and where I'm going wrong. I've searched the Orion support site and the only mails I can find are for 0.9.4 and 0.9.6 versions, and none fo these mails actually describe the conditions I have. where to now? -- Scott Farquhar :: [EMAIL PROTECTED] Atlassian :: http://www.atlassian.com Supporting YOUR J2EE World msg18666/bin0.bin Description: application/ms-tnef
