Copying the properties into a list is better than all that reading a
result set into your view anyhow.
Sure allowing read access to a result set isn't the end of the world,
but copying it into a a list of beans would be my prefered way of
doing things even if the ResultSetModel were available.
If you like SQL in your view, then the JSTL sql tag lib is there at
your disposal. But personallty I dont like sql speak in my JSP in fact
seeing "row" mentioned in JSP (JSF or otherwise) gives me a nauseaous
sensation.
But if thats the way you like working, feed the result set to the jsp.
You could even to this in a backing bean for now and readdress later.
((HttpServletRequest)FacesContent.getCurrentInstance().getExternalContext().getRequest()).setAttribute("myresultset",rs);
Then use
<f:verbatim>
.. some sql tag filth here
</f:verbartim>
Its not perfect, but is adequate.
Mark
On Wed, 3 Nov 2004 09:46:46 +0100, Francesco Consumi
<[EMAIL PROTECTED]> wrote:
> Scrive Manfred Geiler <[EMAIL PROTECTED]>:
>
> > Hi Francesco, Hi all,
> > Yes, ResultSetDataModel is not yet implemented. It is not really
> > difficult to implement but my time is very limited at the moment. So, I
> > encourage you or any other interested developer to implement it. Could
> > be done in about 2-3 man hours, I think.
> > Francesco, thanks for your confidence and: you are just kidding about
> > the ASP.NET thing, arent' you ?! ;-)
> >
>
> Sure I do.. :-)
> I would provoke the java coder's susceptibility......
>
> I'll wait for the implementation of ResultDataSet. I apologize, but I'm
> not able
> to help you in that work, I'm not a so good java programmer......
>
> --
> Francesco Consumi
>
>
