Christopher Oliver wrote:
The cocoon object now supports a new function
getConnection([String] dataSourceName);
This looks cool... but, continuing my rant about oversimplification, why does the _cocoon_ object hold methods to access database connections ? AFAIK, this object is meant to give access to the enclosing context : request, response, manager (but *not* the environment, which IMO should be removed). So why JDBC stuff there ?
Shouldn't we start to structure the JS stuff in libraries that people load whenever (and only when) they need them rather than mix everything in a single object ?
You are absolutely correct. However, for now I'd prefer not to invent new objects, and this was the most convenient place to put it, so others could try it.
