|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I think it's a good idea to allow the developers to configure the context paths Weld should not process (i.e. activate the contexts). Not only for static resources but also for other "special" components which do not require CDI. This would be of course againts the spec (6.7 Context management for built-in scopes), in other words a non-portable feature (not the first one). Ideally the developer could specify a regexp to match context paths Weld should process (by default all).
Note that Seam 2 allowed something similar (configuration of filter components).