Description Justin Spadea 2012-02-06 12:24:56 EST

This was supported until we simplified the editor to remove the "Use an existing JNDI data source" option. We do need to support this though, so we should add a checkbox to the "Deploy as JNDI" section.

New parameter: jndiApplicationAuth

When true, deployment will define the resource-refs and data sources as auth="Application", otherwise it will continue to use auth="Container". Not all data sources support this, so it is up to the user to only check the box when their data source won't throw an error. For example, Tomcat's default data source "BasicDataSource" throws an error when trying to specify credentials from the application - you must only use container-based auth with that class.

I'm going to remove the jndiuser and jndiPassword parameters from the binding, we'll just reuse sqlID and sqlPassword. Deployment will fill these in automatically when jndiApplicationAuth is set true.