DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26414>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26414 UserTransaction bound in comp/env Context when using ResourceLink Summary: UserTransaction bound in comp/env Context when using ResourceLink Product: Tomcat 5 Version: 5.0.18 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] currently it is not possible to use ResourceLinks to bind a UserTransaction in the java:comp context of a web application because the way it is implemented ResourceLinks are always bound in the java:comp/env context. I stumbled across this because I thought it would make sense to configure my transaction manager only in one place and have all my webapps access it via ResourceLinks instead of copying the configuration for each webapp but that did not work. The current behaviour is a little hard to understand and IMHO it doesn't hurt to treat ResourceLinks pointing to a UserTransaction differently. I have attached a patch that does this. Testing the patch I found that the Context implementation does not seem to throw NameAlreadyBoundException when a name already exists and a bind fails (therefore after applying the patch you get a warning whenever a UserTransaction is bound via a ResourceLink). Shall I file this as a separate report? Thanks in advance --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
