|
||||||||
|
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 |
||||||||
Just quick note for this:
In order to handle the unexpected ConversationContextException (for example WELD-000321), we have to wrap the ConversationFilter instead of using the ServletListener, so the new SPI has to be applied to both Listener and Filter, also, since we need to add extra filter before ConversationFilter, so the SPI has to be able to apply to the Customized Filter as well.
And also the regexp sometime is very expensive, so in the sample code I provided, I only do the URI regexp match once (in the Listener), if it match, set a flag in the request's attribute map, the filter will only check the special flag, this way the customized filter can do the same trick without call regexp multiple times. I suppose that the new SPI can do that too.
Thanks