[JBoss JIRA] (WFCORE-295) Add unit tests for Default*DescriptionProvider
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-295?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-3504 to WFCORE-295:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-295 (was: WFLY-3504)
Component/s: Domain Management
(was: Domain Management)
> Add unit tests for Default*DescriptionProvider
> ----------------------------------------------
>
> Key: WFCORE-295
> URL: https://issues.jboss.org/browse/WFCORE-295
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management
> Reporter: Tomaz Cerar
>
> We need proper tests for at least
> - DefaultResourceAddDescriptionProvider
> - DefaultResourceDescriptionProvider
> - DefaultOperationDescriptionProvider
> as they are now tested as part of subsystem tests but they themselfs don't have any proper tests.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (WFCORE-294) support a form of modular XML configuration file
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-294?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-3510 to WFCORE-294:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-294 (was: WFLY-3510)
Component/s: Domain Management
(was: Domain Management)
> support a form of modular XML configuration file
> ------------------------------------------------
>
> Key: WFCORE-294
> URL: https://issues.jboss.org/browse/WFCORE-294
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: James Strachan
> Assignee: Jason Greene
> Priority: Minor
>
> I realise the history of wildfly & that things used to use many XML files and there was a move to unify things. But some modularity of configuration can be a good thing ;)
> With layered products it would be handy to allow separate XML configuration files to configure separate layers/features/parts. e.g. one for web, one for FSW, one for Infinispan/JDG, one for Portal and so forth. e.g. a layered product could release its own XML configuration file by default.
> Rather than it being subsystem specific (e.g. each layer may need to define a database) its more a way of grouping parts of the XML into a separate underlying source XML file.
> e.g. so folks could combine any of the (say) 4 XML files for web / FSW / JDG / Portal to make a configuration for a new wildfly container with different pieces depending on how folks want to map features to JVMs.
> e.g. rather than specifying a single XML file to startup, we'd allow specifying N different XML files with 1 configuration file being the default file used for adding new subsystems; otherwise the configuration system would remember which file a particular bit of configuration comes from; so if its changed, it knows which configuration needs to be written to which file.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (WFCORE-294) support a form of modular XML configuration file
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-294?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-294:
------------------------------------
Assignee: Alexey Loubyansky (was: Jason Greene)
> support a form of modular XML configuration file
> ------------------------------------------------
>
> Key: WFCORE-294
> URL: https://issues.jboss.org/browse/WFCORE-294
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: James Strachan
> Assignee: Alexey Loubyansky
> Priority: Minor
>
> I realise the history of wildfly & that things used to use many XML files and there was a move to unify things. But some modularity of configuration can be a good thing ;)
> With layered products it would be handy to allow separate XML configuration files to configure separate layers/features/parts. e.g. one for web, one for FSW, one for Infinispan/JDG, one for Portal and so forth. e.g. a layered product could release its own XML configuration file by default.
> Rather than it being subsystem specific (e.g. each layer may need to define a database) its more a way of grouping parts of the XML into a separate underlying source XML file.
> e.g. so folks could combine any of the (say) 4 XML files for web / FSW / JDG / Portal to make a configuration for a new wildfly container with different pieces depending on how folks want to map features to JVMs.
> e.g. rather than specifying a single XML file to startup, we'd allow specifying N different XML files with 1 configuration file being the default file used for adding new subsystems; otherwise the configuration system would remember which file a particular bit of configuration comes from; so if its changed, it knows which configuration needs to be written to which file.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (WFCORE-292) mod_proxy incompatible with logout mechanism
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-292?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-3561 to WFCORE-292:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-292 (was: WFLY-3561)
Affects Version/s: (was: JBoss AS7 7.2.0.Final)
Component/s: Domain Management
(was: Domain Management)
> mod_proxy incompatible with logout mechanism
> --------------------------------------------
>
> Key: WFCORE-292
> URL: https://issues.jboss.org/browse/WFCORE-292
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Jason Greene
> Assignee: Jason Greene
> Attachments: apache_mod_proxy_mgmt.conf, Screenshot_proxy_logs.png
>
>
> We need to either outlaw proxies, or to make sure the console works with them.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (WFCORE-291) Handle mixed-domain transformation use cases involving splitting out new subsystems
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-291?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-3563 to WFCORE-291:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-291 (was: WFLY-3563)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: (was: 9.0.0.Beta1)
> Handle mixed-domain transformation use cases involving splitting out new subsystems
> -----------------------------------------------------------------------------------
>
> Key: WFCORE-291
> URL: https://issues.jboss.org/browse/WFCORE-291
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Brian Stansberry
>
> This may end up needing subtasks.
> We need to be able to handle the mixed-domain transformation issues that arise when a subsystem is split out from a previously existing subsystem.
> 1) The registering slave will have no version info for the new subsystem. The new subsystem needs to be able to register a transformer for the logical equivalent of the 'null' version.
> 2) It needs to be possible to register a discard for the root resource of a subsystem. For example, when jsf was split out, the presence of the subsystem was equivalent to the default behavior of the legacy 'web' subsystem, so jsf could just be discarded.
> 3) It needs to be possible for one subsystem to issue a reject transformation if the another subsystem is not configured. For example, when jsf was split out it would have been valid for a reject transformation to have been applied by web if the jsf subsystem was not present, since the legacy slave will have jsf. (It's ok this reject wasn't done; I'm just using jsf/web as an example.)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (WFCORE-289) Emit notifications for servers in domain mode
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-289?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-3602 to WFCORE-289:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-289 (was: WFLY-3602)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: (was: 9.0.0.Beta1)
> Emit notifications for servers in domain mode
> ---------------------------------------------
>
> Key: WFCORE-289
> URL: https://issues.jboss.org/browse/WFCORE-289
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
>
> emit notifications related to server lifecycle in domain mode:
> * server-started
> * server-stopped
> * server-restarted
> * server-destroyed
> * server-killed
> These notifications should be emitted from the corresponding server-config resource (under /host=XXX/server-config=YYY)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month