[jira] [Created] (CXF-6805) cxf-rt-transports-http adds Content-Type header to GET request

[Richard Stollar (JIRA)]

Richard Stollar created CXF-6805:


 Summary: cxf-rt-transports-http adds Content-Type header to GET 
request
 Key: CXF-6805
 URL: https://issues.apache.org/jira/browse/CXF-6805
 Project: CXF
  Issue Type: Bug
  Components: Transports
Affects Versions: 3.2.0
Reporter: Richard Stollar
Priority: Minor


Then generating a web service client from WSDL the request sent to the server 
has an additional Content-Type header.  Microsoft IIS 6.0 fails to process 
these requests and returns 200-OK with empty body. 
The Content-Type header should not be added to the http request when the method 
is GET.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CXF-6805) cxf-rt-transports-http adds Content-Type header to GET request

[Richard Stollar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Stollar updated CXF-6805:
-
Attachment: cxf-rt-transports-http.patch

This patch can be applied to fix the problem.

> cxf-rt-transports-http adds Content-Type header to GET request
> --
>
> Key: CXF-6805
> URL: https://issues.apache.org/jira/browse/CXF-6805
> Project: CXF
>  Issue Type: Bug
>  Components: Transports
>Affects Versions: 3.2.0
>Reporter: Richard Stollar
>Priority: Minor
> Attachments: cxf-rt-transports-http.patch
>
>
> Then generating a web service client from WSDL the request sent to the server 
> has an additional Content-Type header.  Microsoft IIS 6.0 fails to process 
> these requests and returns 200-OK with empty body. 
> The Content-Type header should not be added to the http request when the 
> method is GET.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CXF-6805) cxf-rt-transports-http adds Content-Type header to GET request

[Sergey Beryozkin (JIRA)]

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

Sergey Beryozkin commented on CXF-6805:
---

Hi, 

the code which initiates a WSDL query needs to set a an EMPTY_REQUEST_PROPERTY 
to true so that the branch checking if GET should have CT set or not runs (that 
branch does exclude CT for GET by default). The reason for it is that some 
legacy services do need GET + CT, example:

http://cxf.547215.n5.nabble.com/WebClient-Content-Type-Override-td4640790.html#a5765946

Can you please create another patch, somewhere where a WSDL query starts, there 
should be a code which sets EMPTY_REQUEST_PROPERTY to true. 

> cxf-rt-transports-http adds Content-Type header to GET request
> --
>
> Key: CXF-6805
> URL: https://issues.apache.org/jira/browse/CXF-6805
> Project: CXF
>  Issue Type: Bug
>  Components: Transports
>Affects Versions: 3.2.0
>Reporter: Richard Stollar
>Priority: Minor
> Attachments: cxf-rt-transports-http.patch
>
>
> Then generating a web service client from WSDL the request sent to the server 
> has an additional Content-Type header.  Microsoft IIS 6.0 fails to process 
> these requests and returns 200-OK with empty body. 
> The Content-Type header should not be added to the http request when the 
> method is GET.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CXF-6805) cxf-rt-transports-http adds Content-Type header to GET request

[Richard Stollar (JIRA)]

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

Richard Stollar commented on CXF-6805:
--

There's the problem. I tried to find somewhere where I could set the 
property but couldn't work it out.

When the header is set then this is the stack-trace I receive:

*Caused by: javax.xml.stream.XMLStreamException: ParseError at
[row,col]:[1,1]
Message: Premature end of file.
 at

com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:596)
 at
org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:1346)
 at
org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:1240)
 at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:1168)
 at

org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:219)
 ... 12 more*


*WSDLManagerImpl.loadDefinition(String url)*  must be where things start 
to go wrong. I couldn't find where the actual *Message* was being 
created in this flow. I'll look at it some more tomorrow.  I'm not 
really used to working with Maven projects and thus debugging this isn't 
something I have tried. I just rebuild the .jar files and re-run my test 
application with them - adding System.out.println() messages for debug.

Best regards,

Richard Stollar
See: My Site 




> cxf-rt-transports-http adds Content-Type header to GET request
> --
>
> Key: CXF-6805
> URL: https://issues.apache.org/jira/browse/CXF-6805
> Project: CXF
>  Issue Type: Bug
>  Components: Transports
>Affects Versions: 3.2.0
>Reporter: Richard Stollar
>Priority: Minor
> Attachments: cxf-rt-transports-http.patch
>
>
> Then generating a web service client from WSDL the request sent to the server 
> has an additional Content-Type header.  Microsoft IIS 6.0 fails to process 
> these requests and returns 200-OK with empty body. 
> The Content-Type header should not be added to the http request when the 
> method is GET.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (CXF-6806) don't mark the optional "encoding" parameter as required for cxf-java2wadl-plugin

[Freeman Fang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Freeman Fang reassigned CXF-6806:
-

Assignee: Freeman Fang

> don't mark the optional "encoding" parameter as required for 
> cxf-java2wadl-plugin
> -
>
> Key: CXF-6806
> URL: https://issues.apache.org/jira/browse/CXF-6806
> Project: CXF
>  Issue Type: Bug
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>
> otherwise we get exception like 
> [ERROR] Failed to execute goal org.apache.cxf:cxf-java2wadl-plugin:3.1.5 
> parsejavadoc (parsejavadoc) on project cxf-rest: The parameters 'encoding' 
> for goal org.apache.cxf:cxf-java2wadl-plugin:3.1.5parsejavadoc are missing or 
> invalid -> [Help 1]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CXF-6806) don't mark the optional "encoding" parameter as required for cxf-java2wadl-plugin

[Freeman Fang (JIRA)]

Freeman Fang created CXF-6806:
-

 Summary: don't mark the optional "encoding" parameter as required 
for cxf-java2wadl-plugin
 Key: CXF-6806
 URL: https://issues.apache.org/jira/browse/CXF-6806
 Project: CXF
  Issue Type: Bug
Reporter: Freeman Fang


otherwise we get exception like 
[ERROR] Failed to execute goal org.apache.cxf:cxf-java2wadl-plugin:3.1.5 
parsejavadoc (parsejavadoc) on project cxf-rest: The parameters 'encoding' for 
goal org.apache.cxf:cxf-java2wadl-plugin:3.1.5parsejavadoc are missing or 
invalid -> [Help 1]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CXF-6806) don't mark the optional "encoding" parameter as required for cxf-java2wadl-plugin

[Freeman Fang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Freeman Fang updated CXF-6806:
--
Affects Version/s: 3.1.5
   3.0.8
Fix Version/s: 3.0.9
   3.1.6
   3.2.0
  Description: 
otherwise we get exception like 
[ERROR] Failed to execute goal org.apache.cxf:cxf-java2wadl-plugin:3.1.5 
parsejavadoc (parsejavadoc) on project cxf-rest: The parameters 'encoding' for 
goal org.apache.cxf:cxf-java2wadl-plugin:3.1.5parsejavadoc are missing or 
invalid -> [Help 1]



  was:
otherwise we get exception like 
[ERROR] Failed to execute goal org.apache.cxf:cxf-java2wadl-plugin:3.1.5 
parsejavadoc (parsejavadoc) on project cxf-rest: The parameters 'encoding' for 
goal org.apache.cxf:cxf-java2wadl-plugin:3.1.5parsejavadoc are missing or 
invalid -> [Help 1]


> don't mark the optional "encoding" parameter as required for 
> cxf-java2wadl-plugin
> -
>
> Key: CXF-6806
> URL: https://issues.apache.org/jira/browse/CXF-6806
> Project: CXF
>  Issue Type: Bug
>Affects Versions: 3.1.5, 3.0.8
>Reporter: Freeman Fang
>Assignee: Freeman Fang
> Fix For: 3.2.0, 3.1.6, 3.0.9
>
>
> otherwise we get exception like 
> [ERROR] Failed to execute goal org.apache.cxf:cxf-java2wadl-plugin:3.1.5 
> parsejavadoc (parsejavadoc) on project cxf-rest: The parameters 'encoding' 
> for goal org.apache.cxf:cxf-java2wadl-plugin:3.1.5parsejavadoc are missing or 
> invalid -> [Help 1]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CXF-6806) don't mark the optional "encoding" parameter as required for cxf-java2wadl-plugin

[Freeman Fang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Freeman Fang resolved CXF-6806.
---
Resolution: Fixed

commit fix
http://git-wip-us.apache.org/repos/asf/cxf/commit/7d5a70ba for master
http://git-wip-us.apache.org/repos/asf/cxf/commit/8f624806 for 3.1.x-fixes 
branch
http://git-wip-us.apache.org/repos/asf/cxf/commit/83c9a094 for 3.0.x-fixes 
branch


> don't mark the optional "encoding" parameter as required for 
> cxf-java2wadl-plugin
> -
>
> Key: CXF-6806
> URL: https://issues.apache.org/jira/browse/CXF-6806
> Project: CXF
>  Issue Type: Bug
>Affects Versions: 3.1.5, 3.0.8
>Reporter: Freeman Fang
>Assignee: Freeman Fang
> Fix For: 3.2.0, 3.1.6, 3.0.9
>
>
> otherwise we get exception like 
> [ERROR] Failed to execute goal org.apache.cxf:cxf-java2wadl-plugin:3.1.5 
> parsejavadoc (parsejavadoc) on project cxf-rest: The parameters 'encoding' 
> for goal org.apache.cxf:cxf-java2wadl-plugin:3.1.5parsejavadoc are missing or 
> invalid -> [Help 1]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (CXF-6435) Support base64 for attachment encoding in CXF

[Freeman Fang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Freeman Fang reassigned CXF-6435:
-

Assignee: Freeman Fang

> Support base64 for attachment encoding in CXF
> -
>
> Key: CXF-6435
> URL: https://issues.apache.org/jira/browse/CXF-6435
> Project: CXF
>  Issue Type: Bug
>Reporter: Susan Javurek
>Assignee: Freeman Fang
>
> Description of the issue is in this forum post: 
> http://cxf.547215.n5.nabble.com/Setting-soap-attachment-Content-Transfer-Encoding-td3335835.html
> Attachment encoding in CXF doesn't support base64. AttachmentSerializer.class 
> in cxf-api contains the hardcoded value 
> writer.write(URLDecoder.decode(attachmentId, "UTF-8"));



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CXF-6807) Broken svn URL in http://cxf.apache.org/docs/jax-rs-advanced-features.html

[JIRA]

Tobias Schöneberg created CXF-6807:
--

 Summary: Broken svn URL in 
http://cxf.apache.org/docs/jax-rs-advanced-features.html
 Key: CXF-6807
 URL: https://issues.apache.org/jira/browse/CXF-6807
 Project: CXF
  Issue Type: Bug
  Components: Documentation
Reporter: Tobias Schöneberg
Priority: Minor


In 
http://cxf.apache.org/docs/jax-rs-advanced-features.html#JAX-RSAdvancedFeatures-Client
it somewhere sais "[...]please see this beans.xml" where "beans.xml" is a link 
to 

http://svn.apache.org/repos/asf/cxf/trunk/systests/jaxrs/src/test/java/org/apache/cxf/systest/jaxrs/resources/jms_server_config.xml

that link is broken, the correct URL would be

http://svn.apache.org/repos/asf/cxf/trunk/systests/jaxrs/src/test/java/org/apache/cxf/systest/jaxrs/jms/jms_server_config.xml

Regards, Tobi



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)