"adrian(a)jboss.org" wrote :
| The handling of overrides from the management console
| to these original deployments is a different concern.
|
This wasn't something I had in the original profile design.
In fact for a long time I assumed that JON was going to implement this
via some plugin to the profile service .
i.e. it would set the pre-determined managed objects of the deployment
(based on what has been overridden in the console and in its own repository)
before it got deployed.
The requirements then moved to be based on ManagedObjects.
After I did the initial work this, I posted that I thought the console operations should
be intercepted by the profile service using a mechanism similar to
what JBossCache does using AOP (including "transactional" change sets).
i.e. the ManagedObject/Fields would be enhanced with interceptors to trap
changes which would be persisted and progogated to the server(s).
But this was then rewritten to use ManagedDeployments and the AOP approach
got dropped. Which is where I've kind of lost sight of where this was going. :-)
I didn't expect it would end up with both the profile source(s) and console
edits in the same repository spi. :-)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192192#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...