cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Haul <h...@dvs1.informatik.tu-darmstadt.de>
Subject Re: _esql_connection.connection should be public
Date Mon, 12 May 2003 12:55:19 GMT
On 12.May.2003 -- 02:32 PM, Enke, Michael wrote:
> Torsten Curdt wrote:
> > 
> > > IMHO a new esql tag would be the best.
> > > If we make it outside esql we have to care about all imports and try/catch
> > > and what else is realted to java.sql.* in the xsp. This is not necessary when
> > > we make it with esql.
> > > If we create a new tag for returning the connection, I propose also to create
a tag
> > > for returning a ResultSet and ResultSetMetaData.
> > > Than we have more freedom in manipulating/assigning all kind of DB related
data.
> > 
> > not sure if ResultSet and ResultSetMetaData is really necessary but...
> > care enough for a patch? ;-)
> 
> for variable asignment like:
> 
> double d[] = new doubel[<esql:get-column-count/>];
> for(int i=0;i<d.length;i++) d[i] = _esql_query.getResultSet().getDouble(i+1);
> 
> I can not say: d[i] = <esql:get-double><xsp:attribute name="column"><xsp:expr>i</xsp:expr></xsp:attribute></esql:get-double>
> 
> Or can I?

Yes, you can:

  d[i] = <esql:get-double><esql:column><xsp:expr>i</xsp:expr></esql:column></esql:get-double>

BTW xsp:attribute adds an attribute to the output stream while you
want to add an attribute to a logicsheet tag. Most - but not all -
follow the pattern <prefix:param name="foo">value</prefix:param>
Note that the logicsheet in question - and the tag in particular -
needs to support dynamic values. Unfortunately, only an inspection of
the xsl reveals what is supported and what isn't.

	Chris.
-- 
C h r i s t i a n       H a u l
haul@informatik.tu-darmstadt.de
    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08

Mime
View raw message