Doubt with Seam-managed EJB

[pedrosena]

I'm designing a very large application.

I divided the solution in three parts, where:

ClientA (access) Core
ClientB (access) Core

ClientA, ClientB and Core are three different application, so far so good.

In my core application I'm using EJB and Seam. But today I saw this in documentation:

Seam stateful session bean components may be instantiated using Component.getInstance() or @In(create=true). They should not be directly instantiated via JNDI lookup or the new operator.

Now my question:

How should I access my remote EJB, that is in another application w/o making a lookup ?

Should I avoid Seam in my Core app ?

Thanks in advance,

Pedro Sena

[pedrosena]

Someone?

Regards,

Pedro Sena

[swd847]

You should probably avoid using seam components in your core app. Seam is to closely tied to the web application lifecycle to the point where remote access to an EJB only app does not make sense, as you no longer have a defined SESSION or EVENT scope (there would be many other problems as well).