cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enke, Michael" <michael.e...@wincor-nixdorf.com>
Subject Re: _esql_connection.connection should be public
Date Mon, 12 May 2003 10:44:00 GMT
Torsten Curdt wrote:
> 
> <snip/>
> 
> >>>I propose to set this field again to public access.
> >>
> >>Hm... what about changing getConnection() from protected to public?
> >>...not very happy about this either but...
> >
> >
> > It is no much difference.
> 
> What do you mean? I assume it's ok for you if you have it available
> through the getter?

Yes, it is ok.

> >>>I heavily use method calls from inside of xsp pages to methods which need
> >>>a DB connection. I pass the _esql_connection.connection to this methods.
> >>>But with private access this is no longer possible.
> >>>Why this was changed to private?
> >>
> >>Because you shouldn't use the ESQL classes directly ;-)
> >
> >
> > Is there another possibility to get the connection?
> 
> Well, from a pratical POV I can understand you might wanna re-use
> the same connection. But do you really need to have the *same*
> connection? Just curious... What do you do?

No, I don't need the same connection ;-)
But I don't know how to get another connection.
I want to put e.g. "Store Name" in all xsp's which comes from a DB table.

Regards,
Michael

Mime
View raw message