Hi!
Manie Coetzee wrote:
> > What I'm mostly worried about is the semantics of using, for example, a
> > transactional bean in a non-transactional setting such as a servlet.
>
> Well, the transactional part is added by using a EJB wrapper.
> If the bussiness logic requires it, it needs to be implemented
> environment independand. If the transactional and security
> model used by the business bean is inconsistent with the environment,
> that functionality needs to be replaced with functionality in the wrapper.
>
> Again, in such a case a piece of bussiness logic can exist in
> a EJB server and at the same time participate in a Jini community.
Right. So if you're not in an EJB container you need to build an EJB
container wrapper.....
....
And the win is..?
IMHO it would be better to let the code be always run in an EJB server,
but allow the components to be exposed as Jini services (which is
trivial fix to do in container invoker: just add the home to a Jini
LUS!).
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
