• 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

How to handle CMR entity beans?

 
Ranch Hand
Posts: 121
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm using CMR, and there are about 20 of them.
My entity beans are all related one way or other,
and they are packed in one jar file.
The deployment descriptors are becoming very large, and hard to maintain. Should I divide CMR entity beans into
small groups?
 
Ranch Hand
Posts: 2713
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Only Entity Beans that are packaged in the same ejb-jar can have CMR relationships with each other. Therefore if all of your Entities are truely related in some way then they must all reside in the same ejb-jar.
Typically it is easier to manage multiple ejbs in a single jar then it is to manage multiple ejb-jars. The other benefit is your ejbs will deploy faster in a single jar then in multiple jars (this is from my experiences with JBoss and WebLogic).
I suggest using a tool that helps you manage the descriptors like Xdoclet.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic