Well, I feel that an unstated assumption here is that the SQL
programmers take good care in writing only portable SQL, especially for
an entity bean that has complex data structures. I question this
assumption.
I understand the argument that even if the SQL that the programmer
writes is not portable, it is relatively easy to port since a human
wrote the code (assuming that the same person is porting it). But we all
know, how greek our own code appears when we look at it even a couple of
months later.
My feeling is that as long as you stick with the same O/R tool vendor,
your beans will port fine. I would even argue that even if you change
vendors, as long as the new vendor implement the O/R mappings correctly
(through differently), the process will be easier than what a human
porting will involve.
thanks
inder
Chris Raber wrote:
>
> It is, but because the spec is not tight enough in the area of CMP, CMP
> beans are not as portable.
>
> Session Beans and BMP port just fine.
>
> -Chris.
>
> > -----Original Message-----
> > From: RVASUDEV [SMTP:[EMAIL PROTECTED]]
> > Sent: Wednesday, November 10, 1999 12:54 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Container supported persistence... mapping?
> >
> > > -----Original Message-----
> > > From: Anne Thomas [SMTP:[EMAIL PROTECTED]]
> > > Sent: Wednesday, November 10, 1999 5:18 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: Container supported persistence... mapping?
> > >
> > >
> > [VR] I thought the portability of EJBs
> > between different EJB servers was the key
> > benefit of EJB ?
> >
> > > relational tables. The downside to the Persistence approach is that the
> > > entity beans that you develop with PowerTier are not portable to other
> > EJB
> > > implementations.
> > >
> > > Anne
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Robert Nicholson [mailto:[EMAIL PROTECTED]]
> > > Sent: Tuesday, November 09, 1999 12:30 AM
> > > Subject: Container supported persistence... mapping?
> > >
> > >
> > > With the EJB projects that currently support container supported
> > > persistance. I assume sybase's and oracle's do. How is the mapping
> > > b/w the persistence properties of the bean and the schema of the
> > database
> > > specified?
> > >
> > > Is schema generated from class definitions of the bean?
> > >
> > >
> > ==========================================================================
> > > =
> > > 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".
>
> ===========================================================================
> 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".
