[jira] Created: (AXIS2-1323) Consume Axis 2 web service in VB.NET

2006-10-07 Thread Ravi (JIRA)
Consume Axis 2 web service in VB.NET


 Key: AXIS2-1323
 URL: http://issues.apache.org/jira/browse/AXIS2-1323
 Project: Apache Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 0.95
 Environment: Win 2003
Reporter: Ravi


Please let me know how to hanle request and response object in vb.net client 
application. i am trying to invoke sample web service from axis2 
(getVersion()). It is asking me to pass request object and returns as response 
object. 

i have used axis getVersion which returns of type string and directly assign 
variable and use it. but in axis2 its not the same.

Please do help me.

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (AXIS-2158) Error attempting to use DIME in Axis client

2005-11-29 Thread ravi (JIRA)
[ 
http://issues.apache.org/jira/browse/AXIS-2158?page=comments#action_12358785 ] 

ravi commented on AXIS-2158:


Brian,
  I did not document it. I guess credit should go to  Rodrigo Ruiz for 
documenting it. 

  I found another problem with this though. 
  When I run my client with a proxy server like squid, it runs into problems. 

  Squid gives the error message - (501)Not Implemented.

  This happens only when I use CommonsHTTPSender and does not happen with 
HTTPSender. Also, if I do not have a proxy server, it works perfectly. 

  Any help of the issue would help immensely.

Thanks a lot
Ravi.
 

 Error attempting to use DIME in Axis client
 ---

  Key: AXIS-2158
  URL: http://issues.apache.org/jira/browse/AXIS-2158
  Project: Apache Axis
 Type: Bug
   Components: SAAJ
 Versions: 1.2.1
  Environment: Axis 1.2.1client running jdk1.4.2_05 and Tomcat 5.0 for server.
 Reporter: Brian Husted


 Sending more than eight DIME chunks from an Axis client to Axis server 
 results in the following error:
 Caused by: java.io.IOException: End of physical stream detected when more 
 DIME chunks expected. 
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream._read(DimeDelimitedInputStream.java:268)
  
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:201)
  
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:445)
  
 at 
 org.apache.axis.attachments.ManagedMemoryDataSource.init(ManagedMemoryDataSource.java:146)
  
 at 
 org.apache.axis.attachments.MultiPartDimeInputStream.readTillFound(MultiPartDimeInputStream.java:163)
  
 ... 46 more 
 at 
 org.apache.axis.encoding.DeserializationContext.getObjectByRef(DeserializationContext.java:619)
  
 at 
 org.apache.axis.encoding.ser.JAFDataHandlerDeserializer.startElement(JAFDataHandlerDeserializer.java:70)
  
 at 
 org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1048)
  
 at 
 org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165) 
 at 
 org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
  
 at 
 org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236) 
 at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384) 
 at 
 org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:148)
  
 at 
 org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323) 
 ... 33 more 

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Commented: (AXIS-2158) Error attempting to use DIME in Axis client

2005-11-29 Thread ravi (JIRA)
[ 
http://issues.apache.org/jira/browse/AXIS-2158?page=comments#action_12358793 ] 

ravi commented on AXIS-2158:


Oleg,
  No, the target server is not using SSL, though we are using the basic http 
authentication.

Thanks again for your help
Ravi.

 Error attempting to use DIME in Axis client
 ---

  Key: AXIS-2158
  URL: http://issues.apache.org/jira/browse/AXIS-2158
  Project: Apache Axis
 Type: Bug
   Components: SAAJ
 Versions: 1.2.1
  Environment: Axis 1.2.1client running jdk1.4.2_05 and Tomcat 5.0 for server.
 Reporter: Brian Husted


 Sending more than eight DIME chunks from an Axis client to Axis server 
 results in the following error:
 Caused by: java.io.IOException: End of physical stream detected when more 
 DIME chunks expected. 
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream._read(DimeDelimitedInputStream.java:268)
  
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:201)
  
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:445)
  
 at 
 org.apache.axis.attachments.ManagedMemoryDataSource.init(ManagedMemoryDataSource.java:146)
  
 at 
 org.apache.axis.attachments.MultiPartDimeInputStream.readTillFound(MultiPartDimeInputStream.java:163)
  
 ... 46 more 
 at 
 org.apache.axis.encoding.DeserializationContext.getObjectByRef(DeserializationContext.java:619)
  
 at 
 org.apache.axis.encoding.ser.JAFDataHandlerDeserializer.startElement(JAFDataHandlerDeserializer.java:70)
  
 at 
 org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1048)
  
 at 
 org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165) 
 at 
 org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
  
 at 
 org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236) 
 at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384) 
 at 
 org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:148)
  
 at 
 org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323) 
 ... 33 more 

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Updated: (AXIS-2158) Error attempting to use DIME in Axis client

2005-11-29 Thread ravi (JIRA)
 [ http://issues.apache.org/jira/browse/AXIS-2158?page=all ]

ravi updated AXIS-2158:
---

Attachment: wirelog.txt

Oleg
  I am attaching the wire log (not sure this is it, but this is the output that 
i got when i enabled it). 

Thanks
Ravi

 Error attempting to use DIME in Axis client
 ---

  Key: AXIS-2158
  URL: http://issues.apache.org/jira/browse/AXIS-2158
  Project: Apache Axis
 Type: Bug
   Components: SAAJ
 Versions: 1.2.1
  Environment: Axis 1.2.1client running jdk1.4.2_05 and Tomcat 5.0 for server.
 Reporter: Brian Husted
  Attachments: wirelog.txt

 Sending more than eight DIME chunks from an Axis client to Axis server 
 results in the following error:
 Caused by: java.io.IOException: End of physical stream detected when more 
 DIME chunks expected. 
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream._read(DimeDelimitedInputStream.java:268)
  
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:201)
  
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:445)
  
 at 
 org.apache.axis.attachments.ManagedMemoryDataSource.init(ManagedMemoryDataSource.java:146)
  
 at 
 org.apache.axis.attachments.MultiPartDimeInputStream.readTillFound(MultiPartDimeInputStream.java:163)
  
 ... 46 more 
 at 
 org.apache.axis.encoding.DeserializationContext.getObjectByRef(DeserializationContext.java:619)
  
 at 
 org.apache.axis.encoding.ser.JAFDataHandlerDeserializer.startElement(JAFDataHandlerDeserializer.java:70)
  
 at 
 org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1048)
  
 at 
 org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165) 
 at 
 org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
  
 at 
 org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236) 
 at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384) 
 at 
 org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:148)
  
 at 
 org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323) 
 ... 33 more 

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Commented: (AXIS-2158) Error attempting to use DIME in Axis client

2005-11-29 Thread ravi (JIRA)
[ 
http://issues.apache.org/jira/browse/AXIS-2158?page=comments#action_12358801 ] 

ravi commented on AXIS-2158:


Oleg
  Thanks for your help. Where do I set my program to use HTTP 1.0? 
  
  I have no control over the proxies, and my application has to work with all 
the proxies. 

Thanks
Ravi.

 Error attempting to use DIME in Axis client
 ---

  Key: AXIS-2158
  URL: http://issues.apache.org/jira/browse/AXIS-2158
  Project: Apache Axis
 Type: Bug
   Components: SAAJ
 Versions: 1.2.1
  Environment: Axis 1.2.1client running jdk1.4.2_05 and Tomcat 5.0 for server.
 Reporter: Brian Husted
  Attachments: wirelog.txt

 Sending more than eight DIME chunks from an Axis client to Axis server 
 results in the following error:
 Caused by: java.io.IOException: End of physical stream detected when more 
 DIME chunks expected. 
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream._read(DimeDelimitedInputStream.java:268)
  
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:201)
  
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:445)
  
 at 
 org.apache.axis.attachments.ManagedMemoryDataSource.init(ManagedMemoryDataSource.java:146)
  
 at 
 org.apache.axis.attachments.MultiPartDimeInputStream.readTillFound(MultiPartDimeInputStream.java:163)
  
 ... 46 more 
 at 
 org.apache.axis.encoding.DeserializationContext.getObjectByRef(DeserializationContext.java:619)
  
 at 
 org.apache.axis.encoding.ser.JAFDataHandlerDeserializer.startElement(JAFDataHandlerDeserializer.java:70)
  
 at 
 org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1048)
  
 at 
 org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165) 
 at 
 org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
  
 at 
 org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236) 
 at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384) 
 at 
 org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:148)
  
 at 
 org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323) 
 ... 33 more 

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Commented: (AXIS-2158) Error attempting to use DIME in Axis client

2005-11-29 Thread ravi (JIRA)
[ 
http://issues.apache.org/jira/browse/AXIS-2158?page=comments#action_12358814 ] 

ravi commented on AXIS-2158:


Oleg
  Thanks a lot for you help. I would have been going around in circles if not 
for you. At least now I know what the problem is. 
  
  Since I am not using HTTPClient directly (rather CommonsHTTPSender ? ), I am 
hoping that Axis will have an easy way of setting the http version.

Thanks again
Ravi.

 Error attempting to use DIME in Axis client
 ---

  Key: AXIS-2158
  URL: http://issues.apache.org/jira/browse/AXIS-2158
  Project: Apache Axis
 Type: Bug
   Components: SAAJ
 Versions: 1.2.1
  Environment: Axis 1.2.1client running jdk1.4.2_05 and Tomcat 5.0 for server.
 Reporter: Brian Husted
  Attachments: wirelog.txt

 Sending more than eight DIME chunks from an Axis client to Axis server 
 results in the following error:
 Caused by: java.io.IOException: End of physical stream detected when more 
 DIME chunks expected. 
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream._read(DimeDelimitedInputStream.java:268)
  
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:201)
  
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:445)
  
 at 
 org.apache.axis.attachments.ManagedMemoryDataSource.init(ManagedMemoryDataSource.java:146)
  
 at 
 org.apache.axis.attachments.MultiPartDimeInputStream.readTillFound(MultiPartDimeInputStream.java:163)
  
 ... 46 more 
 at 
 org.apache.axis.encoding.DeserializationContext.getObjectByRef(DeserializationContext.java:619)
  
 at 
 org.apache.axis.encoding.ser.JAFDataHandlerDeserializer.startElement(JAFDataHandlerDeserializer.java:70)
  
 at 
 org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1048)
  
 at 
 org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165) 
 at 
 org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
  
 at 
 org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236) 
 at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384) 
 at 
 org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:148)
  
 at 
 org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323) 
 ... 33 more 

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Commented: (AXIS-2158) Error attempting to use DIME in Axis client

2005-11-22 Thread ravi (JIRA)
[ 
http://issues.apache.org/jira/browse/AXIS-2158?page=comments#action_12358226 ] 

ravi commented on AXIS-2158:


The solution given in 

http://wiki.apache.org/ws/FrontPage/Axis/AttachmentProblems

solves the problem.

Can this be made the default mode of transport?

Thanks 
Ravi.

 Error attempting to use DIME in Axis client
 ---

  Key: AXIS-2158
  URL: http://issues.apache.org/jira/browse/AXIS-2158
  Project: Apache Axis
 Type: Bug
   Components: SAAJ
 Versions: 1.2.1
  Environment: Axis 1.2.1client running jdk1.4.2_05 and Tomcat 5.0 for server.
 Reporter: Brian Husted


 Sending more than eight DIME chunks from an Axis client to Axis server 
 results in the following error:
 Caused by: java.io.IOException: End of physical stream detected when more 
 DIME chunks expected. 
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream._read(DimeDelimitedInputStream.java:268)
  
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:201)
  
 at 
 org.apache.axis.attachments.DimeDelimitedInputStream.read(DimeDelimitedInputStream.java:445)
  
 at 
 org.apache.axis.attachments.ManagedMemoryDataSource.init(ManagedMemoryDataSource.java:146)
  
 at 
 org.apache.axis.attachments.MultiPartDimeInputStream.readTillFound(MultiPartDimeInputStream.java:163)
  
 ... 46 more 
 at 
 org.apache.axis.encoding.DeserializationContext.getObjectByRef(DeserializationContext.java:619)
  
 at 
 org.apache.axis.encoding.ser.JAFDataHandlerDeserializer.startElement(JAFDataHandlerDeserializer.java:70)
  
 at 
 org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1048)
  
 at 
 org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165) 
 at 
 org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
  
 at 
 org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236) 
 at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384) 
 at 
 org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:148)
  
 at 
 org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323) 
 ... 33 more 

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Commented: (AXIS-2186) AxisFault with DIME attachments greater than 1MB with .Net Web Service

2005-11-22 Thread ravi (JIRA)
[ 
http://issues.apache.org/jira/browse/AXIS-2186?page=comments#action_12358227 ] 

ravi commented on AXIS-2186:


The solution given in

http://wiki.apache.org/ws/FrontPage/Axis/AttachmentProblems

works.

Can this be made the default mode of transport instead of HTTPSender.

Thanks
Ravi.

 AxisFault with DIME attachments greater than 1MB with .Net Web Service
 --

  Key: AXIS-2186
  URL: http://issues.apache.org/jira/browse/AXIS-2186
  Project: Apache Axis
 Type: Bug
   Components: Serialization/Deserialization
  Environment: Axis 1.2.1 (+patch for issue 2084); JRE 1.3.1, JRE 1.5.0; 
 Windows XP, 2K
 Reporter: Stefano Meneghello


 Windows XP (and 2K).
 JRE 1.3.1 and 1.5.0
 When I invoke a .Net Web Service using DIME attachments (greater than 1MB), I 
 get the following Stack Trace:
 AxisFault
  faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
  faultSubcode: 
  faultString: In the record EB5604032C3DDD214F52C4F324868FD0, the number of 
 bytes in the Data field is less than 309079, which is the value indicated in 
 the ContentLength field.
  faultActor: http://192.168.1.13/test/ws.asmx
  faultNode: 
  faultDetail: 
   {http://xml.apache.org/axis/}stackTrace:In the record 
 EB5604032C3DDD214F52C4F324868FD0, the number of bytes in the Data field is 
 less than 309079, which is the value indicated in the ContentLength field.
   at 
 org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
   at 
 org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
   at 
 org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
   at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown 
 Source)
   at 
 org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
   at 
 org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
  Source)
   at 
 org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 
 Source)
   at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
   at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
   at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
   at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
   at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown 
 Source)
   at javax.xml.parsers.SAXParser.parse(Unknown Source)
   at 
 org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
   at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
   at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
   at 
 org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
   at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
   at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
   at org.apache.axis.client.Call.invoke(Call.java:2748)
   at org.apache.axis.client.Call.invoke(Call.java:2424)
   at org.apache.axis.client.Call.invoke(Call.java:2347)
   at org.apache.axis.client.Call.invoke(Call.java:1804)
   at WSSoapStub._import(WSSoapStub.java:443)
   at WebServiceCallerImpl.wsImport(WebServiceCallerImpl.java:111)
   at DominoJavaWSImpl.doImport(DominoJavaWSImpl.java:219)
   at DominoJavaWSImpl.doAction(DominoJavaWSImpl.java:113)
   at WSUtils.processSingleMicroDoc(WSUtils.java:58)
   at WSUtils.processSingleMicroDoc(WSUtils.java:50)
   at WSUtils.processMicroDoc(WSUtils.java:121)
   at JavaAgent.NotesMain(JavaAgent.java:24)
   at lotus.domino.AgentBase.runNotes(Unknown Source)
   at lotus.domino.NotesThread.run(NotesThread.java:215)
 It works for single-chunk requests.
 The stack trace is taken from a Domino application, but I get the same from 
 outside.
 thanks
 stefano

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Commented: (AXIS-2186) AxisFault with DIME attachments greater than 1MB with .Net Web Service

2005-11-21 Thread ravi (JIRA)
[ 
http://issues.apache.org/jira/browse/AXIS-2186?page=comments#action_12358165 ] 

ravi commented on AXIS-2186:


Hello
  http://issues.apache.org/jira/browse/AXIS-2084 says that it is fixed in Axis 
1.3. However, it is not.

  Also it says that it works in Axis 1.2 RC3, but the problem is that the 
signatures have been changed between RC3 and 1.2.1 (which I was using for 
development until I found this problem in my code).

  Now I am stuck with changing my other methods to make it work with RC3.

  I appreciate any help in the matter

Thanks a lot for you help.
Ravi.


 AxisFault with DIME attachments greater than 1MB with .Net Web Service
 --

  Key: AXIS-2186
  URL: http://issues.apache.org/jira/browse/AXIS-2186
  Project: Apache Axis
 Type: Bug
   Components: Serialization/Deserialization
  Environment: Axis 1.2.1 (+patch for issue 2084); JRE 1.3.1, JRE 1.5.0; 
 Windows XP, 2K
 Reporter: Stefano Meneghello


 Windows XP (and 2K).
 JRE 1.3.1 and 1.5.0
 When I invoke a .Net Web Service using DIME attachments (greater than 1MB), I 
 get the following Stack Trace:
 AxisFault
  faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
  faultSubcode: 
  faultString: In the record EB5604032C3DDD214F52C4F324868FD0, the number of 
 bytes in the Data field is less than 309079, which is the value indicated in 
 the ContentLength field.
  faultActor: http://192.168.1.13/test/ws.asmx
  faultNode: 
  faultDetail: 
   {http://xml.apache.org/axis/}stackTrace:In the record 
 EB5604032C3DDD214F52C4F324868FD0, the number of bytes in the Data field is 
 less than 309079, which is the value indicated in the ContentLength field.
   at 
 org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
   at 
 org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
   at 
 org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
   at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown 
 Source)
   at 
 org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
   at 
 org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
  Source)
   at 
 org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 
 Source)
   at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
   at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
   at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
   at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
   at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown 
 Source)
   at javax.xml.parsers.SAXParser.parse(Unknown Source)
   at 
 org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
   at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
   at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
   at 
 org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
   at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
   at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
   at org.apache.axis.client.Call.invoke(Call.java:2748)
   at org.apache.axis.client.Call.invoke(Call.java:2424)
   at org.apache.axis.client.Call.invoke(Call.java:2347)
   at org.apache.axis.client.Call.invoke(Call.java:1804)
   at WSSoapStub._import(WSSoapStub.java:443)
   at WebServiceCallerImpl.wsImport(WebServiceCallerImpl.java:111)
   at DominoJavaWSImpl.doImport(DominoJavaWSImpl.java:219)
   at DominoJavaWSImpl.doAction(DominoJavaWSImpl.java:113)
   at WSUtils.processSingleMicroDoc(WSUtils.java:58)
   at WSUtils.processSingleMicroDoc(WSUtils.java:50)
   at WSUtils.processMicroDoc(WSUtils.java:121)
   at JavaAgent.NotesMain(JavaAgent.java:24)
   at lotus.domino.AgentBase.runNotes(Unknown Source)
   at lotus.domino.NotesThread.run(NotesThread.java:215)
 It works for single-chunk requests.
 The stack trace is taken from a Domino application, but I get the same from 
 outside.
 thanks
 stefano

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira