Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Same Entity Bean Different DB Tables

 
Gillian Daniel
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • 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
 
Nathaniel Stoddard
Ranch Hand
Posts: 1258
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think I understand what you're asking, but maybe not. You have some database, with tables in it that you want entity beans and Websphere to ignore, right?
In that case, yes. You can write your deployment descriptors just the normal way, making sure that Websphere doesn't create or destroy the database tables. And it should completely ignore the others. Did that answer what you were asking?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic