[
https://issues.apache.org/jira/browse/CXF-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614427#action_12614427
]
Hani Suleiman commented on CXF-1705:
------------------------------------
Exactly what Daniel said.
There are tons of deployments that are still 2.3 (running with 1.5 JVMs). You
don't need to advertise that this works with tomcat 4.x, just don't explicitly
say it doesnt. If anyone tries to sue you for it, then you can say it doesnt
work with Tomcat 4.x.
The change I'm proposing is a one liner, and it makes everything work (or at
the very least, you can serve up WSDLs, handle requests, and so on). Without
it, the servlet cannot service any requests at all.
I don't want to get into a debate about it, but to be honest, every single
reason you gave against this patch was...dubious at best! If youre still
unconvinced I'll gladly post more refuting every one of them ;)
> Servlet 2.3 compliance
> ----------------------
>
> Key: CXF-1705
> URL: https://issues.apache.org/jira/browse/CXF-1705
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.1.1
> Reporter: Hani Suleiman
> Fix For: 2.1.2
>
> Attachments: cxf-1705.patch
>
>
> Currently there is one call to the servlet 2.4 API in ServletController. This
> can be made 2.3 compatible by specifying the encoding in the
> setContentType(...) call. Attached is a patch to fix this, and enable cxf to
> run in any servlet 2.3 container.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
