Community
Participate
Working Groups
Build Identifier: 3.5 This is a fixture. Here we discussed a problem http://www.birt-exchange.org/org/forum/index.php/topic/22953-jndi-datasource/. And a bug was created by Lin Zhu https://bugs.eclipse.org/bugs/show_bug.cgi?id=353143 It says that: Description Lin Zhu 2011-07-26 13:39:38 EDT In current JNDI support, if user provide username/password in connection property, after acquire a JNDI DataSource, we will first try to connect using the username/password with API java.sql.DataSource.getConnection(String,String). If the API call failed with either a SQLException or UnsupportedOperationException, we will then try to use API java.sql.DataSource.getConnection() which includes no authentication information. I think it would be nice, if there was a way to control the "getConnection" process. For example, provide some property which will enable or disable on of these options. Reproducible: Always Steps to Reproduce: 1. create design supporting JNDI 2. deploy under Jboss 3. run the report
Linking with the original #353143 entry. The current way to bypass the call to #getConnection(String,String) is *not* to specify the username and password values in the data source properties. Property values can be dynamically changed via the Property Binding feature and/or Java scripting feature.
