[weld-issues] [JBoss JIRA] (WELD-1549) ConversationContextActivator calls Request.getParameter(), which forces form data to be parsed

Tue, 19 Nov 2013 11:04:28 -0800

IMHO the stack traces show explicitly enough that CDI ServletListener is invoked before any filter, thus rendering any filter configuration useless regarding request encoding / parameter parsing.
This shows an interesting conflict in the specification, which seems to mandate early invocation of RequestListeners "A servlet request has started being processed by Web components." and filtering.

Furthermore in HttpContextLifecycle.requestInitialized() the ConversationContextActivator is definitely invoked before requestInitializedEvent.fire():
try {
if (conversationActivationEnabled)

{ conversationContextActivator.activateConversationContext(request); }

requestInitializedEvent.fire(request);
} catch (RuntimeException e) {

Therefore there seems to be no way to access the request by ServletListener either, completely independent of any possibility to manage ordering of ServletListener by deployment descriptor.

I am definitely looking forward to the availability of encoding support in Undertow/Wildfly.

Regards,
Thomas
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 
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues

Reply via email to