> > 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 ?
Yep, but that is in the J2EE spec not the Servlet or ejb specs. > If not then we still need to support optimized calls > between 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. The trick is if you think you may want in VM optimized calls you can not rely on the pass by value style method calls. This means don't use Object parameters as temp variables. Later on you can switch to Local interfaces for speed. Alternatively, you could start with local interfaces and then switch to remote if you want to move the web layer to another vm. This has a similar issue regarding by reference parameters. You can't rely on updated parameters being reflected in the web layer. > If optimized calls between web-container and > ejb-container are to be supported, then I still have > ClassLoader issues to be resolved. Whey have to be in an EAR with class-path refs properly set in the manifest.mf file. This is documented in either the J2EE spec or the EJB spec. -dain _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
