Help on the separate deployment of .war and .jar files of a Seam project using remote EJBs

[apbarraza]

I need to develop a JEE project using Seam where the .war file is deployed in tomcat and .jar file is deployed in JBoss. I’m really new to JEE and Seam, so I really don’t have a clear idea of how this would be done. After searching for a tutorial or any kind of help, I am under the impression that using remote EJBs with Seam causes problems with injection and seam contexts in general, and that there really isn’t an out-of-the box simple way of communicating separately deployed .war and .jar projects using Seam. In perspective I’m just lost with the whole subject; could anybody please help me find a tutorial or something that might help me at least to see a little light? I need to solve this as soon as possible so any help is greatly appreciated. Thanks in advance.

[lvdberg]

Hi Andrea,

because of performance problems we just separeted a system over different physical systems, without loosing the benefits of Seam. What we baically did was to run the inter-application communication over JMS. It takes some effort, but JMS is very well supported and can be run also in a semi-J2EE environment as Tomcat.

Leo

[apbarraza]

Thanks, but I need to use remote EJBs (or something that uses RPC) and consider performance...
I was reading around and all I can find is Seam Remoting... would this be the way to go even though it is not exactly remote EJBs?
I would really prefer to use remote EJBs, so i'm still stuck.

[lvdberg]

Hi,

It really depends on your requirements, but there are severeal ways to remotely use your EJB's For instance you couldpeek at the possibilities of RestEasy which is nicely integrated with Seam. We've done several projects with combined producer and consumer use of services with RestEasy. Works definitely better and musch easier to develop than Soap based WS or remote EJB-access.

Leo

[apbarraza]

Thanks. But again I have been reading and RestEasy is basically web services so this would not be the way to go :(

[lvdberg]

Hi,

I would love to help, but you basically reject every possibility if it's not direct remote access to EJB. I can only see this need if the EJB machine is already existing in the company and you need to create an additional Web-Layer. If its an architectural choice for a totally new project (web plus EJB) I would really re-consider such a choice.

You have to understand that Seam (maybe just for now) is not able to proxy something which is not running in the same JVM on the same machine or in another machine. Web access to remote beans is horribly slow compared to local access, because of their proxies and in addition you will have all the nice firewall features to cope with.

However nothing stops you from writing a simple POJO (Seam intercepted) service access layer which in its turn accesses the remote EJB's. 

Leo