"bstansberry(a)jboss.com" wrote : "adrian(a)jboss.org" wrote :
| | Ok but as it stands, the profile service doesn't know about these deployments
| | unless the server is the singleton. Which means the console can't modify them
either.
|
| Yes, that's the fundamental wrong thing about the current
HASingletonDeploymentScanner. With the division of function into 2 parts that I
described, the registration as part of subprofile function needs to happen regardless of
whether the node is master.
Which was also the problem with the refactoring of the bootstrap; these deployments were
not visible to the profile service until I updated the ProfileServiceBootstrap to expose
them.
That all components are know to the profile service and can be exposed to jon needs to be
a goal.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192220#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...