That makes sense, but the current MessageDrivenContainer is the one that
does implement the ContainerInvokerContainer interface and then decides
to void the contract by throwing Errors.
----- Original Message -----
From: "Rickard Öberg" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 09, 2001 10:57 PM
Subject: Re: [JBoss-dev] Why doesn't Container implment
ContainerInvokerContainer?
> Scott M Stark wrote:
> > Another issue is why doesn't the Container class implement
> > ContainerInvokerContainer? This
> > is the assumed behavior as evidenced by the prevelance of unsafe
downcasts
> > scattered
> > throughout the container invoker code:
>
> The reason for the separation is(was at least) that MDB's aren't
> ContainerInvoker-invokable, i.e. they have no remote interface and such.
>
> /Rickard
>
> --
> Rickard Öberg
> Software Development Specialist
> xlurc - Xpedio Linköping Ubiquitous Research Center
> Author of "Mastering RMI"
> Email: [EMAIL PROTECTED]
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
