https://issues.apache.org/bugzilla/show_bug.cgi?id=50159
--- Comment #4 from david jencks <djen...@apache.org> 2010-10-26 19:33:10 EDT --- the aharable/non-sharable attribute refers to the connections, not the datasource/connection factory. The spec is very clear that unless clearly indicated otherwise or unless the object is immutable, each jndi lookup should return a new object. There are some tests for this for datasources in the ee tck. Sharable refers to how many connection handles can be associated with a managed connection (in the same thread and same transaction). Sharable means that if you get multiple connections (in the same thread and tx) they can all be backed by the same managed connection. non-sharable means each connection needs its own managed connection. Typically you'd use non-sharable connections if you got the connection with some unique data such as username/pw that is different for each connection. Some resource adapters also don't support sharable connections. I have no problem relaxing this (IMO very silly) requirement but please don't misuse the sharable flag for it. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
