This week's book giveaway is in the Cloud/Virtualization forum.
We're giving away four copies of Building Blockchain Apps and have Michael Yuan on-line!
See this thread for details.
Win a copy of Building Blockchain Apps this week in the Cloud/Virtualization forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Liutauras Vilda
  • Knute Snortum
  • Bear Bibeault
Sheriffs:
  • Devaka Cooray
  • Jeanne Boyarsky
  • Junilu Lacar
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
  • salvin francis
Bartenders:
  • Tim Holloway
  • Piet Souris
  • Frits Walraven

JNDI name in admin console not filled in spite of the definition in ibm-web-bnd.xmi

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello everybody,

I have try to deploy a ejb client in websphere by using the file "ibm-web-bnd.xmi" like following:

<?xml version="1.0" encoding="UTF-8"?>
<webappbnd:WebAppBinding xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:common="common.xmi" xmlns:webappbnd="webappbnd.xmi" xmi:id="WebAppBinding_1140436044709" virtualHostName="default_host">
<webapp href="WEB-INF/web.xml#WebApp_3140436044663"/>

<ejbRefBindings xmi:id="EjbRefBinding_1259750908284" jndiName="my/jndiA">
<bindingEjbRef xmi:type="common:EJBLocalRef" href="WEB-INF/web.xml#EJBLocalRef_1"/>
</ejbRefBindings>

<ejbRefBindings xmi:id="EjbRefBinding_1259750939719" jndiName="my/jndiB">
<bindingEjbRef xmi:type="common:EJBLocalRef" href="WEB-INF/web.xml#EJBLocalRef_2"/>
</ejbRefBindings>

</webappbnd:WebAppBinding>


---------------------

The problem is why I can not see the specified JNDI in the admin console at the the step "EJB references to Beans".

The filed "JNDI name" is empty!

Can anyone give me an idea, perhaps I have missed to fill the JNDI name in some other files.
By the way, the EJBs are already defined in "ibm-ejb-jar-bnd.xmi" with the same JNDI name.

Thanks in advance.

Jennifer
 
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Have you manually edited ibm-web-bnd.xmi? If so, the references don't seem to be very tolerent of such changes.
 
Jennifer Best
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for your reply.

Sure I have edited the file ibm-web-bnd.xmi manuelly. Is it not allowed?

 
Guy Leeds
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Just based on my own experience and supported by WebSphere Application Server 5.1 Info Center:

You can edit a deployment descriptor file manually. However, it is preferable to edit a deployment descriptor using an Assembly Toolkit deployment descriptor editor to ensure that the deployment descriptor has valid properties and that its references contain appropriate values.

 
He does not suffer fools gladly. But this tiny ad does:
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!