cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-1705) Servlet 2.3 compliance
Date Thu, 17 Jul 2008 14:55:32 GMT

    [ https://issues.apache.org/jira/browse/CXF-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614375#action_12614375
] 

Glen Mazza commented on CXF-1705:
---------------------------------

I'm -0.5 on this.  Servlet 2.3 is Tomcat 4.x--that's kind of old, isn't it?  I think this
change would be of limited benefit because CXF still needs JDK 5.0+.  I would say, security-wise,
CXF web services should not be running on something as old as Tomcat 4.x--go to Axis 1.x for
that.  Another concern is that if you advertise that CXF supports Tomcat 4.x+, might people
think that CXF is kind of old and hasn't been updated and modernized over the past few years.


> 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.


Mime
View raw message