JNDI names in the deploytool

Every time I add my ejb .jar file to my application, the deploytool forgets the JNDI names for my beans. I have to enter them all again every time, and this is annoying!
Using deploytool GUI:
select treenode: Files -> Applications -> myapp -> myEJB
on the right panel, select 'JNDI Names' tab
All names are empty after I add my .jar to the application again (because I added a new bean and want to get the new sun-j2ee-ri.xml).
Do I add something into the ejb-jar.xml file?
Any ideas?
Thanks, Gretel

Frank is correct. When I make a change that requires changes in the deployment descriptor ejb-jar.xml file, I have to remove and readd my .jar file to the application and use the GUI deploytool so that I can then get a newly generated sun-j2ee-ri.xml file for my application that I use when deploying via the command line.
Please, doesn't anyone out there know the solution?
Thanks, Gretel

Similar Messages

No JNDI Names Tab in deployTool

I followed the J2EE tutorial to run ConverterApp example, but couldn't find the
JNDI Names tab when trying to specifying JNDI names. I am using J2sdkee1.4 on win 2k. Anyone knows what's wrong with this? Thanks

Hi Poeple!
PROBLEM IS DIFFERENT************
People just for your knowledge this is what Sun's people have about it -
According to them its not a bug - As Per JSR88, JNDI names are now part of the deployment settings customizers.
But how to set it now is the question!!!
Foll is from Sun on this Bug - read it up to last
Bug Id 4782648
Votes 0
Synopsis REGRESSION: JNDI Names tab in deploytool is missing
Category j2ee:deploytool
Reported Against 1.4beta
Release Fixed
State Closed, not a bug
Related Bugs
Submit Date Nov 21, 2002
Description
FULL PRODUCT VERSION :
FOR J2SE, ver 1.4.1
FOR J2EE, ver 1.4 Beta
FULL OPERATING SYSTEM VERSION :
Windows XP
A DESCRIPTION OF THE PROBLEM :
JNDI Names tab in deploytool is missing.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1.Run deploytool
2.Create New Application EAR
3.Click at the icon for application ear on the left tree
4.On the right panel, you will only see General, Roles and
Web Context tab
REPRODUCIBILITY :
This bug can be reproduced always.
Release Regression From : 1.3.1
The above release value was the last known release where this
bug was known to work. Since then there has been a regression.
(Review ID: 167238)
The JNDI Tab/Pane does not appear for the app or for subsequently added
components (EJB, Web, or app).
(Review ID: 167171)
webbug ytooi4 adrian_popescu
Workaround None.
Evaluation Not a bug.
Per JSR88, JNDI names are now part of the deployment settings customizers.
xxxxx@xxxxx 2002-11-21

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 names tab missing on deploytool

Hi folks,
Sorry I'm a bit of a newbie and have been trying out the J2EE tutorial
All was going well, until I had to specify the JNDI names - and the tab
isn't there!
All i have is general - roles - web context. I also get an error
(Cannot obtain list of methods) when I access the secuirty tab of the bean....
Any ideas.
Garry

Bug Id 4782648
Votes 0
Synopsis REGRESSION: JNDI Names tab in deploytool is missing
Category j2ee:deploytool
Reported Against 1.4beta
Release Fixed
State Closed, not a bug
Related Bugs
Submit Date Nov 21, 2002
Description
FULL PRODUCT VERSION :
FOR J2SE, ver 1.4.1
FOR J2EE, ver 1.4 Beta
FULL OPERATING SYSTEM VERSION :
Windows XP
A DESCRIPTION OF THE PROBLEM :
JNDI Names tab in deploytool is missing.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1.Run deploytool
2.Create New Application EAR
3.Click at the icon for application ear on the left tree
4.On the right panel, you will only see General, Roles and
Web Context tab
REPRODUCIBILITY :
This bug can be reproduced always.
Release Regression From : 1.3.1
The above release value was the last known release where this
bug was known to work. Since then there has been a regression.
(Review ID: 167238)
The JNDI Tab/Pane does not appear for the app or for subsequently added
components (EJB, Web, or app).
(Review ID: 167171)
webbug ytooi4 adrian_popescu
Workaround None.
Evaluation Not a bug.
Per JSR88, JNDI names are now part of the deployment settings customizers.
xxxxx@xxxxx 2002-11-21

Deploytool: Missing JNDI Names tab

I'm attempting the ConverterApp example in the J2EE 1.3 tutorial. In the section titled 'Specifying the JNDI Names' are the following instructions;
To map the enterprise bean references in the clients to the JNDI name of the bean, follow these steps.
1. In the tree, select ConverterApp.
2. Select the JNDI Names tab.
3. To specify a JNDI name for the bean, in the Application table locate the ConverterEJB component and enter MyConverter in the JNDI Name column.
4. To map the references, in the References table enter MyConverter in the JNDI Name for each row.
My problem is that deploytool doesn't display a tab labeled 'JNDI Names'. I see only tabs labeled 'General', 'Roles', and 'Web Context', whereas figure 2-1 in the example shows a deploytool screen that displays tabs labeled 'General', 'JNDI Names', 'Web Context', and 'Security'.
I've tried the deployment steps twice, so I don't think I've missed a step. What can be wrong? I,m running Application Development Tool Version 1.4. Is this the wrong version for this tutorial?

Are you sure that you have selected the application and not he jar from the tree. I'm not sure which one it is, but you should play with that, the gui is a little tricky and depending on whether you have selected the jar or the ejb itself, different menu options will be available.
Sorry I couldn't be more help, but that gui has given me grief in the past so I thought I'd throw it out there.
tj...

A problem determining the JNDI Name of a local EJB with WL 8.1

Hi,
I created a very simple local EJB and deployed it with Weblogic8.1. When I test
it in the Weblogic server admin page, I got the following message:
"The EJB MyLocal has not been tested successfully. There was a problem determining
the JNDI Name of the given bean."
Can anyone help figure out the problem?
Thanks
Henry

Does the ejb have a target server specified?
Does the Ejb have a Jndi binding as specified in the <local-jndi-name></local-jndi-name>
element of weblogic-ejb-jar.xml?
thanks,
Deepak
"Henry" <[email protected]> wrote:
>
>
Hi,
I created a very simple local EJB and deployed it with Weblogic8.1. When
I test
it in the Weblogic server admin page, I got the following message:
"The EJB MyLocal has not been tested successfully. There was a problem
determining
the JNDI Name of the given bean."
Can anyone help figure out the problem?
Thanks
Henry

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>

How to get the JNDI name of an EJB from within itself

Hello,
I'm trying to find a way to get the JNDI name of a session bean from
within itself.
In the application I'm working on we need to support multiple
customers. In order to do that, each EJB has a normal home and remote
interface, a base class bean implementation and different children
bean implemetations for each customer (when the logic for the
customers is different). JNDI is used to get the proper implementation
based on the customer.
I've got an EJB that provides some services that are the same for all
customers, except for the fact that it contains one variable that
should have a different value depending on the customer. I don't want
to creat subclasses just for that. What I want is to be able to get
the JNDI name and set the variable based on the it.
Is there a way to get the JNDI name for the EJB from within itself?
TIA
MJ

Hi Pradeep,
Please try referring to this post which is discussed earliar and seems its also answered.
http://forums.adobe.com/thread/504861
Thanks,
Bhasker Chari

JNDI name for a JMB is not replicatet to other servers in the cluster

Hi,
          wl6.1sp7, two server cluster
          When I look at the JNDI Tree for a server I can't find JNDI names of JMB's from the other server in the cluster.
          I get an exception when trying to send to a destinaton on the other server. (Unable to resolve 'xlink.jms.service.report.biztalk-lab.Report' Resolved: 'xlink.jms.service.report' Unresolved:'biztalk-lab')
          Setting are same as explained in this thread...
          http://forums.bea.com/bea/thread.jspa?threadID=600003492&tstart=0
          And JNDINameReplicated is set to true....
          Why is the JNDI names not replicated?
          <JMSQueue JNDIName="xlink.jms.service.report.biztalk-lab.Report"
          JNDINameReplicated="true" Name="Report" StoreEnabled="default"/>
          This is the DD of a JMB:
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>xlink.jms.service.report.biztalk-lab.Report</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>3</max-beans-in-free-pool>
          <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
          </pool>
          <destination-jndi-name>xlink.jms.service.report.biztalk-lab.Report</destination-jndi-name>
          <connection-factory-jndi-name>xlink.jms.factory.commerceFactory</connection-factory-jndi-name>
          </message-driven-descriptor>
          <jndi-name>xlink.jms.service.report.biztalk-lab.Report</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          ~b

1. yes
          <JMSConnectionFactory AllowCloseInOnMessage="false"
          DefaultDeliveryMode="Persistent" DefaultPriority="4"
          DefaultTimeToLive="0"
          JNDIName="xlink.jms.factory.commerceFactory"
          MessagesMaximum="10" Name="xlink.jms.factory.commerceFactory"
          OverrunPolicy="KeepOld" Targets="bluej,biztalk-lab,devtestCluster"/>
          2. No I am just using the jndi name of the queue.
          This is an example of how I send a message:
               Context ctx = new InitialContext();
          QueueConnectionFactory qconFactory;
          QueueConnection qcon;
          QueueSession qsession;
          QueueSender qsender;
          Queue queue;
          ObjectMessage msg;
          qconFactory = (QueueConnectionFactory) ctx.lookup("xlink.jms.factory.commerceFactory");
          qcon = qconFactory.createQueueConnection();
          qsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
          queue = (Queue) ctx.lookup("xlink.jms.queue.biztalk-lab.OrdrspImport");
          qsender = qsession.createSender(queue);
          msg = qsession.createObjectMessage(reportExecutorContainer);
          qcon.start();
          qsender.send(msg);
          qsender.close();
          qsession.close();
          qcon.close();
          3. I don't know those setting (wl 6.1sp7)

[EJB:011055]Error deploying the EJB with error that JNDI name already inuse

Hi,
I have written a trivial application consisting of 4 stateless beans and 1 MDB. The ear is developed from some code generator tool and works fine if I directly deploy on weblogic server 812.
But in order to learn Weblogic Workshop I created new Application and EJB project. Then I imported the EJB jar and provided other source files.
From Weblogic Workshop I could generate the ear successfully. But while trying to deploy the ear I get the following exception :
<16/03/2005 10:02:38 PM GMT+05:30> <Error> <Deployer> <BEA-149201> <Failed to complete the deployment task with ID 1 for the application hsbc.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for MCAppBEAN.jar
Module: MCAppBEAN.jar Error: Exception preparing module: EJBModule(MCAppBEAN.jar,status=NEW)
Unable to deploy EJB: StatelessBean from MCAppBEAN.jar:
<b>[EJB:011055]Error deploying the EJB 'StatelessBean(Application: hsbc, EJBComponent: MCAppBEAN.jar)', the JNDI name 'StatelessBeanHSBC' is already in use. You mu
st set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor for this EJB before it can be deployed.</b> at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2556)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
--------------- nested within: ------------------
<b>Can someone tell where have I made the mistake?</b>
thanks in advance.

Try to undeploy and un target the applcation via WLS console and they try to deploy it again. Or just try to redeploy it.

Override JNDI names in persistence.xml and @resource annotation

I have a Java EE 7 application that I am developing for use with both GlassFish and WildFly, but I have discovered that both application servers use a slightly different format for specifying JNDI names.
In GlassFish the persistence.xml file references the data source jdbc/myDataSouce, but in WildFly the data source needs to be java:/jdbc/myDataSource.The same is also true for classes that are annotated with @Resource. In GlassFish the annotation for a class using JavaMail would be @Resource(name = "mail/myMailSession"), but to deploy onto WildFly this would need to be @Resource(name = "java:mail/myMailSession").
The only solution I've got at present is using Maven to create two different releases of the EAR file, with one EAR file containing a persistence.xml file with the data source jdbc/myDataSouce for use with GlassFish, and the second EAR file containing a persistence.xml file with the data source java:/jdbc/myDataSource for use with WildFly. Unfortunately, I haven't found a solution for the @Resource annotation.
I've taken a look at the documentation for glassfish-application.xml and glassfish-ejb-jar.xml and have tried using resource-ref to override the JNDI names but the application fails to deploy due to an error in the name.
My question is does GlassFish provide any capability to override the JNDI names specified in the persistence.xml file and classes with the @resource annotation?
Many Thanks
Paul

Have you been able to solve this? I'm attempting to understand what Web Server 7 can do with regard to Java Persistence and what elements of it require Glassfish.
I've also spent great amounts of time in WS6.1 trying to figure out why a JNDI resource couldn't be found. The rules of thumb I've learned are:
- Try dropping the *'java:/comp/env/* prefix; just use jdbc/pact part
- Make sure all referrences (in web.xml and sun-web.xml) are identical with regard to that name.
I'm hoping you're not still dealing with this (it's been two months!) but if anybody else stumbles on this, maybe it'll help them.
Dave

Jndi-name in Message Driven Bean

Hi
I have successfully created the ejb jar file for deployment using sun one studio . I created the message driven bean and I right clicked on the ejb and used the customize option to set the bean properties . But my problem is that the jndi-name in the <ejb> tags takes the value jms/(ejbname) instead of jms/(queuename) . I am attaching the xml file with this . Can any one tell how to set the jndi-name to queue value using studio
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Sun ONE Application Server 7.0 EJB 2.0//EN" "http://www.sun.com/software/sunone/appserver/dtds/sun-ejb-jar_2_0-0.dtd">
<sun-ejb-jar>
<enterprise-beans>
<name>ejb</name>
<ejb>
<ejb-name>Suneesh</ejb-name>
<jndi-name>jms/Suneesh</jndi-name> <resource-ref>
<res-ref-name>QueueConnectionFactory</res-ref-name>
<jndi-name>jms/QueueConnectionFactory</jndi-name>
</resource-ref>
<resource-env-ref>
<resource-env-ref-name>TestQueue</resource-env-ref-name>
<jndi-name>jms/TestQueue</jndi-name>
</resource-env-ref>
<pass-by-reference>false</pass-by-reference>
</ejb>
<ejb>
<ejb-name>Suneesh1</ejb-name>
<jndi-name>jms/Suneesh1</jndi-name>
<resource-ref>
<res-ref-name>QueueConnectionFactory</res-ref-name>
<jndi-name>jms/QueueConnectionFactory</jndi-name>
</resource-ref>
<resource-env-ref>
<resource-env-ref-name>TestQueue1</resource-env-ref-name>
<jndi-name>jms/TestQueue1</jndi-name>
</resource-env-ref>
<pass-by-reference>false</pass-by-reference>
</ejb>
</enterprise-beans>
</sun-ejb-jar>

Hi Bhagya,
Thanks for your response. I think from EJB container we can call Local EJBs with the full JNDI name. The session facade bean which is being called is a remote bean. From the session facade bean I am calling a local stateless session bean for database access. I am getting the reference of the local EJB from my session facade bean with full JNDI name "java:comp/env/ejb/EJBJNDIName". It is working fine with out any problem. My servicelocator is able to provide me the reference of the local EJB from the session facade remote bean with Full JNDI name. I am only having this problem calling from the MDB. I am really not sure whether what is causing it?
Thanks
Amit

Weblogic 10.3 - changing jndi-name with deployment plan fails

I was trying to alter the global jndi name of a stateless ejb by using a deployment plan, but can't get it to work.
- to be able to replace it later on with a deployment plan, I specify a jndi-name in weblogic-ejb-jar.xml (so I do not use the @mappedName)
e.g.
<?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>ExampleService</ejb-name>
          <enable-call-by-reference>true</enable-call-by-reference>
          <stateless-session-descriptor>
               <business-interface-jndi-name-map>
                    <business-remote>com.example.ExampleServiceRemote</business-remote>
                    <jndi-name>com.example.ExampleService#com.example.ExampleServiceRemote</jndi-name>
               </business-interface-jndi-name-map>
          </stateless-session-descriptor>
     </weblogic-enterprise-bean>
</weblogic-ejb-jar>
- during deployment I specify a deploymentPlan with following content:
<variable-definition>
<variable>
<name>ejb_jndiname_ExampleService</name>
<value>ExampleService</value>
</variable>
</variable-definition>
<module-override>
<module-name>ExampleService.jar</module-name>
<module-type>ejb</module-type>
<module-descriptor external="true">
<root-element>weblogic-ejb-jar</root-element>
<uri>meta-inf/weblogic-ejb-jar.xml</uri>
<variable-assignment>
<name>ejb_jndiname_ExampleService</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/\[ejb-name="ExampleService"\]/stateless-session-descriptor/business-interface-jndi-name-map/\[business-remote="com.example.ExampleServiceRemote"\]/jndi-name</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
</module-override>
- after deployment, the original jndi-name ("com.example.ExampleService#com.example.ExampleServiceRemote") is active in the jndi tree instead of "ExampleService"
p.s. When I specified the jndi-name in weblogic-ejb.jar.xml as
     <weblogic-enterprise-bean>
          <ejb-name>ExampleService</ejb-name>
          <enable-call-by-reference>true</enable-call-by-reference>
          <jndi-name>com.example.ExampleService#com.example.ExampleServiceRemote</jndi-name>
     </weblogic-enterprise-bean>
and the replace in the deployment plan as
<variable-assignment>
<name>ejb_jndiname_SecurityService</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/\[ejb-name="ExampleService"\]/jndi-name</xpath>
<operation>replace</operation>
</variable-assignment>
the replacement does work (checked by verifying the jndi-name within the deployed ear using the console), but the problem then is that the jndi-name does not appear in the jndi tree (that's why I tried the <business-interface-jndi-name-map>)
Any ideas?
Kind regards,
Ben
Edited by: user11230128 on 4-jun-2009 7:42

After a Service Request and some trial and error, I got it to work after adding the following part in each 'jar module override' section of the deployment plan:
<module-descriptor external="false">
<root-element>ejb-jar</root-element>
<uri>META-INF/ejb-jar.xml</uri>
</module-descriptor>
Apparantly this is needed even though there is no ejb-jar.xml in the jar.
So the deployment plan has to be something like:
<variable-definition>
<variable>
<name>ejb_jndiname_ExampleService</name>
<value>ExampleService</value>
</variable>
</variable-definition>
<module-override>
<module-name>ExampleService.jar</module-name>
<module-type>ejb</module-type>
<module-descriptor external="false">
<root-element>weblogic-ejb-jar</root-element>
<uri>meta-inf/weblogic-ejb-jar.xml</uri>
<variable-assignment>
<name>ejb_jndiname_ExampleService</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/[ejb-name="ExampleService"]/stateless-session-descriptor/business-interface-jndi-name-map/[business-remote="com.example.ExampleServiceRemote"]/jndi-name</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
<module-descriptor external="false">
<root-element>ejb-jar</root-element>
<uri>META-INF/ejb-jar.xml</uri>
</module-descriptor>
</module-override>
...

Specify JNDI Name For EJB Module

Hi folks, please I need to know how I can specify the Jndi name for an ejb module I am creating in netbeans 5.0, to be accessed by a web application.
If this can be done using the sun java system application server 9 admin consle (just as for JDBC Resources), i'll also like to know how.
Thanks.

Thanks Jay. I went through the links, it seems that if you have the JNDI name set in the weblogic-ejb-jar.xml, there is no need to set the same in the weblogic admin console. I am using ejb 2.x version. Particularly if you get the WLInitialContextFactory in your code , then there is no need to set the JNDI name in the JNDI tree in weblogic admin console.
Like:-
Context ctx = null;
java.sql.Connection conn = null;
Hashtable<String,String> ht = new Hashtable<String,String>();
ht.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL,"t3://localhost:7001");
This will take care of JNDI tree, hence there is no need to set the JNDI name explictly in the weblogic admin console.
Please correct me if i am wrong. Whether for datasource also whether we can do the same, by setting the resource-ref with datasource in the ejb-jar.xml and not set anything in weblogic admin console? Thanks.

Deployment of two SDOs -- jndi name is already in use

(this was accidentally posted earlier -- I deleted that post and created this one)
Hello,
I am on jdev 11.1.1.17 and am working with the Oracle SOA Suite. I have an application and have 3 projects each with an ADFBC module and Application module Service Interface (for the SDO). I have one project that I imported from the Oracle Uni Soa Class files, and I created two projects on my own, both "pointing" to different oracle tables. I am able to deploy all separately -- but of the two that I created on my own, if one is already deployed, I cannot deploy it -- get the error below, however here is the pertinant part;
[EJB:011055]Error deploying the EJB 'model.common.AppModuleServiceBean(Application: FlashADFBCService, EJBComponent: FlashADFBC_MiddleTier.jar)', the JNDI name 'AppModuleServiceBean#model.common.serviceinterface.AppModuleService' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
What I tried:
1. I deleted out the cache and tmp directories as suggested here: https://forums.oracle.com/message/11024693#11024693
2. When I created the application modules, I originally used the default settings, but when I encountered the error, I recreated everything I could think of with unique names -- the app module, the service interface and target namespace.
3. I checked the weblogic-ejb-jar.xml , the ejb-jar.xml and the AppModuleSoaADFBCServiceImpl class annotations:
### AppModuleSoaADFBCServiceImpl #######################################
@Stateless(name="orderssdo.common.OrdersAppModuleServiceBean", mappedName="OrdersAppModuleServiceBean")
@Remote(OrdersAppModuleService.class)
@PortableWebService(targetNamespace="/orderssdo/com/", serviceName="OrdersAppModuleService",
    portName="OrdersAppModuleServiceSoapHttpPort", endpointInterface="orderssdo.common.serviceinterface.OrdersAppModuleService")
@Interceptors( { ServiceContextInterceptor.class })
### weblogic-ejb-jar.xml #######################################
<?xml version = '1.0' encoding = 'UTF-8'?>
<weblogic-ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-ejb-jar http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd" xmlns="http://www.bea.com/ns/weblogic/weblogic-ejb-jar">
<weblogic-enterprise-bean>
    <ejb-name>orderssdo.common.OrdersAppModuleServiceBean</ejb-name>
    <stateless-session-descriptor>
      <pool>
        <initial-beans-in-free-pool>2</initial-beans-in-free-pool>
      </pool>
    </stateless-session-descriptor>
    <enable-call-by-reference>true</enable-call-by-reference>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
### ejb-jar.xml #######################################
<?xml version = '1.0' encoding = 'windows-1252'?>
<ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
         version="3.0" xmlns="http://java.sun.com/xml/ns/javaee">
<enterprise-beans>
    <session>
      <ejb-name>orderssdo.common.OrdersAppModuleServiceBean</ejb-name>
      <resource-ref>
        <res-ref-name>jdbc/soademoDS</res-ref-name>
        <res-type>javax.sql.DataSource</res-type>
        <res-auth>Container</res-auth>
      </resource-ref>
    </session>
</enterprise-beans>
</ejb-jar>
THE ERROR: (It repeats alot)
Unable to deploy EJB: model.common.AppModuleServiceBean from FlashADFBC_MiddleTier.jar:
[EJB:011055]Error deploying the EJB 'model.common.AppModuleServiceBean(Application: FlashADFBCService, EJBComponent: FlashADFBC_MiddleTier.jar)', the JNDI name 'AppModuleServiceBean#model.common.serviceinterface.AppModuleService' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
[10:59:26 AM] Weblogic Server Exception: weblogic.application.ModuleException: Exception preparing module: EJBModule(FlashADFBC_MiddleTier.jar)
Unable to deploy EJB: model.common.AppModuleServiceBean from FlashADFBC_MiddleTier.jar:
[EJB:011055]Error deploying the EJB 'model.common.AppModuleServiceBean(Application: FlashADFBCService, EJBComponent: FlashADFBC_MiddleTier.jar)', the JNDI name 'AppModuleServiceBean#model.common.serviceinterface.AppModuleService' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
[10:59:26 AM] Caused by: java.lang.Throwable: Substituted for missing class [EJB - 11055]Error deploying the EJB 'model.common.AppModuleServiceBean(Application: FlashADFBCService, EJBComponent: FlashADFBC_MiddleTier.jar)', the JNDI name 'AppModuleServiceBean#model.common.serviceinterface.AppModuleService' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
[10:59:26 AM]   See server logs or server console for more details.
[10:59:26 AM] Caused by: java.lang.Throwable: Substituted for missing class [EJB - 11055]Error deploying the EJB 'model.common.AppModuleServiceBean(Application: FlashADFBCService, EJBComponent: FlashADFBC_MiddleTier.jar)', the JNDI name 'AppModuleServiceBean#model.common.serviceinterface.AppModuleService' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
[10:59:26 AM]   See server logs or server console for more details.

Thank you for your answer. I haven't tested whether your answer works I am sure it does however, I just discovered a way to make it work also. I found some references to adding the jndi name in the weblogic-ejb-jar.xml and then referencing that in the ejb-jar.xml. The weblogic-ejb-jar.xml has a gui where you can add the jndi, but then I referenced it in the ejb-jar.xml as such.
see <mapped-name>soaDemoSSF</mapped-name>
<?xml version = '1.0' encoding = 'windows-1252'?>
<ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
         version="3.0" xmlns="http://java.sun.com/xml/ns/javaee">
<enterprise-beans>
    <session>
      <ejb-name>adfbcsoademo.common.SoaDemoAppModuleServiceBean</ejb-name>
      <mapped-name>soaDemoSSF</mapped-name>
      <resource-ref>
        <res-ref-name>jdbc/soademoDS</res-ref-name>
        <res-type>javax.sql.DataSource</res-type>
        <res-auth>Container</res-auth>
      </resource-ref>
    </session>
</enterprise-beans>
</ejb-jar>

JNDI names in the deploytool

Similar Messages

Maybe you are looking for