> -----Original Message-----
> From: Laird Nelson [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 24, 2000 9:25 PM
> To: [EMAIL PROTECTED]
> Subject: Re: downcast / EJB-Inheritance
>
>
> Evan Ireland wrote:
> > I would have thought that PortableRemoteObject.narrow would
> be required to work
> > in this case. But I wouldn't mind hearing the official
> position on this. Perhaps
> > it is only required that this work when narrowing the home
> reference returned
> > by a JNDI lookup.
>
> Boy, that would be nice. I don't have a project set up where
> this is a
> problem and I'm too lazy to go set one up to test this. :-)
> Has anyone
> successfully gotten this to work? If PortableRemoteObject.narrow()
> exists to solve this problem, that would be terrific. My
> sense is that
> it's a bit, um, er, narrower than this.
>
it depends on the CMP engine. with the most cmp engines if you're using a
finder method from Person you just get a collection of persons and narrow
doesn't work. But there are some cmp engines which autmatically maps the
necessary inheritance information to the DB. With that information they're
able to create SmartPersons even if you're using a finder method in
PersonHome (and then narrow works fine). AFAIK Persistence Powertier is able
to do that (and OR-Mapping tools like Toplink or Avantis should also).
> {FX: ducks}
>
> Cheers,
> Laird
>
> ==============================================================
> =============
> To unsubscribe, send email to [EMAIL PROTECTED] and
> include in the body
> of the message "signoff EJB-INTEREST". For general help,
> send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
