• Post Reply Bookmark Topic Watch Topic
  • New Topic

EJBs for Data Warehouse  RSS feed

Ben Bailey
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I wanted to kick around some ideas regarding using EJBs to access a Data Warehouse.
Some constraints:
C1. In this particular case, the data will be read-only, and won't be updated during normal business hours, when all transactions will occur.
C2. The database drivers are somewhat defective, so that no CMP can be utilized; all queries must be hand coded.
What are your thoughts on the following:
T1. Since the data is Read-Only, most, if not all, EJBs will be stateless Session Beans.
T2. Session Beans will return data objects (Details Pattern) to requesters.
T3. In a very few instances, there are a few tables that have very very limited number of rows. Rather then make repeated SQL calls against the database during the course of the day, use Entity Beans for each row instance, because these are a)sharable, and b)are unique by key, and c)remain in the EJB Container for the next user. These would also return data objects.
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!