Bug 357657

Description Justin Spadea 2011-09-14 12:17:37 EDT

After a lengthy discussion about resource bindings it became clear that there are pieces of information that will differ from machine to machine, and those that will differ between development and production. For example SQL information will be different among developer machines during development (different credentials, JDBC jar paths, etc).

Given this, there should be a way to define this information that is local to your machine. Each resource binding type would have two options: 1) specify a URI that describes how to access the information. 2) Specify the information directly (as is done today).

Users will be able to define named binding definitions in preferences. These named bindings will provide the real binding information as you would have formerly defined in the DD file. The definitions will have a unique identifier. The deployment descriptor can then point to these definitions via their unique identifier when running inside the IDE.

The URI for a named resource binding in the deployment descriptor will have different schemes, and each scheme will have a handler that knows how to deal with it. Here are some example schemes for a named REST binding:

1) http://localhost:8080/project/restservices/foo - The deployed service will be invoked directly.
2) workspace://ProjectName/pkg.Service1 - The service will be run locally on a test server.
3) preferences://Service1 - We'll look at the definition named 'Service1' from preferences, which will then tell us how to invoke it (could be http:// or workspace://, or anything else that has defined a handler).

For SQL the URI might look like:
1) jndi://jdbc/SAMPLE
2) workspace://nameOfConnectionProfile
3) preferences://someUniqueBindingId
Your development DD file would probably point to preferences:// and then the value in preferences would be either jndi:// if right now you're running on an app server, or workspace:// if you're running on the jetty test server. It is up to the user to configure the JNDI data source on the app server.

The "Add a Resource Binding" wizard will need to be updated. When you pick REST or SQL, the next page should let you choose whether you want this to be a named binding or whether you want to explicitly define the information. If you choose the named binding option then you should be able to pick from the current list of available binding definitions in preferences (would be nice if you could define a new one right there, or at least pop up the preference page to edit the definitions and then refresh the list in the wizard when the preference page is closed).

The details section of resource bindings in the DD editor should also let you choose between a named binding (maybe a drop-down with a button to open the preference page for configuration) vs explicitly defining binding information (as is done today). The list of properties for an SQL binding would then remove the "JNDI Name" property, since in this case you would use the named option instead of the explicitly defined option.