j2ee 1.4???

[cesar]

Hello,

jet I have read that spring-ws requires j2ee 1.4.
I try to execute in j2ee 1.3 (was 5.1), and throws exception:



org.springframework.web.util.NestedServletExceptio n: Handler processing failed; nested exception is java.lang.NoSuchMethodError: javax.servlet.http.HttpServletResponse: method setCharacterEncoding(Ljava/lang/String;)V not found
java.lang.NoSuchMethodError: javax.servlet.http.HttpServletResponse: method setCharacterEncoding(Ljava/lang/String;)V not found


is this the only cause why requires j2ee 1.4??? could i try modify this call localy and build spring-ws and then works with j2ee 1.3???

thanks in advance,
César.

[Arjen Poutsma]

Hello,

jet I have read that spring-ws requires j2ee 1.4.
I try to execute in j2ee 1.3 (was 5.1), and throws exception:



org.springframework.web.util.NestedServletExceptio n: Handler processing failed; nested exception is java.lang.NoSuchMethodError: javax.servlet.http.HttpServletResponse: method setCharacterEncoding(Ljava/lang/String;)V not found
java.lang.NoSuchMethodError: javax.servlet.http.HttpServletResponse: method setCharacterEncoding(Ljava/lang/String;)V not found


is this the only cause why requires j2ee 1.4??? could i try modify this call localy and build spring-ws and then works with j2ee 1.3???


The only major reason I listed J2EE 1.4 is because that includes SAAJ and the javax.xml.namespace.QName class, which are essential. Obviously, those classes can be found elsewhere.

The setCharacterEncoding thing you found is not necessary and can be removed from the codebase. Unfortunately, I don't have much time right now (SpringOne is around the corner), but you can do it yourself by removing the offending line in org.springframework.ws.transport.http.MessageHandl erAdapter, around line 70, and create your own jar by doing an "ant dist".

Can you file an issue (http://opensource.atlassian.com/projects/spring/browse/SWS) for it? I will fix it ASAP.

Thanks,
Arjen

[Arjen Poutsma]

I've created an issue here (http://opensource.atlassian.com/projects/spring/browse/SWS-31).

[decrypt]

Please resolve this issue. We cannot deploy to several of our clients now due to this incompatibility with J2EE 1.3. Jurgen had a work around he implemented elsewhere in spring. I believe it was appending the character set to the content type.

[Arjen Poutsma]

It has been fixed in svn. You can check out the source code using svn and the following svnroot https://svn.sourceforge.net/svnroot/springframework/spring-projects/trunk/spring-ws/. I will create a snapshot this weekend.

[decrypt]

Thank you for your quick response. Genuinely appreciated.

[robertobradley70]

What is this j2ee 1.4???
Anyone tell me... (http://www.members.webs.com/MembersB/editAppPage.jsp?app=blog&pageID=254198686&token=null#blog/)