Hi Keith, Thanks for your response. What I observe is that the XML opens up fine on IE. I have checked wellformedness after extracting the XML out into a file. The other point I forgot to add is that the same XML works fine when sending out a HTTP request. If I use HTTPS, I get this error. I am attaching the XML I am using for my testing here for your reference
Just to give an idea of the environment that we are testing in, the
webservice sits on a tomcat
behind apache http server both of which are secure.
The webservice client sits on a tomcat (this can be secure or non-secure,
in either case same error ..) in front of the apache and sends out HTTPS
(secure ) request to Apache which then forwards the request to the tomcat.
Please help.
(See attached file: Copy of check_1.xml)
Vidhya Mahadevan
Technical Consultant -
ITEC/CRS/ARC
Societe Generale Global
Solution Center Pvt. Ltd.
6th Floor, "Inventor"
Building, ITPL, Whitefield
Road,
Bangalore 560 066, India
Tel.: 91 80 28095 279
Mob.: 91 98453 28950
[EMAIL PROTECTED]
www.socgensolutions.com
|------------------------------
| "keith chapman"
| <[EMAIL PROTECTED]
| ail.com>
|
| 11/25/2008 07:33
| PM
|
|
| Please respond to
| [EMAIL PROTECTED]
| he.org
|
|
To
[email protected]
cc
Subject
Re: Problem with large XML
request using AXIS2 AXIOM
[C1]
>From the exception it looks like your XML was malformed (not having proper
closing tags). There is no such an upper limit on the number of elements an
AXIOM tree can have.
Thanks,
Keith.
On Tue, Nov 25, 2008 at 4:09 PM, Vidhya MAHADEVAN <
[EMAIL PROTECTED]> wrote:
Hello,
We are using AXIS2-1.4. We are building a request message with AXIOM.
This message is quite large. It has about 280 elements in the request
XML.
We are bulding an OMElement with
this XML.
When we call the web service from the client, it fails at the client end
with this message.
" com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 't'
(code 116) in prolog; expected '<'"
However, if we reduce the number of elements to about 150, it works.
Is there an upper limit on what the maximum number of elements an AXIOM
tree can have ?
If there is, then is there a workaround for this problem ?
I have searched many places for similar issues. I could not find any
solutions and therefore am raising it here.
Appreciate any inputs from the group.
Here is the client code :
OMElement requestOMElement = buildOMElementFromXML();
//call web service
Options options = new Options();
options.setTo(targetEPR);
options.setProperty(org.apache.axis2.transport.http.HTTPConstants.CHUNKED
,Boolean.FALSE);
//options.setTransportInProtocol(Constants.TRANSPORT_HTTPS);
options.setAction("urn:saveBulkUpload");
OMElement responseElement = null;
try {
ServiceClient sender = new ServiceClient();
sender.setOptions(options);
sender.sendReceive(requestOMElement);
} catch (AxisFault e) {
sLogger.info(e);
}
private static OMElement buildOMElementFromXML() {
//String filePath = "c:/check_3_trans.xml";
String filePath = "C:/Copy of check_1.xml";
OMElement documentElement = null;
try {
documentElement = new
StAXOMBuilder(filePath).getDocumentElement();
} catch (FileNotFoundException e) {
// TODO Auto-generated catch block
e.printStackTrace();
} catch (XMLStreamException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
return documentElement;
}
Vidhya Mahadevan
Technical Consultant -
ITEC/CRS/ARC
Societe Generale Global
Solution Center Pvt. Ltd.
6th Floor, "Inventor"
Building, ITPL, Whitefield
Road,
Bangalore 560 066, India
Tel.: 91 80 28095 279
Mob.: 91 98453 28950
[EMAIL PROTECTED]
www.socgensolutions.com
*************************************************************************
This message and any attachments (the "message") are confidential,
intended solely for the addressee(s), and may contain legally privileged
information.
Any unauthorised use or dissemination is prohibited. E-mails are
susceptible to alteration.
Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall
be liable for the message if altered, changed or
falsified.
************
Ce message et toutes les pieces jointes (ci-apres le "message") sont
confidentiels et susceptibles de contenir des informations couvertes
par le secret professionnel.
Ce message est etabli a l'intention exclusive de ses destinataires. Toute
utilisation ou diffusion non autorisee est interdite.
Tout message electronique est susceptible d'alteration.
La SOCIETE GENERALE et ses filiales declinent toute responsabilite au
titre de ce message s'il a ete altere, deforme ou falsifie.
*************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Copy of check_1.xml
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
