3 Replies Latest reply on Aug 12, 2009 10:18 AM by jesper.pedersen

    proposal for JBossRA 2.0 metadata

    jeff.zhang

      We would like to extend the jboss-ra.xml for more feature.

      1. possibility to add additional bean validation groups.

       <bean-validation-groups>
       <bean-validation-group>com.mycompany.myproject.bv.Group1</bean-validation-group>
       <bean-validation-group>com.mycompany.myproject.bv.Group2</bean-validation-group>
       </bean-validation-groups>
      

      see https://jira.jboss.org/jira/browse/JBJCA-135

      2. currently we use "ra-config-property" to override configuration value like this
       <ra-config-property>
       <ra-config-property-name>StringRAR</ra-config-property-name>
       <ra-config-property-type>java.lang.String</ra-config-property-type>
       <ra-config-property-value>XMLOVERRIDE</ra-config-property-value>
       </ra-config-property>
      

      It is just work for the config-property in the resourceadapter element.
      Now we need it can work also for other elements includes:
      activationspec, adminobject, authentication-mechanism, connection-definition(managedconnectionfactory)

      I would like add the attribute name "override-element", that figure it override the configuration value. For example:
       <ra-config-property override-element="connection-definition">
       <ra-config-property-name>StringRAR</ra-config-property-name>
       <ra-config-property-type>java.lang.String</ra-config-property-type>
       <ra-config-property-value>XMLOVERRIDE</ra-config-property-value>
       </ra-config-property>
      


        • 1. Re: proposal for JBossRA 2.0 metadata
          jesper.pedersen

          1) Yes

          2) Yes, but define a type for the override-element such that it only can have our defined values (xsd:restriction on xsd:token)

          We can change the XSD until we release the first version, so we'll work through the use-cases over time.

          • 2. Re: proposal for JBossRA 2.0 metadata
            jeff.zhang

            for
            2) yeah. I have add the restriction. please see https://jira.jboss.org/jira/browse/JBMETA-219

            1) We also need an attribute to figure out which bean we use bean validation group against, like :

             <bean-validation-groups bean-id="org.jboss.jca.test.deployers.spec.rars.ra16standard303jbossra.TestResourceAdapter">
             <bean-validation-group>com.mycompany.myproject.bv.Group1</bean-validation-group>
             <bean-validation-group>com.mycompany.myproject.bv.Group2</bean-validation-group>
             </bean-validation-groups>
            


            • 3. Re: proposal for JBossRA 2.0 metadata
              jesper.pedersen

               


              We also need an attribute to figure out which bean we use bean validation group against, like :


              The groups should be used for the entire RAR archive IMHO - e.g. if people wants more advanced features they'll use the BV API.