• 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
  • Tim Cooke
  • paul wheaton
  • Liutauras Vilda
  • Ron McLeod
Sheriffs:
  • Jeanne Boyarsky
  • Devaka Cooray
  • Paul Clapham
Saloon Keepers:
  • Scott Selikoff
  • Tim Holloway
  • Piet Souris
  • Mikalai Zaikin
  • Frits Walraven
Bartenders:
  • Stephan van Hulst
  • Carey Brown

Designing Reports

 
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Can i use CachedRowSet in transferring my data from EJB layer to Web Layer, how much it is going to impact on application performance level, or I have to use value objects. I am designing reports.


mohan
 
Ranch Hand
Posts: 1683
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
A CachedRowSet is usually serializable, so it can certainly be passed to a remote client. But bear in mind that it is a ResultSet object (disconnected of course), so do you want your client to know that it dealing with a relational DB? This is why the use of a transfer object (new term for value object) is often advocated. My own preference is to always shield the client from implementation details, so I would use a transfer object.

Don't worry too much about performance, it's rare to find transfer objects a problem.
reply
    Bookmark Topic Watch Topic
  • New Topic