[
https://issues.jboss.org/browse/JBAS-9329?page=com.atlassian.jira.plugin....
]
Thomas Diesler commented on JBAS-9329:
--------------------------------------
12:51:30 PM) darranl: emuckenhuber, kkhan - what do you think? I am thinking maybe one
for Brian - this sounds like it is coming back into the realm of server group specific
config
(12:52:06 PM) darranl: the profiles could be extended to achieve this but not sure if that
is the intent for deployment related subsystem state
(12:54:07 PM) darranl: tdiesler, yes I think all subsystems potentially have state that
affects the deplyments so the admin can choose if that state is really shared but in this
case I think it is moving over to the deployments now also affecting the state
(01:02:41 PM) tdiesler: darranl, in OSGi ConfigAdmin is the standard service that that
(3rd party) bundles use to configure their own services. For example the HttpService gets
its port configured that way. You might want this to be equivalent to our server-socket
config
(01:03:53 PM) tdiesler: How about not replicating ConfigAdmin state for now and we cross
that bridge we we need to support replicated OSGi frameworks
(01:04:30 PM) tdiesler: A lot more thought might need to go into what it means to have
replicated frameworks
(01:08:35 PM) darranl: tdiesler, I am thinking this is one for Brian - the problem is once
it is in the domain model it is replicated
Restore persistent configuration changes
-----------------------------------------
Key: JBAS-9329
URL:
https://issues.jboss.org/browse/JBAS-9329
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.0.0.Beta4
The ConfigAdminService used the ServerConfigurationPersister in the past.
The code is currently commented out
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira