[JBoss JIRA] (AS7-3854) MimeMappingAdd and MimeMappingRemove don't affect the runtime
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-3854:
-------------------------------------
Summary: MimeMappingAdd and MimeMappingRemove don't affect the runtime
Key: AS7-3854
URL: https://issues.jboss.org/browse/AS7-3854
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Web
Reporter: Brian Stansberry
Assignee: Tomaz Cerar
Fix For: 7.1.1.Final
While reviewing https://github.com/jbossas/jboss-as/pull/1549 I see that MimeMappingAdd and MimeMappingRemove just update the model but have no effect on the runtime services. If context.isNormalServer() == true, they should either impact a runtime service or put the server into reload-required.
Note that the current behavior may make sense during boot if the overall subsystem design has a parent resource adding a Stage.RUNTIME handler that reads child resources and uses their state to set up runtime services. But it's definitely not correct if these operations are performed independently.
As part of processing pull request 1549 I'll add TODO comments in these classes referencing this JIRA.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] (AS7-2171) Revisit deployment triggering subsystem startup
by Thomas Diesler (Created) (JIRA)
Revisit deployment triggering subsystem startup
-----------------------------------------------
Key: AS7-2171
URL: https://issues.jboss.org/browse/AS7-2171
Project: Application Server 7
Issue Type: Task
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Currently the RestEasyIntegrationTestCase deploys a JAXRS endpoint that integrates with an OSGi service. The endoint deployment does not trigger the OSGi subsystem to start up, but depends on the compendium being deployed. The compendium gets deployed during OSGi subsystem startup.
There is currently no way for a deployment foo to declare a dependency on deployment bar when bar gets deployed during subsystem startup, which gets triggered by deployment foo.
OSGi has the notion of dynamic package import which seems to be required here for non-osgi deployments
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years