[
https://issues.jboss.org/browse/WFLY-2533?page=com.atlassian.jira.plugin....
]
Norbert Kozłowski edited comment on WFLY-2533 at 12/2/13 9:54 AM:
------------------------------------------------------------------
It produces such error:
{code}
{"JBAS014671: Failed services" =>
{"jboss.undertow.deployment.default-server.default-host./business_alerts.UndertowDeploymentInfoService"
=> "org.jboss.msc.service.StartException in service
jboss.undertow.deployment.default-server.default-host./business_alerts.UndertowDeploymentInfoService:
Failed to start service
Caused by: java.lang.NullPointerException"}}
{code}
was (Author: khozzy):
It produces such error:
{code:title= jboss-web.xml}
{"JBAS014671: Failed services" =>
{"jboss.undertow.deployment.default-server.default-host./business_alerts.UndertowDeploymentInfoService"
=> "org.jboss.msc.service.StartException in service
jboss.undertow.deployment.default-server.default-host./business_alerts.UndertowDeploymentInfoService:
Failed to start service
Caused by: java.lang.NullPointerException"}}
{code}
Add ability to set default character encoding on a subsystem level
------------------------------------------------------------------
Key: WFLY-2533
URL:
https://issues.jboss.org/browse/WFLY-2533
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web (Undertow)
Reporter: Stuart Douglas
Assignee: Tomaz Cerar
Fix For: 8.0.0.CR1
Stuart: the charset one should be pretty simple, just an attribute on
<servlet-container?
Stuart: ideally we would also have it in jboss-web.xml as well
Stuart: I should also add an option to use the connector encoding
Stuart: as connectors have their own encoding set
Stuart: that is used to decode the URL
Stuart: we should have an option to use the connector encoding as the default encoding
--
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