If there is a Tag to deal with ResultSets, and you
don't need to post process the data at all, you can
use it in a jsp without needing to write any Java on
the page.  It just becomes a DTO, that the controller
hands to the view.  Right?

Now, if you only need a subset, and you are passing it
over a network to the presentation tier, then you
might want an adapter or wrapper type class to trim
down the pay load.  But, then you could just trim the
sql appropriately, too.

I'm sure there are other issues, and the whole concept
can be made more complicated.  There may be security
issues, like your front end team can't have access to
a ResultSet, esp a 2.0 JDBC one.  

Best practice in my experience would be use the RS,
and refactor if you need to.  But, you should not
import java.sql in your jsps.  So, use a wrapper if
you can't find an introspecting tag, or another trick.

- gene






--  From Marc --
Hello,

I would like to know what is for you the best practice
to present to a user the result of a db query (a
ResultSet variable)?

If, you can take some example of your suggestion, it
will help me to understand...

thank you in advance

regards
Marc

__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to