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/07/21 01:48:39 UTC
[jira] Created: (AXIS-1468) (SAAJ) Call.invoke(SOAPEnvelope) should allow for one-way invocation
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1468
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1468
Summary: (SAAJ) Call.invoke(SOAPEnvelope) should allow for one-way invocation
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
Basic Architecture
Versions:
1.1
Assignee:
Reporter: Quynh Dang
Created: Tue, 20 Jul 2004 4:47 PM
Updated: Tue, 20 Jul 2004 4:47 PM
Environment: Windows
Description:
When using Call.invoke(SOAPEnvelope) to call an endpoint with one-way operation (response has content-length=0), the method throws a "Premature end of file" exception. I would like to have either another "invokeOneWay(SOAPEnvelope) to skip the response or another flag to the current invoke method. This is similar to Call.invokeOneWay(Object[])
---------------------------------------------------------------------
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-1468) (SAAJ) Call.invoke(SOAPEnvelope) should allow for one-way invocation
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Jayachandra Sekhara Rao Sunkara
Created: Mon, 18 Oct 2004 8:04 AM
Body:
The exception name hints me that the SOAPEnvelope creation (prior to invoke method call) hasn't been complete (for ex. matching close tags not being appended etc.). This is just a guess, though. We can look into the code in greater detail and troubleshoot the issue, if you post it.
Thanks,
Jayachandra
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1468?page=comments#action_54308
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1468
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1468
Summary: (SAAJ) Call.invoke(SOAPEnvelope) should allow for one-way invocation
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
SAAJ
Versions:
1.1
Assignee:
Reporter: Quynh Dang
Created: Tue, 20 Jul 2004 4:47 PM
Updated: Mon, 18 Oct 2004 8:04 AM
Environment: Windows
Description:
When using Call.invoke(SOAPEnvelope) to call an endpoint with one-way operation (response has content-length=0), the method throws a "Premature end of file" exception. I would like to have either another "invokeOneWay(SOAPEnvelope) to skip the response or another flag to the current invoke method. This is similar to Call.invokeOneWay(Object[])
---------------------------------------------------------------------
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-1468) (SAAJ) Call.invoke(SOAPEnvelope) should allow for one-way invocation
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Quynh Dang
Created: Mon, 18 Oct 2004 8:11 AM
Body:
Here is the client code that I have cleaned up a bit for clarity
that was used to call the Biztalk service. Note that I have observed
that the Biztalk web service received the request OK, processed it, but not returning any contents.
The msgbuf has well-formed <SOAPEnvelope> element.
It is in the parsing of the response (which has no contents)
that throws the exception.
public void invokeSOAPViaSAAJ(StringBuffer msgBuf,
String soapAction,
String soapAddress)
throws Exception
{
SOAPConnectionFactory scFactory = SOAPConnectionFactory.newInstance();
SOAPConnection connection = scFactory.createConnection();
MessageFactory messageFactory = MessageFactory.newInstance();
SOAPMessage message = messageFactory.createMessage(new MimeHeaders(),
new ByteArrayInputStream(msgBuf.toString().getBytes("UTF-8")));
message.getMimeHeaders().addHeader("SOAPAction", soapAction);
SOAPMessage response = connection.call(message, soapAddress);
SOAPBody responseBody = response.getSOAPPart().getEnvelope().getBody();
if (responseBody.hasFault())
{
SOAPFault soapFault = responseBody.getFault();
....
}
else
{
....
}
}
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1468?page=comments#action_54309
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1468
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1468
Summary: (SAAJ) Call.invoke(SOAPEnvelope) should allow for one-way invocation
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
SAAJ
Versions:
1.1
Assignee:
Reporter: Quynh Dang
Created: Tue, 20 Jul 2004 4:47 PM
Updated: Mon, 18 Oct 2004 8:11 AM
Environment: Windows
Description:
When using Call.invoke(SOAPEnvelope) to call an endpoint with one-way operation (response has content-length=0), the method throws a "Premature end of file" exception. I would like to have either another "invokeOneWay(SOAPEnvelope) to skip the response or another flag to the current invoke method. This is similar to Call.invokeOneWay(Object[])
---------------------------------------------------------------------
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-1468) (SAAJ) Call.invoke(SOAPEnvelope) should allow for one-way invocation
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Quynh Dang
Created: Mon, 18 Oct 2004 7:51 AM
Body:
Hi Jayachandra,
I'm referring to calling a web service that does not return any contents.
So the HTTP response was 200 with Content-Length=0.
For example, a Biztalk web service that has no response (one-way method)
responded with 200 and 0 content-length.
When using Axis to call that service via the Call.invoke(SOAPEnvelope) method,
I got the exception of "Premature end of file."
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1468?page=comments#action_54305
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1468
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1468
Summary: (SAAJ) Call.invoke(SOAPEnvelope) should allow for one-way invocation
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
SAAJ
Versions:
1.1
Assignee:
Reporter: Quynh Dang
Created: Tue, 20 Jul 2004 4:47 PM
Updated: Mon, 18 Oct 2004 7:51 AM
Environment: Windows
Description:
When using Call.invoke(SOAPEnvelope) to call an endpoint with one-way operation (response has content-length=0), the method throws a "Premature end of file" exception. I would like to have either another "invokeOneWay(SOAPEnvelope) to skip the response or another flag to the current invoke method. This is similar to Call.invokeOneWay(Object[])
---------------------------------------------------------------------
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-1468) (SAAJ) Call.invoke(SOAPEnvelope) should allow for one-way invocation
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Jayachandra Sekhara Rao Sunkara
Created: Mon, 18 Oct 2004 2:55 AM
Body:
Hi Quynh Dang,
could you be more elaborate on this issue. There are two levels of responses here. (i) the response returned by the web service's method, wrapped as a SOAPEnvelope by Axis on server side. (ii)what the web server lets out on the wire (i.e HTTP Response).
The later has, of course, the former as part (content) of it. This HTTP Response, since, will be handled by a web-server and is beyond what we can manipulate from being returned (convention says for every (and only) HTTP Request there would be a HTTP Response).
And also the error you were quoting 'method throws a Premature end of file', appears like an exception and why should exceptions be skipped. I have some lapses in understanding the exact problem. Could you give a better picture.
Thanks,
Jayachandra
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1468?page=comments#action_54300
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1468
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1468
Summary: (SAAJ) Call.invoke(SOAPEnvelope) should allow for one-way invocation
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
SAAJ
Versions:
1.1
Assignee:
Reporter: Quynh Dang
Created: Tue, 20 Jul 2004 4:47 PM
Updated: Mon, 18 Oct 2004 2:55 AM
Environment: Windows
Description:
When using Call.invoke(SOAPEnvelope) to call an endpoint with one-way operation (response has content-length=0), the method throws a "Premature end of file" exception. I would like to have either another "invokeOneWay(SOAPEnvelope) to skip the response or another flag to the current invoke method. This is similar to Call.invokeOneWay(Object[])
---------------------------------------------------------------------
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-1468) (SAAJ) Call.invoke(SOAPEnvelope) should allow for one-way invocation
Posted by ax...@ws.apache.org.
The following issue has been updated:
Updater: Davanum Srinivas (mailto:davanum@gmail.com)
Date: Fri, 15 Oct 2004 11:02 AM
Changes:
Component changed to SAAJ
Component changed from Basic Architecture
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/AXIS-1468?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1468
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1468
Summary: (SAAJ) Call.invoke(SOAPEnvelope) should allow for one-way invocation
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
SAAJ
Versions:
1.1
Assignee:
Reporter: Quynh Dang
Created: Tue, 20 Jul 2004 4:47 PM
Updated: Fri, 15 Oct 2004 11:02 AM
Environment: Windows
Description:
When using Call.invoke(SOAPEnvelope) to call an endpoint with one-way operation (response has content-length=0), the method throws a "Premature end of file" exception. I would like to have either another "invokeOneWay(SOAPEnvelope) to skip the response or another flag to the current invoke method. This is similar to Call.invokeOneWay(Object[])
---------------------------------------------------------------------
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-1468) (SAAJ) Call.invoke(SOAPEnvelope) should allow for one-way invocation
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Jayachandra Sekhara Rao Sunkara
Created: Mon, 18 Oct 2004 7:58 AM
Body:
Hi Quynh Dang,
would you like to share some client side code that you might have? This would only expedite the process of replicating the buggy behaviour on our end.
Thanks
Jayachandra
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1468?page=comments#action_54306
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1468
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1468
Summary: (SAAJ) Call.invoke(SOAPEnvelope) should allow for one-way invocation
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
SAAJ
Versions:
1.1
Assignee:
Reporter: Quynh Dang
Created: Tue, 20 Jul 2004 4:47 PM
Updated: Mon, 18 Oct 2004 7:58 AM
Environment: Windows
Description:
When using Call.invoke(SOAPEnvelope) to call an endpoint with one-way operation (response has content-length=0), the method throws a "Premature end of file" exception. I would like to have either another "invokeOneWay(SOAPEnvelope) to skip the response or another flag to the current invoke method. This is similar to Call.invokeOneWay(Object[])
---------------------------------------------------------------------
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