This content has been marked as final. Show 3 replies
Lookup in the JNDI tree...by default doesnt requires any Authentication. It means without using the Username & Password Informations u should be able to lookup your EJBs even if it is Located in a Remote Server. You need to pass the Credentials inside the Hashtable ....Only if your have secure the JNDI lookup of your EJBs....Which generally we dont do.
NOTE: Securing JNDI tree for Lookup is not related to EJBs....EJB Layer Security is different from JNDI level security....So using Deployment descriptor Tags <ejb-reference-description> You cannot make your EJB secure , You can just refer to it....For Lookup and access a JNDI tree u need to have Security implemented at JNDI layer...so naturally the JNDI Access/Authentication will be limited to JNDI lookup layer only.....
Even there is NO mapping (Tag) available inside deployment descriptor as part of Tag <ejb-reference-description> ..which can be used.
*<ejb-reference-description>* can be used to refer to an EJB which is deployed on the Same Server...*u CANNOT even use it to access (reference) and EJB which is deployed on a Remote Server.*
</font>... Still if you want to authenticate a User ...before he looks up to the remote EJB ..then u need to provide authentication at the Web Layer.
http://weblogic-wonders.com/weblogic (WebLogic Wonders Are Here)
Thanks Jay ... that's the information I was missing.
Use the mapped name for session bean. The format of the global JNDI name is mappedName#qualified_name_of_businessInterface.
<remote_interface> beanRemote = (<remote_interface>) context.lookup("mappedName#qualified_name_of_businessInterface");