[jboss-as7-dev] access to the ModelNodeRegistration during handling of an operation and during deployment

Brian Stansberry brian.stansberry at redhat.com
Thu May 12 09:30:14 EDT 2011


Thanks, Stefano. Your description here ties to my understanding of our 
chat yesterday, but in nice formal language so I know for sure I 
understand. :)

I was concerned about giving handlers complete access to the model 
registry (i.e. a ref to the root ModelNodeRegistration) but from what 
you describe this can be more limited; i.e. the ability to register a 
new submodel under some parent that is defined by the call context.

Emanuel, the 2) case below ties into what you're doing on exposing 
runtime state associated with a deployment. My assumption was that would 
involve DUPs being able to register resources/handlers under the portion 
of the tree that represents the deployment.


On 5/12/11 1:05 AM, Stefano Maestri wrote:
> Hi All,
>
> I'm trying to resume here the discussion I had yesterday on IRC with
> Brian and Jesper.
>
> Basically JCA needs to have and already deployed instance of
> ResourceAdapter when adding its metrics and some operation. The reason
> for that is because some operation and metrics availability are known
> only at runtime, depending from RA status and/or vendor specific feature
> known only.
>
> Speaking from a Model point of view the basically issue is to have
> access to the ModelNodeRegistration when the RA instance is created and
> these runtime infos are available. There are 2 cases:
>
> 1) during handling ADD operation for a DataSource or special
> ResourceAdapter creation withour rar deployment (like hornetQ).
> 2) during foo.rar deployment chain
>
> We have also discussed where we can put these operation in the model
> tree. Also in this case there are two possible places:
>
> 1) at subsystem level for special no-deployment RA (DataSources and
> HornetQ atm). So we will obtain something like
> /subsystem=datasource/data-source=myDS and /subsystem=hq/ra
> 2) at DUP level /deployment=foo.rar Having this deployment support we
> can remove the current operation in /subsystem=resource-adapters that is
> redudant, referring the same RA (or better a subset of deployed ones)
>
> Hoping to have written all the matters discussed, feel free to integrate
> and/or ask.
>
> regards
> S.
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat


More information about the jboss-as7-dev mailing list