cancel
Showing results for 
Search instead for 
Did you mean: 

org.xml.sax.SAXParseException: Premature end of file error in receiver AXIS adapter

former_member206760
Active Contributor
0 Kudos

Hi experts

I am getting a "org.xml.sax.SAXParseException: Premature end of file" error in the receiver  axis adapter.

I think it is because the SOAP 1.2 web services expect content type as "application/soap+xml;charset=UTF-8"

So I used the MessageTransformBean just before the AF_Adapters/axis/AFAdapterBean  to convert the content type from "text/xml"

to  "application/soap+xml;charset=UTF-8"

However when i check in XPI inspector the content type is still "text/xml"

Any direction on this issue will be very helpul

thanks

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi T Shah, 

Am also getting the same error in receiver axis adapter:: "org.xml.sax.SAXParseException: Premature end of file" when am using HTTP Axis adapter .

Note:It is working fine with regular HTTP adapter.

Module Configuration:

Thanks in Advance

Former Member
0 Kudos

Hi T Shah,

If you have resolved it can you share the solution or shall I raise new thread.

Regards,

Mohammed Gouse

former_member206760
Active Contributor
0 Kudos
gagandeep_batra
Active Contributor
0 Kudos


Hi Shah,

Can you let me know why you are using two time Stric2XML

Reagrds

gAGan

former_member206760
Active Contributor
0 Kudos

one is for the request and another for the response..

anyways even i remove the second one it still gives the same error

gagandeep_batra
Active Contributor
0 Kudos

Try:

Transform.Class     com.sap.aii.messaging.adapter.Conversion

Transform.ContentType     text/xml;charset=utf-8

Regards

Gagan

former_member206760
Active Contributor
0 Kudos

PI by default sends text/xml there is no need to use transformbean or that

gagandeep_batra
Active Contributor
0 Kudos

use

Transform.Class com.sap.aii.messaging.adapter.Conversion

rest is yours

stefan_grube
Active Contributor
0 Kudos

You have used httpS. Check if basic authentication is suffient for https.

Remove the flag "Keep XI headers".

The additional modules for MessageTranformBean make no sense. The content type will be set correctly automatically.

former_member206760
Active Contributor
0 Kudos

hi stefan,

Thanks for the reply

Tried removing the tick " keep XI header " and also the message trasnformation bean,

And it is not working.

As far as the https is concerned i think the basic authentication is sufficient as it works with the option

SOAP 1.1 in axis adapter .....only SOAP 1.2 gives issue

Any further help ?

gagandeep_batra
Active Contributor
0 Kudos

Hi Shah,

Can you post screen shot of your Receiver CC

& also try to post data through soapUI if possible;

Regards

Gagan