JNDI name in J2EE

I am trying to get an object using the JNDI name.
The problem i face is such that the i don't really know the full path of the JNDI name of my beans in J2EE. And i would hope to know how to remotely access a object using JNDI name on a J2EE server in the same network.
InitialContext ic = new InitialContext();
Object objRef = ic.lookup (JNDIname);
And is this the correct way to access an object locally using JNDI name?

InitialContext ic = new InitialContext();
Object objRef = ic.lookup (JNDIname);
And is this the correct way to access an object
locally using JNDI name?Locally, this should be fine! However, if you want to access from a remote client, you would need to specify the environment properties to the InitialContext constructor.

Similar Messages

How to Set the JNDI name in J2EE 1.4 ??

Hello,
I am sure i am have done everything right except for the JNDI name ! I have recently shifted to J2EE 1.4. I was using j2EE 1.2.
So kindly tell me how should i set me JNDI name in the deploytool.
Here is the exception i got when i tried to run my application without having set any JNDI name !!
http://img220.imageshack.us/img220/832/hellodt5.gif
Thanks.

There are 2 types of descriptors:
standard and portable deployment descriptors (e.g. ejb-jar.xml, web.xml, application.xml, etc)
vendor specific deployment plan (e.g., sun-ejb-jar.xml, sun-web.xml, sun-application.xml, jboss.xml, weblogic.xml, etc)
When you are developing ejb apps with glassfish, or JavaEE SDK, or Sun Java System Application Server, you usually package all descriptors in META-INF directory inside the jar.
You can also create portable apps that do not contain any vendor specific deployment plans. So you can deploy it to any appserver. At deployment time, you then specify an option to pass the deployment plan to deploy tool. This is required by JSR 88 and all J2EE- or JavaEE-compliant appserver must support this.
In Glassfish, JavaEE SDK, or SJSAS, you can:
$SJSAS_HOME/bin/asadmin deploy --deploymentplan /tmp/deploy-plan.jar /tmp/my-ejb.jar
where /tmp/deploy-plan.jar is a jar file containing sun-ejb-jar.xml for the deployable ejb-jar:
jar tvf deployment-plan.jar
0 Thu Oct 12 11:55:00 EDT 2006 META-INF/
106 Thu Oct 12 11:54:58 EDT 2006 META-INF/MANIFEST.MF
570 Thu Oct 12 11:55:00 EDT 2006 sun-ejb-jar.xml

JNDI name tab not present in J2EE RI ,Deploy tool

I have dowlaoded the J2EE server RI.i have created new applications using the deploytool, but was unable to find the JNDI name Tab as per the tutorials.
Can any one help me in figuring out the problem.Let me know what might be wrong with the "deploytool".
Thanks in advance
Ravi

Someone finally found this one (Farhan I think) - I hope you can find this link: its in this forum - just a few weeks old do a search on jndi on this forum if you don't find it.
http://forum.java.sun.com/thread.jsp?forum=136&thread=321971&start=15&range=15&hilite=false&q=

Jndi-name javax.naming.NameAlreadyBoundException:

Hi,
I am getting the following error while deploying a CMP Bean. Initially
this started to deploy, but later when I recompiled the source files
and tried to deploy again, I get the following errors.
In fact I am tired of trying to see what's actually happening.
Your immediate response is highly appreciated.
thanks and regards,
F S Joseph
Unable to deploy EJB: country from Country.jar:
weblogic.ejb20.WLDeploymentException: Unable to bind EJB Home
Interface to the JNDI name: ejb.CountryHome. The error was:
javax.naming.NameAlreadyBoundException: Failed to bind remote object
(ClusterableRemoteRef(127.0.0.1
null)/292     [cashnet.ejb.CountryHome+javax.ejb.EJBHome+weblogic.ejb.QueryHome+weblogic.ejb20.interfaces.QueryHandler+weblogic.ejb20.interfaces.RemoteHome])
to replica aware stub at CountryHome(ClusterableRemoteRef(127.0.0.1
[127.0.0.1/291])/291     [cashnet.ejb.CountryHome+javax.ejb.EJBHome+weblogic.ejb.QueryHome+weblogic.ejb20.interfaces.QueryHandler+weblogic.ejb20.interfaces.RemoteHome]);
remaining name 'ejb'
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
     at weblogic.jndi.internal.ServerNamingNode_WLStub.bind(Unknown
Source)
     at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:359)
     at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:353)
     at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:951)
     at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1302)
     at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:342)
     at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1509)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:970)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:957)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1074)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:700)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
     at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:956)
     at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1302)
     at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:342)
     at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1509)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:970)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:957)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1074)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:700)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
failed application Country on cashnetserver

there is already an ejb with this name!
this is set in weblogic-ejb-jar.xml
Ronak Parekh wrote:
Unable to deploy EJB: OrganizationEJB from sempire_bc.jar:
Unable to bind EJB Home Interface to the JNDI name: Organization. The error
was:
javax.naming.NameAlreadyBoundException: Organization is already bound;
remaining
name 'com.sempire.builder.business_component'
<<no stack trace available>>

Problem with Database JNDI Name

I have written an entity bean & tring to deploy it with CMP 1.0
I have already included classes12.jar in my classpath.
(I am using Oracle database)
I have specified driver & datasource as follows
j2eeadmin -addJdbcDriver oracle.jdbc.driver.Driver
j2eeadmin -addJdbcDataSource jdbc/Oracle jdbc:oracle:[email protected]:1521:listorcl
When I tried Deployment Settings I have given following specs
Database JNDI Name : jdbc/Oracle
User : username
Password : password
When I click on Generate SQL Now or Generate Default SQL the following exception occurs .
NameNotFoundException : Oracle__pm not found
Note : The J2EE server & Database Server are running.
Pl Help Me.
Thanks In Advance

mmm I will try to explain it better:
1) long time ago I created my account SDN, in "kind of relationship with SAP option", I indicated "partner" (i work for consulting company, SAP partner), and register in the form our S000... number.
2) From there, I login SDN with my personal mail, and in my profile my data OK and like SAP partner.
3) from a few months ago, when I try to login using my ma.il as usual, I get an error message:
The email address does not exist. and that I must enter you user S000 ....
4) but when I login user our S000.. (such as SAP partner), "Ariela" data appears (who is my boss), because she is the comercial contact person with SAP, and she manage the S000 account
5) the history, posts, points and others are mine (Leandro Balboni);
6) but I do not want is to change this profile, because in this way would be modifying the data responsible for the SAP account as a partner.
7) I wonder if I can still loing SDN as before, perhaps must not indicate "partner", but simply put the name of my company.
8) how can I fix it?
thanks in advance,
best regards,
Leandro
Edited by: Ariela Mara Fefer on Aug 25, 2009 1:03 PM

Mapping of logical resource-name to absolute jndi-name for data source

Hi,
I am using SJS AS 8.1. I do a lookup for datasource using logical name specified in ejb-jar.xml using resource-ref element as below :
<resource-ref>
        <res-ref-name>jdbc/db-resource</res-ref-name>
        <res-type>javax.sql.DataSource</res-type>
        <res-auth>Container</res-auth>
        <res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>jdbc/db-resource is mapped to absolute jndi name 'jdbc/jndi-db-resource' in sun-ejb-jar.xml as below :
<resource-ref>
        <res-ref-name>jdbc/db-resource</res-ref-name>
        <jndi-name>jdbc/jndi-db-resource</jndi-name>
</resource-ref>I have configued data source using admin GUI with JNDI name jdbc/jndi-db-resource. When I do a look up of datasource as below :
initalContext.lookup("jdbc/db-resource"); from the EJB I get NameNotFoundException. How do I configure logical datasource name using admin GUI ?
Thanks,
Manisha.

Hi Manisha,
When doing a lookup of standard j2ee connection factories like jms or jdbc "java:comp/env" need to be prefixed.
initalContext.lookup("jdbc/db-resource");
need to be
initalContext.lookup("java:comp/env/jdbc/db-resource");
For more information :
http://docs.sun.com/source/819-0079/dgjndi.html#wp24616
Thanks,
-Jagadish

Dynamic jndi-name in weblogic-ejb-jar.xml

Is there a way to create dynamic (i.e. runtime) jndi-names for EJBs instead of
(or in addition to) "hard coding" them in the weblogic-ejb-jar.xml file? What
I'm trying to do is have one WebLogic instance (JVM) host multiple environments
(our Beta and Training environments) and I simply want to deploy the same .ear
file twice but have each environment (application - .ear) reference a different
database schema (jdbc connection pool). I have everything working just fine for
this scenario except when I define jndi-names for our ejbs. The problem is that
I am really deploying the same ejbs (jndi-names and actually code base) in each
applicatoin instance and I get an exception when the WebLogic is trying to deploy
the second application (.ear) because the jndi-names in it have already been deployed
by the first application instance. I recieve a jndi error stating that the name
is already deployed.
Or is there a better path to go down for what I am trying to do to have one WebLogic
instance support our beta and training environments? Usually (but not always)
our code base is the for same for both of these environments, I simply need to
have each environment use a different database schema.
Thanks

A little birdie tells me that BEA does this very thing. Looking at the
descriptors for WebLogic Portal I see:
<weblogic-enterprise-bean>
<ejb-name>LoaderEJB</ejb-name>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>${APPNAME}.BEA_content.LoaderHome</jndi-name>
</weblogic-enterprise-bean>
Yes, the ${APPNAME} token really is expanded into the J2EE application
name at deployment time!
Sincerely,
Daniel Selman
Bryan Dixon wrote:
Rewriting our build process isn't really much of an option for me. Our current
build process is too complex and time consuming right now to convert to Ant (we
eventually will do this but not for a while). So are there any other ideas that
aren't build related?
Thanks
"Eric Ma" <[email protected]> wrote:
You don't need run-time dynamism in JDNI names and it can't be done anyways.
You
need token substitution in XML configuration files when building the
app. If
you are using Ant for building, then it is a breeze. If not, first convert
your
build process to use Ant.
Also, a single WLS instance hosting multiple environments sounds really
INTRIGUING
to me.
Eric Ma
"Bryan Dixon" <[email protected]> wrote:
Is there a way to create dynamic (i.e. runtime) jndi-names for EJBsinstead
of
(or in addition to) "hard coding" them in the weblogic-ejb-jar.xml file?
What
I'm trying to do is have one WebLogic instance (JVM) host multiple environments
(our Beta and Training environments) and I simply want to deploy the
same .ear
file twice but have each environment (application - .ear) referencea
different
database schema (jdbc connection pool). I have everything working just
fine for
this scenario except when I define jndi-names for our ejbs. The problem
is that
I am really deploying the same ejbs (jndi-names and actually code base)
in each
applicatoin instance and I get an exception when the WebLogic is trying
to deploy
the second application (.ear) because the jndi-names in it have already
been deployed
by the first application instance. I recieve a jndi error stating that
the name
is already deployed.
Or is there a better path to go down for what I am trying to do to have
one WebLogic
instance support our beta and training environments? Usually (but not
always)
our code base is the for same for both of these environments, I simply
need to
have each environment use a different database schema.
Thanks

Problem in setting up jndi name in servlet

hi,
I am using netbeans6.8, glassfishv3 with mysql5.1. I set up a new jdbc Resource & connection pool by using the glassifsh admin console, and associated the connection pool with jdbc resource
when i ping the status of the connection pool , it is success.
Following is the lines added from my config.xml file in glassfish domain
<jdbc-resource pool-name="knockknock_poool" description="For connecting with knockknock for testing" jndi-name="jdbc/knockknock" />
<jdbc-connection-pool datasource-classname="com.mysql.jdbc.jdbc2.optional.MysqlDataSource" max-pool-size="250" res-type="javax.sql.DataSource" steady-pool-size="32" description="pool for contains connection to connect with knockknock" name="knockknock_poool" non-transactional-connections="true" ping="true">
<property description="jdbcname" name="URL" value="jdbc:mysql://localhost:3306/knockknock" />
<property description="knockknock" name="databaseName" value="knockknock" />
<property description="knockknock" name="datasourceName" value="knockknock" />
<property description="tcp" name="networkProtocol" value="tcp" />
<property description="admin" name="password" value="admin" />
<property description="3306" name="portNumber" value="3306" />
<property description="localhost" name="serverName" value="192.168.2.36" />
<property description="root" name="user" value="root" />
</jdbc-connection-pool>
My DB name is knockknock & jndi name of datasource is jdbc/knockknock and ping status is true
when i try to make a datasource lookup from my servlet i am getting the following exception
javax.naming.NamingException: Lookup failed for 'jdbc/knockknock' in SerialContext [Root exception is javax.naming.NameNotFoundException: knockknock not found]
at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:442)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at knockingvideopackage.NewRegistration.init(NewRegistration.java:50)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1428)
at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:1073)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:187)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:188)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:641)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:97)
at com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:85)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:185)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:332)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:233)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:165)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309)
at java.lang.Thread.run(Thread.java:619)
Caused by: javax.naming.NameNotFoundException: knockknock not found
at com.sun.enterprise.naming.impl.TransientContext.doLookup(TransientContext.java:197)
at com.sun.enterprise.naming.impl.TransientContext.lookup(TransientContext.java:168)
at com.sun.enterprise.naming.impl.TransientContext.lookup(TransientContext.java:172)
at com.sun.enterprise.naming.impl.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:58)
at com.sun.enterprise.naming.impl.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:101)
at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:430)
... 28 more
and my servlet code is
@Override
public void init(ServletConfig config)
try {
InitialContext ctx = new InitialContext();
// ctx.bind("java:comp/env/jdbc/knockknock", ctx);
if(ctx == null )
try {
throw new Exception("Boom - No Context");
} catch (Exception ex) {
Logger.getLogger(NewRegistration.class.getName()).log(Level.SEVERE, null, ex);
DataSource ds = (DataSource)ctx.lookup("java:comp/env/jdbc/knockknock");
try {
con = ds.getConnection();
} catch (SQLException ex) {
Logger.getLogger(NewRegistration.class.getName()).log(Level.SEVERE, null, ex);
} catch (NamingException ex) {
Logger.getLogger(NewRegistration.class.getName()).log(Level.SEVERE, null, ex);
i believe that what i am doing is correct from this document of mysql
http://dev.mysql.com/doc/refman/5.1/en/connector-j-usagenotes-j2ee.html
But i cannot understand what is the problem. any help is appreciated
thanks

Hello there.
Here's the ServiceLocator and delegates I am using....
// LoginDelegate.as
package com.myproj.products.business {
     import com.myproj.products.vo.LoginVO;
     import mx.rpc.IResponder;
     import com.adobe.cairngorm.business.ServiceLocator;
     public class LoginDelegate {
          // anything that implements the IResponder interface can act as a responder
          private var responder:IResponder;
          private var service:Object;
          public function LoginDelegate(responder:IResponder) {
               this.responder = responder;
               this.service = ServiceLocator.getInstance().getRemoteObject("loginService");
          public function login(loginAttempt:LoginVO):void {
               // Call the method of service that resides on server
               var call:Object = service.login(loginAttempt);
               // Send the response to responder
               call.addResponder(responder);
// com/myproj/products/business/Services.mxml
<?xml version="1.0" encoding="utf-8"?>
<cairngorm:ServiceLocator
     xmlns:mx="http://www.adobe.com/2006/mxml"
        xmlns:cairngorm="com.adobe.cairngorm.business.*">
     
     <mx:RemoteObject
          id="loginService"
          destination="zend"
          source="LoginService"
          showBusyCursor="true">
          <mx:method name="doLogin" />
     </mx:RemoteObject>
</cairngorm:ServiceLocator>
With kind regards
ShiVik

The DataSource with the JNDI name: MyDataSource could not be located.

hi,
I created a connection pool myconnectionpool and i create a data source MyDataSource with jndi name as mydsn.
in my weblogic-cmp-rdbms-jar.xml i gave
<data-source-name>MyDataSource</data-source-name> and
When i deploy the bean i am getting following exception.
Unable to deploy EJB: containerManaged from cmp7.jar:
weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: MyDataSource could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
     at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:128)
     at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:213)
     at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:185)
     at weblogic.ejb20.manager.DBManager.setup(DBManager.java:160)
     at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:928)
     at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1216)
     at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:850)
     at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:70)
     at weblogic.j2ee.Application.addComponent(Application.java:253)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:144)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:301)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:255)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:206)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:716)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:698)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:380)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:902)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:480)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:208)
     at $Proxy34.updateDeployments(Unknown Source)
     at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:3724)
     at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1584)
     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:337)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:233)
     at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:61)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:852)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:273)
     at weblogic.Server.main(Server.java:33)
Where i went wrong?
Thanks in advance
phani

Hi ,
I have the same problem .when i look into JNDI tree view the jndi name is listed. but it saying error below listed.
my
ejb-name:=containerManaged
datasourcename=EX_DataSource
jndi-name=EX_JNDI
<Feb 14, 2005 3:10:08 PM IST> <Error> <Deployer> <149231> <The slave deployer was unable to set the activatio
true for the application EX_Container
weblogic.management.ApplicationException: activate failed forEX_Container
Module Name: EX_Container, Error: Exception activating module: EJBModule(EX_Container,status=PREPARED)
Unable to deploy EJB: containerManaged from EX_Container.jar:
The DataSource with the JNDI name: EX_DataSource could not be located. Please ensure that the DataSource has
ed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
TargetException:
Unable to deploy EJB: containerManaged from EX_Container.jar:
The DataSource with the JNDI name: EX_DataSource could not be located. Please ensure that the DataSource has
ed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1093)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1022)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:376)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLife
ava:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:65)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:832)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:300)
at weblogic.Server.main(Server.java:32)
my weblogic-ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB//EN'
'http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>containerManaged</ejb-name>
<entity-descriptor>
<persistence>
     <persistence-use>
     <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
     <type-version>7.0</type-version>
     <type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
     </persistence-use>
</persistence>
</entity-descriptor>
<jndi-name>EX_JNDI</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
<?xml version="1.0"?>
<!DOCTYPE weblogic-rdbms-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB RDBMS Persistence//EN'
'http://www.bea.com/servers/wls700/dtd/weblogic-rdbms20-persistence-700.dtd'>
weblogic-cmp-rdbms-jar.xml file
<weblogic-rdbms-jar>
<weblogic-rdbms-bean>
<ejb-name>containerManaged</ejb-name>
<data-source-name>EX_DataSource</data-source-name>
<table-map>
<table-name>ejbAccounts</table-name>
<field-map>
<cmp-field>accountId</cmp-field>
<dbms-column>id</dbms-column>
</field-map>
<field-map>
<cmp-field>balance</cmp-field>
<dbms-column>bal</dbms-column>
</field-map>
<field-map>
<cmp-field>accountType</cmp-field>
<dbms-column>type</dbms-column>
</field-map>
</table-map>
</weblogic-rdbms-bean>
<create-default-dbms-tables>DropAndCreateAlways</create-default-dbms-tables>
</weblogic-rdbms-jar>
ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC
"-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
"http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<entity>
<ejb-name>containerManaged</ejb-name>
<home>containerBN.EX.AccountHome</home>
<remote>containerBN.EX.Account</remote>
<ejb-class>containerBN.EX.AccountBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>AccountBean</abstract-schema-name>
<cmp-field>
<field-name>accountId</field-name>
</cmp-field>
<cmp-field>
<field-name>balance</field-name>
</cmp-field>
<cmp-field>
<field-name>accountType</field-name>
</cmp-field>
<primkey-field>accountId</primkey-field>
<query>
<query-method>
<method-name>findBigAccounts</method-name>
<method-params>
<method-param>double</method-param>
</method-params>
</query-method>
<ejb-ql>
<![CDATA[SELECT OBJECT(a) FROM AccountBean AS a WHERE a.balance > ?1]]>
</ejb-ql>
</query>
<query>
<query-method>
<method-name>findAccount</method-name>
<method-params>
<method-param>double</method-param>
</method-params>
</query-method>
<ejb-ql>
<![CDATA[SELECT OBJECT(a) FROM AccountBean AS a WHERE a.balance = ?1]]>
</ejb-ql>
</query>
<query>
<query-method>
<method-name>findNullAccounts</method-name>
<method-params>
</method-params>
</query-method>
<ejb-ql>
<![CDATA[SELECT OBJECT(a) FROM AccountBean AS a WHERE a.accountType IS NULL]]>
</ejb-ql>
</query>
</entity>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>containerManaged</ejb-name>
     <method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
<ejb-client-jar>EX_Container.jar</ejb-client-jar>
</ejb-jar>
pls lhelp me .
my email id: [email protected]
thanks in advance.
Sudhakar.M

WLS10.3.1 : How to overload the jndi name of a stateless EJB

Hi,
I am trying to overload the jndi name of a stateless bean defined in an application by using a weblogic-ejb-jar.xml descriptor file.
This does not work.
The ear contains a jar that have a weblogic-ejb-jar.xml file in its META-INF directory. The file is :
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar
xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>HelloWorldBean</ejb-name>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>TOTO</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
This is the code of my bean :
package test;
import javax.ejb.Local;
import javax.ejb.Remote;
import javax.ejb.Stateless;
@Stateless( name = "HelloWorldBean", mappedName="HWBean")
@Local( IHelloWorldLocal.class)
@Remote( IHelloWorldRemote.class)
public class HelloWorldBean implements IHelloWorldLocal, IHelloWorldRemote
public void sayHello(String name) {
System.out.println( "Hello " + name + "!!!!");
The bean implements the following interfaces :
package test;
public interface IHelloWorldRemote extends IHelloWorld {
package test;
public interface IHelloWorldLocal extends IHelloWorld {
package test;
public interface IHelloWorld {
public void sayHello( String name);
When i browse the JNDI tree, i see the bean registered with the mapped name attribute (HWBean#test.IHelloWorldRemote) but i don't see any bean registered with the name provided by the weblogic-ejb-jar.xml (TOTO)
My standalone client can't perform a lookup using the JNDI name 'TOTO' but reaches the bean when using 'HWBean#test.IHelloWorldRemote'
It seem's that the overload of the Jndi name using the weblogic-ejb-jar file descriptor doesn't work.
Can you help me to solve the problem.
Thanks.

Thank you, my sample works fine with the following weblogic-ejb-jar.xml :
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>HelloWorldBean</ejb-name>
<enable-call-by-reference>true</enable-call-by-reference>
<stateless-session-descriptor>
<business-interface-jndi-name-map>
<business-remote>test.IHelloWorldRemote</business-remote>
<jndi-name>TOTO</jndi-name>
</business-interface-jndi-name-map>
</stateless-session-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>

Changing JNDI-name

I'm doing an exercise from SAMS Teach yourself J2EE in 21 days, and I'm stuck allready on day 4.
The exercise uses an example from the book. In short:
An EJB that returns some information registers in the JNDI as "ejb/Agency"
A client application looks up "java:comp/env/ejb/Agency" and retrives the informtion for the EJB and prints it.
I've got the application working, and everything is fine and dandy, until I'm stuck at exercise 4:
"Try changing the name under which the EJB is reistered in the JNDI using "deploy-tool". Change the JNDI name used by your client to find the Agency EJB and make sure that it still works"
The first thing I did was to change the name of the EJB (under sun spesific settings) in deploytool, redeploy the EJB and make sure that It did'nt work (just to make sure that the change had taken effect).
Then I edited my SimpleClient.java to match the new name, recompiled it and ran it. (It did'nt work of course).
I soon figured out that the file i actually ran was the jar.file returned upon deployment from deploytool, and that my change had not propagated to this file yet. I redeployed the application and explicitly retrived the jar file afterwards, but it still did'nt work.
I'm not sure where the problem is, but I expect it to be in my understanding of how the different files are treated by the deploytool, and that my changes to the client-file in fact has not been propagated at all. (I'm actually quite sure of this, since leaving the sun spesific settings as they were, and changing my SimpleClient.java/class does not give any errors).
One thing that puzzels me is how I need the jar-file that is returned upon deployment to compile my client-file whille at the same time it's this jar-file I afterwards run to start my client.
Any suggestions, enlightning information or other help is much appreciated.

I've about determined that deploytool is about the worst thing you could use when learning J2EE. When I was first working with ejb's I tried using that thing, and getting up to speed took far longer than it should have. Once I ditched that crappy 'tool' and spent a day messing with the xml descriptors everything started to make sense.
Deploy tool could be nice, but I find it far more a hinderance than a help.

Could not deploy an JAR archive because JNDI name is already in use.

Hi,
I have a problem.
When the WebLogic server starts, it cannot deploy an EJB application because a
JDNI name is already in use.
What can I do to unregister this name ?
If it is possible a better description is step by step.
The WebLogic server, when starts, prints the next lines:
<18/01/2002 12:35:24 PM GMT-06:00> <Error> <J2EE> <Error deploying EJB Component
: sui_ejb
weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB; nested exc
eption is:
javax.naming.NameAlreadyBoundException: Can't rebind anything but a repl
ica-aware stub to a name that is currently bound to a replica-aware stub; remain
ing name ''
javax.naming.NameAlreadyBoundException: Can't rebind anything but a replica-awar
e stub to a name that is currently bound to a replica-aware stub; remaining name
<<no stack trace available>>
>
<18/01/2002 12:35:24 PM GMT-06:00> <Error> <J2EE> <Error deploying application
s
ui_ejb: Could not deploy: 'sui_ejb.jar': JNDI name in use
>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer> <WebLogic Server
st
arted>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer> <ListenThread liste
ning on port 7001, ip address 157.253.174.63>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer> <SSLListenThread
li
stening on port 7002, ip address 157.253.174.63>
In advance, thanks for your help.
- Ricardo De la Rosa (Colombia)

Cameron,
I resolve the problem using your clues.
The problem was that I include the ejb.jar file in the .ear file and I copy the
ejb.jar file in the applications directory and it is redundant.
It is only needed to include the ejb.jar file in the .ear file.
Best regards,
- Ricardo (Colombia)
"Cameron Purdy" <[email protected]> wrote:
In that case, check the config.xml and make sure that the app isn't being
deployed in ways that you weren't expecting ... just double-check
everything. Sometimes the console does weird things.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Ricardo De la Rosa" <[email protected]> wrote in message
news:[email protected]...
Cameron,
I think that it isn't the problem because yesterday it deploys correctly,and
today I didn't touch the compilation options.
Thank you !
If you have another idea I really appreciate it.
Best regards,
- Ricardo (Colombia)
"Cameron Purdy" <[email protected]> wrote:
Hi Ricardo,
Certain items are not replica-aware, such as JMS queues, so they must
be
deployed to a single target in the cluster. It sounds like your EJB
is
compiled with an option that turned off the replica aware stubs.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you shouldbe!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Ricardo De la Rosa" <[email protected]> wrote in message
news:[email protected]...
Hi,
I have a problem.
When the WebLogic server starts, it cannot deploy an EJB applicationbecause a
JDNI name is already in use.
What can I do to unregister this name ?
If it is possible a better description is step by step.
The WebLogic server, when starts, prints the next lines:
<18/01/2002 12:35:24 PM GMT-06:00> <Error> <J2EE> <Error deployingEJB
Component
: sui_ejb
weblogic.ejb20.EJBDeploymentException: Error deploying stateless
EJB;
nested exc
eption is:
javax.naming.NameAlreadyBoundException: Can't rebind anythingbut
a repl
ica-aware stub to a name that is currently bound to a replica-awarestub;
remain
ing name ''
javax.naming.NameAlreadyBoundException: Can't rebind anything but
a
replica-awar
e stub to a name that is currently bound to a replica-aware stub;remaining name
<<no stack trace available>>
>
<18/01/2002 12:35:24 PM GMT-06:00> <Error> <J2EE> <Error deployingapplication
s
ui_ejb: Could not deploy: 'sui_ejb.jar': JNDI name in use
>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer> <WebLogicServer
st
arted>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer>
<ListenThread
liste
ning on port 7001, ip address 157.253.174.63>
<18/01/2002 12:35:26 PM GMT-06:00> <Notice> <WebLogicServer><SSLListenThread
li
stening on port 7002, ip address 157.253.174.63>
In advance, thanks for your help.
- Ricardo De la Rosa (Colombia)

Error from ejbc: The JNDI name of bean

hi~
i have a problem .
to deploy , i did test bean like this..
java -classpath %CLASSPATH% -Dweblogic.home=%WL_HOME% weblogic.ejbc -compiler javac
old.jar new.jar
ERROR: Error from ejbc: The JNDI name of bean c was not set
ERROR: ejbc found errors
thank..^^
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN'
'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>c</ejb-name>
<home>c1.cHome</home>
<remote>c1.c</remote>
<ejb-class>c1.cEJB</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>c</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

What's your weblogic-ejb-jar.xml file?
"oh ki sung" <[email protected]> wrote in message
news:3cc8499a$[email protected]..
>
hi~
i have a problem .
to deploy , i did test bean like this..
java -classpath %CLASSPATH% -Dweblogic.home=%WL_HOME%weblogic.ejbc -compiler javac
old.jar new.jar
ERROR: Error from ejbc: The JNDI name of bean c was not set
ERROR: ejbc found errors
thank..^^
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD EnterpriseJavaBeans 1.1//EN'
'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>c</ejb-name>
<home>c1.cHome</home>
<remote>c1.c</remote>
<ejb-class>c1.cEJB</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>c</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

EJB Refs ( coded name and JNDI name )

Hi
I am just starting to develop EJBs . I can't get to work the EJB refs as expected . In a session bean I have a lookup for an Entity bean . Both beans are in separate JAR files , but in the same ear .
The lookup from session bean to entity bean only works when
the coded name in EJB ref is defined exactly the same as JNDI name for enity bean , also the name in lookup method must be the same in session bean .
To my surprise , the JNDI name for the target EJB , defined in EJB ref for session bean , does not mater at all . Even if I change it to a non existant name , the bean lookup works .
Theoritacally I understand that EJB ref is there to provide a mapping between the name of bean mentioned in code to the actual JNDI name of another bean , at the time of deployment .
The above is happening in J2EE 1.4 envoirment .
Please let me know , what am I doing here that is wrong .
( All examples and tutorials , usually give coded name same as JNDI name ) .
Thanks
Tarun

Hi Tarun,
The ejb-ref-name lives in a different namespace than the global JNDI names. Any names of ejb-refs, ejb-local-refs, resource-refs, etc. are scoped within a particular component's private namespace. All environment references are accessed via the java:comp/env namespace at runtime. So, if your ejb-ref-name(a.k.a "coded name") is ejb/foo in the deployment descriptor, you would access it from the code as follows :
initialContext.lookup("java:comp/env/ejb/foo");
This way, neither the standard deployment descriptor nor the code has any dependency on the global JNDI name. That's a good thing since the decision about which target EJB should be linked to is often not made until deployment time rather than development time. Furthermore, it means if you want to change the linking you can always do it without recompiling your code.
As for the global JNDI names, the first thing to note is that they are completely vendor-specific. That's why they don't appear in the standard deployment descriptor. In the J2EE SDK, each EJB that exposes a Remote view is assigned a global JNDI name in sun-ejb-jar.xml. This JNDI name is assigned from the global namespace of the application server. There's nothing stopping it from also being "ejb/foo", but it refers to a different thing than the "ejb/foo" above.
Now we have an ejb-ref called ejb/foo and an ejb whose JNDI name is ejb/foo, but we haven't linked the two. When it comes to linking, you have two choices:
1. If the target ejb is in the same .ear as the client component, you can use the ejb-link mechanism. This allows you to specify the target ejb by referring to its ejb-name. Since ejb-name is only guaranteed to be unique within an ejb-jar, the syntax allows for you to give the uri of the containing ejb-jar, followed by #, followed by ejb-name.
2. Alternatively, you can specify the global JNDI name of the target ejb using sun-ejb-jar.xml Note that this will work whether the target ejb is in the same .ear or not. However, it's the only option if the target ejb is in a different .ear. In this case, you would create an ejb-ref entry for the client component within the sun-ejb-jar.xml. e.g. :
<ejb>
<ejb-name>MyClientBean</ejb-name>
<ejb-ref>
<ejb-ref-name>ejb/foo</ejb-ref-name>
<jndi-name>ejb/foo</jndi-name>
</ejb-ref>
</ejb>
Again, it's just a coincidence that both names happen to be ejb/foo. They refer to different things.
When you do a global lookup from your code, initialContext.lookup('ejb/foo"), it will work in some environments because you're simply bypassing the level of indirection provided by your component environment and going straight to the global namespace. This is non-portable and not a good idea, since you've now tightly coupled the name of the target ejb to your client component. That means if it changes you need to recompile your code. Hope this helps.
--ken

Accessing Distributed destination JNDI Names Web

I am using WebLogic Full Client with Weblogic 10.3. I would like to obtain the JNDI names of the physical members of a Distributed Destination. Weblogic Documentation recommends doing:
"you must look up the JNDI name or the member name using the weblogic.jms.extensions.JMSModuleHelper class uddMakeName and uddMemberJNDIName APIs"
http://download.oracle.com/docs/cd/E11035_01/wls100/jms/dds.html#wp1314556
When I attempt to do the same using the Weblogic full client, I get a class not found exception where a QueueBean class is not found.
Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/j2ee/descriptor/wl/QueueBean
at com.overstock.jms.weblogic.ConfigurationMBeanHelper.main(ConfigurationMBeanHelper.java:150)
Caused by: java.lang.ClassNotFoundException: weblogic.j2ee.descriptor.wl.QueueBean
What is the best way to obtain JNDI names of distributed destinations when using Weblogic Full Client? Any code snippets would be valuable.
Thanks.

I think there are a variety of ways to crack this nut. Here are a couple of ideas:
One option would be to write a server side proxy that the client can invoke. For example, a simple EJB (stateless session bean). Another option would be write client-side JMX calls that query either the runtime mbeans or config mbeans to get a list of JMS servers and/or UDD members.
All of these options may require that the domain's administrative server be up and running (not sure). The runtime mbean options would only yield active members.
Tom

JNDI name in J2EE

Similar Messages

Maybe you are looking for