|
Home > Archive > WebSphere Application Server > August 2005 > WAS supports local-jndi-name ?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
WAS supports local-jndi-name ?
|
|
|
| when using xDoclet for EJB, developers can specify both jndi-name and local-jndi-name.
For EJB container like WebLogic and JBoss, they allow use both ejb reference and local-jndi-name for looking up a bean's local home interface.
However, in WAS, no official documents say WAS supports using local-jndi-name for looking up a bean's local home interface. All documents only mentioned using ejb reference to locate local home interface.
Although using ejb reference is more portable, we are now moving application from JBoss to WAS, we still wanna use local-jndi-name in WAS. Is it possible?
| |
| rschnier 2005-08-03, 6:01 pm |
| local-jndi-name is not supported within WAS.
In WAS, the local home is bound into a private location within the namespace patterned using the JNDI name of the remote home. The J2EE-specified way to access the local home is to define an ejb-local-ref within the calling component and use an ejb-link
element to connect this ejb-local-ref to the target bean.
|
|
|
|
|