IMHO, the JBossUserPrincipal has to be serializable. You can't always
assume that the bean invocations from the web tier will be local. Be that
for clustering or whatever. My current project is wide-area distribution
of j2ee apps, where we take an EAR configured to run on a single node and
'stretch' it accross a bunch of nodes, so we end up with having web tier
doing remote invocations on the beans. True, this is non-production
feature and quite inefficient at the moment but that is the whole purpose
of research, to make it better. So, stick to serializable, please.

-------------------------------------------------------------------------
Anatoly Akkerman
Computer Science Dept.
Courant Institute of Mathematical Sciences, NYU
715 Broadway, #719                      Tel: 212 998-3493
New York, NY 10003                      Fax: 212 995-4123
-------------------------------------------------------------------------

On Wed, 2 Jan 2002, Adrian Brock wrote:

> Hi,
> 
> Oops, should have said JRMPInvokerProxy.
> 
> There might still be some bizarre case where it
> needs to go over a wire.
> But, I would have thought the servlet always wants to
> invoke a local bean. That's the whole point of
> web integration isn't it?
> 
> Regards,
> Adrian
> ______________________________________________________________________
> View this jboss-dev thread in the online forums:
> http://jboss.org/forums/thread.jsp?forum=66&thread=6446
> 
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to