Tim, the spec says that dependent objects are not exposed in the remote
interface. It is correct that your client app can't see them.
The method laid out by the spec says that your supposed to write a
non-abstract method in your bean class that manipulates the collection of
dependent objects using the abstract methods you defined. These
non-abstract methods are exposed in the remote interface.
Jim
--On Thursday, October 26, 2000 1:04 PM -0400 Tim Drury
<[EMAIL PROTECTED]> wrote:
>
> I save successfully saved an ejb w/ dependent object
> into the database. But when I try to pull the ejb
> back (w/dependent object), the client throws an
> exception saying it cannot find the dependent object
> class.
>
> Client code snippet:
>
> system.out.println(contact.getName()); // this works
> Address a = contact.getAddress(); // this throws exception
>
> The ejb attributes print out on the screen
> fine, but when I try to get the Address
> dependent object the *client* throws this
> exception:
>
> java.lang.ClassNotFoundException: Address_Dependent0
>
> Now, I think the problem is obvious. My class
> is called "Address" and Orion compiled the class
> on the server and called it "Address_Dependent0".
> Obviously, the client isn't going to see that.
>
> My question: Can the client not see dependent objects
> at all? Should I write another Address class and
> copy all the dependent Address class attributes into
> it?
>
> Is this addressed in the spec (I didn't see it)?
> I hope this is how it is supposed to work, I sure hope
> they change it - it seems a huge waste of time to
> have to write 2 classes for each dependent object.
>
> -tim
>
