I evaluated TOPLink for WebLogic 1.0 Beta 2's CMP. So I
let TOPLink to manage UOW automatically without my coding.
I thought people doing BMP or SB + TOPLink for Java 2.0 should
be OK with TOPLink Sessions, but I have no personal experience
yet, so I can not comment just yet.
cheers
chuck
>Hi Chuck,
>
>Are you using TOPLink (TL) for Java 2.0 or TOPLink for WebLogic? Are you utilizing
UnitOfWork (UOW) within your EntityBeans (EB) or just utilizing TL's Sessions?
>
>I haven't been able to figure out how to set up my EB's to utilize UOW's (because
EB's are shared and by definition, UOW's are one per user).
>
>I've tried to set up the UOW's encapsulated inside a SessionBean (SB) per client,
but don't know how to identify which Client is modifying the EB from the Server
EB.
>
>Any insight would be helpful.
>
>Thanks,
>
>Gary
>
>On Wed, 8 Sep 1999 10:10:33 NZST, Chuck Zheng <[EMAIL PROTECTED]> wrote:
>
>>I have evaluated TOPLink and JavaBlend and consider TOPLink is
>>far superior on following accounts
>>
>>- less intrusive
>>- flexibiity
>>- CMP (anyone use TOPLink CMP EntityBean in large production now?)
>>- all the goodies already mentioned in the list
>>
>>TOPLink's lazy instantiation can be improved as ackownledged by Object People.
>> It is not serious anyway.
>>
>>My favourate TOPLink capability is that it manages relationship
>>from a CMP EB to a dependent object, which has a relationship to another CMP
>>EB, all without a single line of "relationship" code. Does anyone know any
>>other tool can do this?
>>
>>When applying the pattern of Session Bean facade over Entity Beans, if (stateless)
>>Session only receives EB's PK from client,
>>then you have to call EBHome.findBYPrimaryKey() in Session Bean, as expected.
>>
>>
>>cheers
>>chuck
>>
>>
>>>Rudi Vankeirsbilck wrote:
>>>
>>>I agree TOPLink does have some limitations, but they are relatively easy
to
>>live with. And, as has been pointed out before, some of them will disappear
>>with JDK 1.2.
>>>
>>>We have evaluated a number of O-R mapping products and concluded that only
>>TOPLink had all the features we needed. Flexible mapping strategies to allow
>>mapping to a legacy database was one of them. We also found TOPLink was the
>>least intrusive of the tools we looked at.
>>>
>>>As for maturity: I understand TOPLink Java is based on a TOPLink Smalltalk
>>product that had already been used by the Object People for several years.
The
>>Java version GA'd in spring 1998 if I remember well, we have been using it
since
>>then. We _do_ think the product is mature enough.
>>>
>>>My favourite missing TOPLink feature: to be able to generate a TOPLink mapping
>>layer from an XMI file (which in turn can be generated from Rational Rose
and
>>other modellers). I hope the Object People will jump on the XMI bandwagon
soon...
>>
>>>
>>>Regards, Luc Peerdeman.
>>>
>>>===========================================================================
>>
>>>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".
