> Do you have one or multiple interfaces to your app server? We are in the
> situtation that we will have multiple end points for our data: our client,
> third party software, other internal products which want to integrate with
> ours, etc etc.
[Frentress, James] and it's a near certainty that some of that
integration will require you to include parts you don't control into a
single transaction along with the stuff you do control (eg ejb stuff). it's
this requirement that led us to create our "transaction coordinator" and
it's that coordinator that obviated the need for (multiple layers of)
"session-wrappers". it may be argued that session beans could be modified to
handle this integration but i'd counter that this starts to break component
architecture. of course session bean could provide the transaction
coordinator function and it's just this topic that we're discussing in this
thread.
===========================================================================
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".
