Win a copy of Clojure in Action this week in the Clojure forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Binding file ibm-ejb-jar-bnd.xmi

 
Rajesh So
Ranch Hand
Posts: 149
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I have to edit the binding files of pre-EJB 3.0 beans. In pre-historic times, the binding files were generated by a xdoclet or Websphere Application Developer or RAD. I am trying to merge to ejb-jar files. I am making a mess because I am doing it by hand. There are some references and naming convention that I cannot understand. I feel its best edited using the IBM tool. I have downloaded a Websphere plugin for the same. But I can't find it appear in the Eclipse.

Do you have any idea how to use the Websphere plug-in in Eclipse?

regards,
Raj
 
Claude Moore
Ranch Hand
Posts: 747
7
IBM DB2 Java Netbeans IDE
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Every time I had to manipulate xml files in WebSphere / RAD (deployment descriptors, ejb bindings and so on) I felt like I fell in the Hell.
I think that if you need to merge two EJB projects, the simplest and less error prone way is to replicate your ejbs in the destination project, copy and paste code from source project ejbs, and then
promote to remote /local interfaces your public methods, assigning transaction isolation levels, resources bindings and so on.
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 33694
316
Eclipse IDE Java VI Editor
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I agree with Claude. Even in IBM's own tooling, they have been making this task more difficult. RAD 6 had decent support. RAD 7.5 made it a painful task.

I thought the WebSphere plugin for Eclipse was to run or deploy. Not for editing files. Maybe I'm remembering wrong?
 
Steve Harney
Greenhorn
Posts: 19
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The documentation around the ibm-ejb-jar-bnd.xmi files is non existent. I have done a number of these by hand, or i should say by cut and paste. I would start with building the ear without the xmi files and deploy to a local WebSphere instance, using the detailed path to ensure that i was able to fill in all the bits required for the xmi file. Once the application was deployed i would extract the ejb-jar.xml and the xmi file from WebSphere and use those to update the ejb-jar.xml with the required id's and to build the new ibm-ejb-jar-bnd.xmi file. Depending on how anal retentive you are depends on how far you clean them up.. Once i had something i was happy with i would redeploy, again using the detailed path and confirm i didnt break anything.

Not a pretty process but given the tooling and lack of documentation it worked for me.

Steve.
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic