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 String name;
public long getCode() { 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????
