• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

XDoclet problem

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am trying to add a new stateless session bean to an existing J2EE application. The build uses an ejbdoclet ant task to generate the deployment descriptor file ejb-jar.xml (as well as dataobject, utilobject, remoteinterface, homeinterface, localinterface, and localhomeinterface). All new files are generated consistently with the rest of the application except the entry in the deployment descriptor file. In the ejb-jar.xml, all of the other stateless session beans in the project have an <ejb-class> entry with a name of the form {0}Impl. However the <ejb-class> entry for the new bean has the form {0}CMP as if it were an entity bean. Obviously I am not an expert in XDoclet, but there is no merge directory as far as I can tell, and I can't figure out where the name pattern is coming from and why this single class is using the wrong pattern.
Any help would be appreciated.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic