[
https://issues.jboss.org/browse/AS7-3854?page=com.atlassian.jira.plugin.s...
]
Tomaz Cerar closed AS7-3854.
----------------------------
Resolution: Rejected
Problem is that adding/removing mime type at run-time would really complicate
implementation.
add/remove applies new mime type to container but container only propagates that data to
deployed application at deploy time.
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.2.0.Alpha1
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