Manisha,
I don't see a problem with your requirement.
Can't you just code ejbLoad accordingly? I am assuming that
since you want to do additional SQL during update that container
manager persistence is out the door.
-Chris.
----------------------------------------------------------------------
Chris Raber, Director Professional Services, GemStone Systems Inc.
100 West Big Beaver, Suite 200, Troy, MI 48084
phone: (248)-680-6691, fax: (248)-680-6689,
email: [EMAIL PROTECTED]
web: http://www.gemstone.com/
----------------------------------------------------------------------
> -----Original Message-----
> From: Manisha Umbarje [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, June 24, 1999 1:54 PM
> To: [EMAIL PROTECTED]
> Subject: design issue
>
> Hi All,
>
> I have few entity Beans which correspond to DB records .
>
> I have few rules to be executed before executing every Insert, Delete and
> Update statement.
>
> for eg. For Update :
>
> Read record from Db
> Do something
> Create "Update SQL stmt" with new values
> Read the same record again
> Do something
> execute Update
>
>
> Can I implement these rules in a bean,let's say "RulesBean", so that
> before
> executing any SQL statment, every bean will execute methods of this
> RulesBean ?
>
> But the problem here is certain SQL statements have to be executed as part
> of
> the Rules.
> It's not just business logic.
>
>
> Any Suggestions ?
> Manisha
>
> ==========================================================================
> =
> 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".
