[jboss-dev-forums] [Design of POJO Server] - Handling more complex properties in a ManagedComponent

bytor99999 do-not-reply at jboss.com
Thu Apr 26 15:57:40 EDT 2007


So currently there are just Simple ManagedProperty(s) in a ManagedComponent. So for DataSource, properties like jndi-name, and connection-url can easily be handled. However, support for a property like connection properties cannot be handled. Since there can be 0-many connection properties defined in a DataSource, the ManageProperty object might need to have more than one value, and is not currently supported.

As an Example, in the Oracle XA datasource in the docs dir has three <xa-datasource-property> tags. the name, attribute is what distinguishes the property. <connection-property> is another tag example.


  | <xa-datasource-property name="URL">jdbc:oracle:oci8:@tc</xa-datasource-property>
  | <xa-datasource-property name="User">scott</xa-datasource-property>
  | <xa-datasource-property name="Password">tiger</xa-datasource-property>
  | 

Some other ManagedComponents and Templates might have other similar type of properties. Some might require just a List of Properties, whereas some might require a Map of Properties.

So a LoginModule can have many module-options, So if there was a Map for the module-options, the key being the name attribute value, and the value in the Map is the value of that module-option.

An example of a List property might be the URIList of the VFSDeploymentScanner.

Can this change be made?

Mark

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041165#4041165

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041165



More information about the jboss-dev-forums mailing list