[JBoss-dev] Optimised Servlet-EJB calls.../ Local Interfaces

2001-11-21 Thread Julian Gosnell


Now that I've read about Local interfaces, I can see
that they are the natural choice for communications
between beans in the same Container.

Is it being suggested that I should use these for
servlet/jsp-ejb communication ?

If not then we still need to support optimised calls
etween the web and ejb container. it is these that
fail between Jetty and JBoss.

If so, then something is wrong. Do I really have to
decide the architecture of my AppServer before I write
my App? It should be transparent.


If optimised calls between web-container and
ejb-container are to be supported, then I still have
ClassLoader issues to be resolved.

Anyone ?


Jules (having a bad day)


__
Do You Yahoo!?
Everything you'll ever need on one web page from News and Sport to Email and Music 
Charts
http://uk.my.yahoo.com

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



Re: [JBoss-dev] Optimised Servlet-EJB calls.../ Local Interfaces

2001-11-21 Thread Rickard Öberg

Julian Gosnell wrote:

 Is it being suggested that I should use these for
 servlet/jsp-ejb communication ?


I would :-)


 If so, then something is wrong. Do I really have to
 decide the architecture of my AppServer before I write
 my App? It should be transparent.


You can write your app so that these issues are transparent, but then 
you need to take alays care of the worst case, which is remote behaviour.

If not, then you are guilty of having believed in the Seven Fallacies of 
Network Computing
(http://wwwtec.informatik.uni-rostock.de/IuK/gk/thm/devdef/Vortrag1/tsld008.htm)

Architecture is rarely transparent, although it is often quite possible 
to *localize* the impact of it to some degree.


/Rickard


-- 
Rickard Öberg


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