[jboss-dev-forums] [Design of JCA on JBoss] - Re: JBAS-1437 RARMetaDataRepository

[adrian@jboss.org]

"weston.price at jboss.com" wrote : 
  | Obviously this is not the only reason for the repository, but I can't quite see how we can get away with getting rid of the RAR names from our deployments. 
  | 

If you are doing this in two phases (parse/runtime) it should be automatic?

The parsing stage populates the repository, the runtime stage (the actual
construction/configuration of the MBeans/Pojos) should have all the parsed rar information
in the repository by then?

What you really need is something I've not yet done in the MC
which is the "write your own dependency".
Basically allowing users to define and implement their own DependencyItem.

You can sort of already do it with a bit of hacky code.
e.g. for MBeans you can subclass ServiceDependencyMetaData
to implement something more dynamic in the visitor callback
but you need to update the ServiceMetaData by hand with your new dependency.

But what I'd really like is for the dependencies to support wildcards, e.g.


  | <mbean code="MCF">
  |    <depends xmlns="urn:jboss-jca:5.0" rar-name="some.rar"/>
  | </mbean>
  | 

Where urn:jboss-jca:5.0:depends will unmarshal to a dependency implementation
that knows how to look at the rar metadata repository at runtime.

The attributes of this dependency could then have all the query parameters
we'd like to support for looking up implementations, e.g. give me a rar that supports 
JmsXA outbound (not such the hardwired rar name).

If nothing supports it (yet), you just return false from isResolved() in your
DependencyItem implementtaion.

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

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