2 Replies Latest reply on Jul 11, 2006 8:36 PM by starksm64

    EAR Metadata

    bill.burke
    bill.burke Jul 11, 2006 8:32 AM

      This is in regards to EJBTHREE-617

      Maybe a generic metadata facility would be a better approach rather than a specifc jndi binding setting in jboss-app.xml? This way EAR subdeployment types can evolve without having to change EAR Deployer code. EARs already have the concept of additional metadata.

      This probably coincides with the Profile service as well.



      • 11382 Views
      • Tags:
        • 1. Re: EAR Metadata
          jicken
          jicken Jul 11, 2006 6:11 PM (in response to bill.burke)

          do you think of

          /** An arbitrary map of state associated with the deployment */
 public transient HashMap context = new HashMap();


          in DeploymentInfo filled via a generic key-value xml file describing the deployment?

          e.g. 

          <deployment-context>
 <jndi-root-context>my-ear</jndi-root-context>
 <2ndKey>2ndValue</2ndKey>
</deployment-context>


          resulting in the context hashmap {["jndi-root-context", "my-ear"], ["2ndKey", "2ndValue"]}


            • Actions
          • 2. Re: EAR Metadata
            starksm64
            starksm64 Jul 11, 2006 8:36 PM (in response to bill.burke)

            We already have the jboss5 metadata repository which is an extension of the aop metdata notions:

            http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73653

              • Actions