> > Not sure. Would it be possible to code ResultSet so that .close does the
> > connection return thingy? That should be ok I think.
> Yes, that might be a nice solution. The jBoss Connection would
> have to track open ResultSets. It draws a connection from the pool
> to support open ResultSets--otherwise it remains a virtual
> connection.
Something like that. I can't put my finger on it right now, but it should be
possible to code this fairly cleanly.
> Second question: how should PreparedStatements be managed? I
> can easily see a component developer using a connection per
> component instance so that he or she can reuse
> PreparedStatements. We don't necessarily want to draw a
> Connection from the pool just to support this. Any ideas?
Nope, it's a tricky one.
I would guess that when we get this right, the final solution will not be
complicated (just as the current jBoss container architecture is pretty
straightforward). It's just a matter of "feeling" the proper solution that
is missing IMHO... it will come...
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
