Ann,
The sentence highlighted below seems to be incorrrect. I'm seekinbg
clarification.
I believe the deployment tools automatically generate all EJB wrapper
methods.
Or are you perhaps referring to the callbacks made into the bean code for
activation, passivation, etc.?
If so, the terminology "wrapper method" seems to be incorrect.
Randy
COMPAQ
> -----Original Message-----
> From: Anne Thomas [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, April 02, 1999 6:38 AM
> To: [EMAIL PROTECTED]
> Subject: Re: EJB, MTS comparison anywhere?
<snip>
> The MTS and EJB component models are very similar. Both work by
> intercepting
> method calls and inserting services based on a set of attributes defined
> at
> deployment time. MTS uses a common wrapper to intercept the method calls
> (the MTS executive, which is called automatically by the COM runtime). EJB
> requires a different set of wrappers for each component type (EJBHome) and
> each component instance (EJBObject).
> EJB component developers need to implement the wrapper methods,
> MTS component developers do not need to
> implement the wrapper methods. MTS is simpler for simple programs, but
> doesn't give you as many options, as many services, or as much control.
> EJB
> allows you more flexibility and it allows you to more easily build more
> complex application systems.
<snip>
===========================================================================
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".
