Summary: | Error in the JNDI Generic JavaBean Resources documentation | ||
---|---|---|---|
Product: | Tomcat 7 | Reporter: | Giulio Quaresima <giulio.quaresima> |
Component: | Documentation | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux | ||
Attachments: | server.xml and the test classes in maven format |
Description
Giulio Quaresima
2013-10-25 11:50:00 UTC
Created attachment 30969 [details]
server.xml and the test classes in maven format
This behavior is controlled by the singleton attribute of the factory. The default is to create singleton resources as that is what users expect even though the J2EE spec suggests that a new object should be created on each lookup. I'll go through the JNDI docs and expand any statements like the one you quote below so that the full picture is available. OK, this is true for Tomcat 7 but it's not, as I can see, for the still supported 6.x version. Moreover, I think it would be better to mention the 'singleton' option also in the documentation page I refer to, in order do avoid misunderstanding. Thanks (In reply to Mark Thomas from comment #2) > This behavior is controlled by the singleton attribute of the factory. The > default is to create singleton resources as that is what users expect even > though the J2EE spec suggests that a new object should be created on each > lookup. > > I'll go through the JNDI docs and expand any statements like the one you > quote below so that the full picture is available. JNDI how-to updated in 7.0.x for 7.0.48 onwards and 8.0.x for 8.0.0-RC6 onwards. |