Community
Participate
Working Groups
Add new wizard to create SQL Database Binding. Story: Developer opens the DD editor and clicks the Resource Bindings tab Developer clicks Add button in Resource Binding tab Developer selects SQL Database Binding to launch the db binding wizard ( ) Resting Service Binding (*) SQL Database Binding Developer chooses a connection from the Database Connection drop-down (populated from set of connections configured in the workspace), accepts the default binding name (based on the name of the connection), and click Finish. Developers can also launch the wizard to create a new Database Connection. The information of the selected (created) database binding is written to EGLDD
Tony, in SQLDatabaseBinding, there exists a 'name' property, from my understanding, it refers to 'user name' while connection database, if my understanding is correct, then it should be changed to 'userName', and add a 'name' property for the item, now no property for newly added item. The checked code can added 4 properties, for others, need discussion about it. Please review code.
Created attachment 202502 [details] Check in code Tony, please review code
Justin - to avoid the situation we found ourselves in RBD where we didn't store enough parameters to create, for example, the context.xmL, can you confirm we're storing enough of the db connection parameters and in a way such that a deploy operation to create a context.xml will have what it needs? My thought would be to add every db property we can to the DD ...
The following properties are the minimum needed to configure a data source in context.xml for Tomcat: JNDI name User name Password JDBC URL Driver class name There are other data source properties that can be set, but we haven't exposed them before. Users are free to edit context.xml if they don't like the settings. Examples include: maxWait="5000" auth="Container" maxIdle="2" maxActive="4" type="javax.sql.DataSource" The issue in RBD was configuring a data source on WAS. The RAD tooling in the EAR's DD expected the pieces broken up differently. There was sufficient information if you had a workspace database connection, but the problem was when the values came from the build descriptor - and I don't remember exactly what settings WAS needed that we didn't have.
name refers to the name of the binding sqlId is the username (In reply to comment #1) > Tony, in SQLDatabaseBinding, there exists a 'name' property, from my > understanding, it refers to 'user name' while connection database, if my > understanding is correct, then it should be changed to 'userName', and add a > 'name' property for the item, now no property for newly added item. > > The checked code can added 4 properties, for others, need discussion about it. > Please review code.
see this bug 356157 for egldd model changes (In reply to comment #4) > The following properties are the minimum needed to configure a data source in > context.xml for Tomcat: >
Created attachment 202649 [details] Complete the feature
Complete the feature
close the feature
