You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ax...@ws.apache.org on 2004/09/03 16:57:51 UTC
[jira] Created: (AXIS-1545) Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1545
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1545
Summary: Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
Basic Architecture
Versions:
1.2 Beta
Assignee:
Reporter: Erich Oliphant
Created: Fri, 3 Sep 2004 7:56 AM
Updated: Fri, 3 Sep 2004 7:56 AM
Description:
Some code that worked with an older Sun JAXM RI is not working properly w/ the latest AXIS. Setting the SOAPAction via MimeHeader.addHeader() seems to create 2 copies of the header in the request message.
This code:
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (AXIS-1545) Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Posted by ax...@ws.apache.org.
Message:
The following issue has been closed.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1545
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1545
Summary: Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Axis
Components:
Basic Architecture
Fix Fors:
current (nightly)
Versions:
1.2 Beta
Assignee:
Reporter: Erich Oliphant
Created: Fri, 3 Sep 2004 7:56 AM
Updated: Wed, 8 Sep 2004 8:46 AM
Description:
Some code that worked with an older Sun JAXM RI is not working properly w/ the latest AXIS. Setting the SOAPAction via MimeHeader.addHeader() seems to create 2 copies of the header in the request message.
This code:
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1545) Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Ias
Created: Fri, 3 Sep 2004 10:41 AM
Body:
Could you apply this patch and test your case?
Index: HTTPSender.java
===================================================================
RCS file: /home/cvs/ws-axis/java/src/org/apache/axis/transport/http/HTTPSender.java,v
retrieving revision 1.118
diff -u -r1.118 HTTPSender.java
--- HTTPSender.java 4 Jun 2004 12:05:48 -0000 1.118
+++ HTTPSender.java 3 Sep 2004 17:38:48 -0000
@@ -350,7 +350,9 @@
if (mimeHeaders != null) {
for (Iterator i = mimeHeaders.getAllHeaders(); i.hasNext(); ) {
MimeHeader mimeHeader = (MimeHeader) i.next();
- if (mimeHeader.getName().equals(HTTPConstants.HEADER_CONTENT_TYPE)) {
+ String headerName = mimeHeader.getName();
+ if (headerName.equals(HTTPConstants.HEADER_CONTENT_TYPE)
+ || headerName.equals(HTTPConstants.HEADER_SOAP_ACTION)) {
continue;
}
header2.append(mimeHeader.getName())
Thanks,
Ias
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1545?page=comments#action_52809
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1545
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1545
Summary: Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
Basic Architecture
Versions:
1.2 Beta
Assignee:
Reporter: Erich Oliphant
Created: Fri, 3 Sep 2004 7:56 AM
Updated: Fri, 3 Sep 2004 10:41 AM
Description:
Some code that worked with an older Sun JAXM RI is not working properly w/ the latest AXIS. Setting the SOAPAction via MimeHeader.addHeader() seems to create 2 copies of the header in the request message.
This code:
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1545) Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Erich Oliphant
Created: Fri, 3 Sep 2004 9:06 AM
Body:
Could not figure out how to edit the description after submittal.
The attached .java file generates the following message:
---
POST /TRXServices/TRXSSabre/RSSabre.asmx HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.2beta3
Host: localhost:8999
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: "http://www.trx.com/TRXServices/TRXSSabre/SeatMapGet"
Content-Length: 333
SOAPAction: http://www.trx.com/TRXServices/TRXSSabre/SeatMapGet
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<SeatMapGet xmlns="http://www.trx.com/TRXServices/TRXSSabre/"/>
</soapenv:Body>
</soapenv:Envelope>
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1545?page=comments#action_52807
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1545
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1545
Summary: Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
Basic Architecture
Versions:
1.2 Beta
Assignee:
Reporter: Erich Oliphant
Created: Fri, 3 Sep 2004 7:56 AM
Updated: Fri, 3 Sep 2004 9:06 AM
Description:
Some code that worked with an older Sun JAXM RI is not working properly w/ the latest AXIS. Setting the SOAPAction via MimeHeader.addHeader() seems to create 2 copies of the header in the request message.
This code:
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1545) Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Erich Oliphant
Created: Wed, 8 Sep 2004 8:39 AM
Body:
That seems to have fixed it!
I am patching our local copy. Will this make it into the next beta drop?
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1545?page=comments#action_52964
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1545
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1545
Summary: Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
Basic Architecture
Versions:
1.2 Beta
Assignee:
Reporter: Erich Oliphant
Created: Fri, 3 Sep 2004 7:56 AM
Updated: Wed, 8 Sep 2004 8:39 AM
Description:
Some code that worked with an older Sun JAXM RI is not working properly w/ the latest AXIS. Setting the SOAPAction via MimeHeader.addHeader() seems to create 2 copies of the header in the request message.
This code:
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS-1545) Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Posted by ax...@ws.apache.org.
The following issue has been updated:
Updater: Erich Oliphant (mailto:ericho@vantixweb.com)
Date: Fri, 3 Sep 2004 7:57 AM
Changes:
Attachment changed to AxisSoapActionBug.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/AXIS-1545?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1545
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1545
Summary: Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
Basic Architecture
Versions:
1.2 Beta
Assignee:
Reporter: Erich Oliphant
Created: Fri, 3 Sep 2004 7:56 AM
Updated: Fri, 3 Sep 2004 7:57 AM
Description:
Some code that worked with an older Sun JAXM RI is not working properly w/ the latest AXIS. Setting the SOAPAction via MimeHeader.addHeader() seems to create 2 copies of the header in the request message.
This code:
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1545) Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Ias
Created: Tue, 7 Sep 2004 10:19 AM
Body:
Maybe your source base is not the latest revision, 1.118. Actually the patch is equivalent to changing
if (mimeHeader.getName().equals(HTTPConstants.HEADER_CONTENT_TYPE)) {
to
if (headerName.equals(HTTPConstants.HEADER_CONTENT_TYPE)
|| headerName.equals(HTTPConstants.HEADER_SOAP_ACTION)) {
.
Thanks,
Ias
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1545?page=comments#action_52931
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1545
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1545
Summary: Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
Basic Architecture
Versions:
1.2 Beta
Assignee:
Reporter: Erich Oliphant
Created: Fri, 3 Sep 2004 7:56 AM
Updated: Tue, 7 Sep 2004 10:19 AM
Description:
Some code that worked with an older Sun JAXM RI is not working properly w/ the latest AXIS. Setting the SOAPAction via MimeHeader.addHeader() seems to create 2 copies of the header in the request message.
This code:
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1545) Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Erich Oliphant
Created: Tue, 7 Sep 2004 7:39 AM
Body:
Having difficulty applying the patch, not exactly sure why.
Here's the reject file:
cat ./HTTPSender.java.rej
***************
*** 350,356 ****
if (mimeHeaders != null) {
for (Iterator i = mimeHeaders.getAllHeaders(); i.hasNext(); ) {
MimeHeader mimeHeader = (MimeHeader) i.next();
- if (mimeHeader.getName().equals(HTTPConstants.HEADER_CONTENT_TYPE)) {
continue;
}
header2.append(mimeHeader.getName())
--- 350,358 ----
if (mimeHeaders != null) {
for (Iterator i = mimeHeaders.getAllHeaders(); i.hasNext(); ) {
MimeHeader mimeHeader = (MimeHeader) i.next();
+ String headerName = mimeHeader.getName();
+ if (headerName.equals(HTTPConstants.HEADER_CONTENT_TYPE)
+ || headerName.equals(HTTPConstants.HEADER_SOAP_ACTION)) {
continue;
}
header2.append(mimeHeader.getName())
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1545?page=comments#action_52922
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1545
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1545
Summary: Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
Basic Architecture
Versions:
1.2 Beta
Assignee:
Reporter: Erich Oliphant
Created: Fri, 3 Sep 2004 7:56 AM
Updated: Tue, 7 Sep 2004 7:39 AM
Description:
Some code that worked with an older Sun JAXM RI is not working properly w/ the latest AXIS. Setting the SOAPAction via MimeHeader.addHeader() seems to create 2 copies of the header in the request message.
This code:
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1545) Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Ias
Created: Wed, 8 Sep 2004 8:45 AM
Body:
The patch is applied to CVS. You can expect it from the next Axis 1.2 release.
Thanks,
Ias
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1545?page=comments#action_52965
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1545
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1545
Summary: Adding SOAPAction MimeHeader generates 2 SOAPAction's in the actual message
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
Basic Architecture
Fix Fors:
current (nightly)
Versions:
1.2 Beta
Assignee:
Reporter: Erich Oliphant
Created: Fri, 3 Sep 2004 7:56 AM
Updated: Wed, 8 Sep 2004 8:45 AM
Description:
Some code that worked with an older Sun JAXM RI is not working properly w/ the latest AXIS. Setting the SOAPAction via MimeHeader.addHeader() seems to create 2 copies of the header in the request message.
This code:
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira