Seam Beans with Remote and Local EJBs

[jnusaira]

So I have a bean ...

@Name("substanceSetRun")
@Stateful
@Scope(ScopeType.SESSION)
@TransactionManagement(value = TransactionManagementType.BEAN)
@CacheConfig(idleTimeoutSeconds=3600) 
@Local(SubstanceSetRunService.class)
@Remote(SubstanceSetRunRemoteService.class)
public class SubstanceSetRun implements SubstanceSetRunService {
   ... stuff ...
}

... now i have the remote item on there, mainly because we have a remote call to it and all it needs is a small subset of the services. And i'd rather my client not have to update its bean soo often when we make changes to the other items.

However, whats happening now is that that UI components when referencing the Seam bean are referencing the remote instead of the local interface.

Is there anyway to tell the Seam component that it should look at the local first??

[pmuir]

What JNDI binding is Seam using to look up the EJB3 (look in your startup log)?

[jnusaira]

Blah ... never mind.

I think it had to do with me trying to change those local and remote settings and do a hot deploy.

When i took it down (so i could clear the logs) and restarted it worked fine.

Thanks though :)

[andy]

Hi, can you share with us what do you use in your context.xml file? So how did you solve your problem?