Well Chris since u responded to my mail with Cocobase -- I want to ask some
questions about this product Cocbase ---
1. Say I am using cmp. Now the containers like weblogic or IAS or gj will
generate the sql code for me quite transparent to me. Now if I use Cocobase
--- for cmp --- what code will it generate?? what I have seen is that it
writes some code -- say within the ejbCreate/ejbRemove/ejbLoad/ejbStore
methods quite unlike the normal cmp beans where within thismethods no code
is written (except for setting the variables in the bean). So when I deploy
such a bean in my container as a cmp --- how does it tell the container not
to do the persistence and that it will do the persistence on its own!!!!
Frankly speaking I think the way any such o/R tool should do their
persistence is tell the actual container (say gj or wls) through DDs that
Cocobase is going to take care of the persistence and then donot write any
code in those methods and do the job. but cocobase dosent seem to behave
like that and Toplink seem to behave like that!
your comments pls
Anamitra
-----Original Message-----
From: Chris Raber [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 04, 2000 4:56 PM
To: [EMAIL PROTECTED]
Subject: Re: Implementing using CMP quickly runs in to limitation...
The Cocobase code generation is template based, so if there is some problem
with the source it generates this can likely be fixed through tweeking of
the code templates. At least this has been my experience in its integration
with GemStone/J.
-Chris.
> -----Original Message-----
> From: Laird Nelson [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, April 04, 2000 2:11 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Implementing using CMP quickly runs in to limitation...
>
> "Bhattacharyya, Ana" wrote:
> >
> > Well I went to that site and there is no mention of support for Weblogic
> > server 5.1!
>
> True. A text search on the string "5.1" does not turn up anything. But
> if you read the site you get several versions of an answer that appears
> to contradict your earlier assertion.
>
> Here is one relevant section:
>
> <citation>
> 1) Full support for EJB 1.0/1.1 and compatibility with an Optimized
> O/R runtime designed to enhance Bean Performance, not slow it down.
> </citation>
>
> (Note explicit reference to EJB 1.1.)
>
> <citation>
> 3) The ability to generate all code needed including standard
> default implementations for the standard EJB Servers such as
> Gemstone/J, Bea Weblogic, WebSpere and IPlanet's Application Server
> </citation>
>
> (Note explicit reference to Bea Weblogic.)
>
> Then, following the "for more click here" link, we get:
>
> <citation>
> - CMP Entity Beans that work with any EJB Server
> By using our CMP Installer Tool, and developers can customize this
> extensible tool for their
> own installation and configuration requirements.
> </citation>
>
> Note mention of "any EJB Server".
>
> 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".
===========================================================================
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".
