• 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

Same Entity Bean Different DB Tables

 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello there,
I hope someone can help me.
Currently I am writing approx. 100 entity beans for an application which I am involved in creating. They are container managed, and I will be deploying in weblogic 8.1
25 of the tables in the database are archive tables, where no additional information about the entities are stored, it is just to keep old data.
So basically, when it comes to the time where I create these <i><b>archive</b></i> entity beans, they will be exactly the same as the <i><b>non-archive</b></i> entity beans (apart from the deployment descriptor). Is it possible for me to re-use the non-archive entity beans and just write deployment descriptors for the archive ones? Or do I really have to write the EntityBean, LocalHome and Local interface all over again for the archive ones?
I appreciate any help offered,
Thank -you
Gillian Daniel
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic