Hi Swaminathan,

I'm working on a project at the moment where we are facing the same issues. We are 
replacing a system that had lots of functionality that is in place in stored 
procedures. Our problem is that we are replacing just one of a number of applications 
and some of the others are still relying on the functionality provided by the stored 
procedures.

Our solution to this is to create session beans that wrap up the database 
functionality, calling the stored procedures jusing JDBC. In front of this we are 
providing a nice interface using the session facade pattern.

This allows us to build the application quickly as we are not re implementing the 
functionality. Also later when (or maybe if) all the applications are migrated to the 
J2EE architecture we could migrate the business logic into the EJB architecture 
without needed to update the applications as everything is hidden behind session 
facades.

Hope that this helps

Regards
IV



>  from:    "Swaminathan K.N." <[EMAIL PROTECTED]>
>  date:    Mon, 01 Jul 2002 07:15:00
>  to:      [EMAIL PROTECTED]
>  subject: Re: Calling a SP from Entity bean
>
> Hello All,
>
>
>         Can anyone tell me the reason for calling a Stored Procedure from a
> Entity Bean ( CMP or BMP ) assuming some business logic is there in Stored
> Procedure. Does it make sense??
>
>         Assuming the existing business logic is available in a Stored
> Procedure, What is the approach to be taken to move the business logic to
> the Session bean as much as possible?. Should we leave some of the business
> logic in SP itself?
>
>
>
> Regards,
> Swaminathan
> ****************************************************************************
> This communication contains information, which is confidential and may also
> be privileged. It is for the exclusive use of the intended recipient(s). If
> you are not the intended recipient(s), please note that any distribution,
> printing, copying or use of this communication or the information in it is
> strictly prohibited. If you have received this communication in error,
> please notify the sender immediately and then destroy any copies of it.
> ****************************************************************************
>
> ===========================================================================
> 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".
>



http://www.amazon.co.uk/exec/obidos/redirect-home?tag=velloscouk-21&placement=home_multi.gif&site=amazon

===========================================================================
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".

Reply via email to