SOAP AXIS jars issue

Hi,
We have a client wsdl , and for communication with webservice as per client have to use AXIS1.4.
So imported all the jars into the project EJBmodule related to SOAP, but still the jars are not recognized while building the application.
Need a quick help on this.
Thanks
Srivastsa
+91-9885304877

HI ,
Issue resolved: /people/raphael.vogel/blog/2008/05/05/how-to-use-external-libraries-in-the-sap-component-model-part-ii
Thanks
Srivastsa

Similar Messages

PI 7.11 Receiver SOAP (Axis) Adapter with MTOM (Attachments)

Hello,
Iu2019m trying to configure the Receiver SOAP (Axis) adapter for sending SOAP attachments via MTOM to a third-party webservice, but I'm not getting that PI transform the binary encode64 data in an payload element into a MTOM attachment (xop:include).
The configuration looks like this:
Transport Protocol: HTTP (Axis)
SOAP Version: 1.2
Encapsulation Format: MTOM
Keep Attchments: enabled
Payload Extraction: SOAP Body Child
First of all, could you confirm if this is supported?
Or Axis only supports MTOM for the transport protocol 'File (Axis)' like it seems refered in [Configuring the Receiver Axis SOAP Adapter|http://help.sap.com/saphelp_nwpi711/helpdata/en/45/a3c48c87cd0039e10000000a11466f/frameset.htm]
Can you please provide me some guidance here?
Thanks in advance!
Kind Regards,
Alexandre

Hello,
I am facing the exact same issue.
I can't seem to set the cookie in the http header after following the guide.
Cookie: WSL-credential=MyOwnCookie
I managed to set the SOAPAction though.
Anyone has any ideas?

Problem with Dynamic Configuration in SOAP-AXIS adapter..!!!

Hi ,
Idoc> XI>SOAP-AXIS
I am doing a scenario where I need to pass the URL dynamically in SOAP-AXIS adapter by taking the SNDPRN of Idoc.
If SNDPRN = 100 , message has to go to http://10.190.25.16:8210/file/receiver
   SNDPRN = 200 , message has to go to http://20.180.26.16:8210/file/receiver
It is working correctly when I tried for single receiver. When I' tried to use DynamicConfiguration, it is coming in SOAP document but it is not working and not passing to correct channel. According to this note 1039369, I mentioned the following modules.
AF_Adapters/axis/AFAdapterBean --->                 afreq
AF_Adapters/axis/HandlerBean      --->                  xireq
AF_Adapters/axis/HandlerBean      --->                  dc
AF_Adapters/axis/HandlerBean       --->                 remover
AF_Adapters/axis/HandlerBean       --->                 trp
AF_Adapters/axis/HandlerBean        --->                xires
AF_Adapters/axis/AFAdapterBean    --->               afres
xireq -> handler.type-> java:com.sap.aii.axis.xi.XI30OutboundHandler
dc    -> handler.type-> javasap.aii.axis.xi.XI30DynamicConfigurationHandler
dc   --->   key.1 --->      write http://sap.com/xi/XI/System/SOAP TServerLocation
dc    --->          location.1 --->         context
dc     --->         value.1      --->        transport.url
remover    ---> handler.type    --->   java:com.sap.aii.axis.soap.HeaderRemovalHandler
remover     ---> namespace    --->      http://sap.com/xi/XI/Message/30
trp         --->     handler.type   --->    java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
trp           ---> module.pivot --->     true
xires     --->    handler.type   --->    java:com.sap.aii.axis.xi.XI30OutboundHandler
and I am getting the below error in SOAP-AXIS channel
Error Axis:    error in invocation: java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Error MP:     Exception caught with cause java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Error           Exception caught by adapter framework: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage: java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Kindly let me know if anyone has any idea what might be wrong?
Thanks
Deepthi

I have a similar problem. I also like to add some header fields to my message und that's way I'm trying to use the AXIS adapter. (Axis adapter FAQ question 30) Unfortunately I'm getting exactly the same error message:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.IllegalArgumentException: object type invalid: class com.sap.aii.adapter.xi.ms.XIMessage
Deepthi, you wrote that you have missed one jar file. Can you remember which file it was?

Missing soap action in the soap axis receiver adapter ?

Hi Guys,
I could not find the soap action field in the soap receiver adapter and i followed the OSS note
Note 1054986 - SOAP (Axis) receiver adapter's SOAPAction field missing
Please apply the following patch and use the handler parameter defaultSOAPAction for the XI30OutboundHandler handler in the request chain. This handler parameter can be configured as a module parameter for the HandlerBean module associated with this handler. It is noted that this module parameter takes precedence over the channel parameter for SOAPAction if this field is available.
For SP12
XI ADAPTER FRAMEWORK CORE 7.0
Support Package 12, Patch Level 1 (SAPXIAFC12P_1.SCA)
we are on SP15 so i think the option should be available ?
Do i need to add this parameter in the Module Configuration ?
Moduel Key : ?
Parameter Name: handler.type ---> is this right
Parameter Value ---> ?
we need to validate the user id and pw on IIS for NTLM authentication. Any help regarding developong the handlers would be great
any help would be appreciated.
Thanks,
Srini

Srinivas,
You are on the right path...........yes that is the right note for this issue.
The problem is this is not a general fix that comes with all service packs as the axis adapter is not used a lot, that being said.if you dont see it with sp15..i would safely go apply this fix and see if it works..else you might have to open an oss note for the same...
Hope that helps..
Regards
Ravi Raman
P.S: On my home system..i did apply the fix and i was on a much higher sp level ..i saw some errors..in the logs but nothing a restart couldent fix..

How to install SOAP Axis adapter and where is it available ??

Hi,
I heard that SOAP Axis adapter was not initially available for PI 7.0 and was introduced in some later support pack.When I checked the below url I found that some of the components are missing.
http://xi-dev.intranet.com:50000/XIAxisAdapter/MessageServlet
Can anyone please suggest how I can get that pack and where it will be available?
How to install it?
Thanks
Deepthi.

Hi Sunil,
Dont mind...one final question, they mentioned in the README file as below..
// Open the SDA archive using some unzip tool and replace the following empty
jar files with the those inclued in Axis 1.4 src package
axis.jar
commons-discovery-0.2.jar
commons-logging-1.0.4.jar
commons-net-1.0.0-dev.jar
wsdl4j-1.5.1.jar
When i checked in the Axis folder, I found so many files.
Do I need to just add this Axis zip file into aii_af_axisprovider.sda Archive file.?
If possible, It would be very helpful if you send the aii_af_axisprovider.sda file which you have deployed into your system?
Thanks
Deepthi

SOAP (Axis) Adapter

Hello XI SDNers,
I want to use SOAP (Axis) Adapter for my Webservice Scenario.
According to the SAP Note 1028961, I deployed the "aii_af_axisprovider.sda" file with corresponding ".jar" files from Apache AXIS 1.4 and the deployement was successful.
But now, If I want to use this SOAP (Axis) Adapter, I am unable to see this adapter in my list, for ex., If I create a new "Communication channel" in Configuration and want to select the new SOAP (Axis) Adapter, I couldn't see this in my list.
Am I still missing something?
-Satish.

dear ..
My system is PI7.0 sp15.
With "http://host:port/XIAxisAdapter/MessageServlet" checking , everything corrected.
All jars from axis-bin-1_4.zip and axis-src-1_4.zip .
under " aii_af_axisprovider.sda\META-INF " has a " primary-library-sda-dd.xml " , content :
<?xml version="1.0" encoding="UTF-8"?>
<SDA>
<SoftwareType>primary-library</SoftwareType>
<engine-deployment-descriptor version="2.0" />
</SDA>
I don't know, why didn't list...

SOAP Axis receiver: host parameter is null

Hello,
we are on a PI 7.11 (SP06) system & we are trying to setup a scenario SOAP - SOAP (Axis) where we initiate a third party webservice. To connect to this service we are obliged to go through our proxy, which we defined in our JVM parameters:
http.nonProxyHosts: [*.ont.local|*.val.local|*.mon.local]
http.proxyHost: [proxypac.mon.local]
http.proxyPort: [8080]
http.proxySet: true
When we execute our scenario via soapUI we get following error:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException:
java.lang.IllegalArgumentException: host parameter is null
We already tried with http://proxypac.mon.local as parameter as well but still we get this error.
Furthermore we are able to make a connection to the service via a SM59 connection.
Axis details:
Adapter Common Library Version: 1.7.1106.20110202095400.0000, NW711_06_REL
Adapter Application Version: 1.7.1106.20110202095400.0000, NW711_06_REL
Axis Version: Apache Axis version: 1.4 Built on Apr 22, 2006 (06:55:48 PDT)
Many thanks in advance for your help,
Frédéric.

Hello Mark,
we get this last error when connecting with SOAP receiver instead of Axis receiver.
We are sending different headers (wsa & wsse) in our soapUI request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:klip="http://ws.agiv.be/klipws" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header>
<wsa:Action xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://ws.agiv.be/klipws/ListKLB</wsa:Action>
<wsa:MessageID>urn:uuid:2a46571e-d5a7-4b33-a4a1-a174330cd36c</wsa:MessageID>
<wsa:ReplyTo> <wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address></wsa:ReplyTo>
<wsa:To>http://wsklip.beta.agiv.be/**********.asmx</wsa:To>
<wsse:Security soapenv:mustUnderstand="1" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:klip="http://ws.agiv.be/klipws" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
<wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsu:Created>2011-09-27T10:00:31Z</wsu:Created>
<wsu:Expires>2011-09-30T18:01:31Z</wsu:Expires>
</wsu:Timestamp>
<wsse:UsernameToken>
<wsse:Username>*********</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">***************************************wsse:Password>
<wsse:Nonce>****************************************</wsse:Nonce>
<wsu:Created xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">2011-09-12T14:01:31Z</wsu:Created>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>
<soapenv:Body> <klip:ListKLB xmlns="http://ws.agiv.be/klipws"/>
</soapenv:Body>
</soapenv:Envelope>
For the Axis receiver it looks like one of the handlers can't get the value of our host parameter.
Any help or tips would be really appreciated!
Regards,
Frédéric.

Can I use axis.jar in my custom component

Can I use axis.jar in my custom component.
Is there any license need to user this jar ??
Thanks

In our UCM setup axis has been implemented in a custom component to consume webservices. As Axis falls under the Apache license you can freely import it in your custom java classes.

How to XI error message will mapped to the SOAP faul message-SOAP(Axis)

Hi,
Receiver end I am using SOAP (Axis) adapter and I am getting the system error and I am not getting the payload in SXMB_MONI.
What ever the error message how do MAP as a SOAP Fault message in SXMB_MONI.
I found the Solution from OSS note 1039369 but did not explain where to set what parameter and what modules...
SOAP Fault code
If parameter Category is XIAdaptger, Area SOAP, Code FAULT
In this case, parameters P1 and P2 may be set to the fault namespace and fault name. If these parameters are set, the SOAP fault code is set to namespace P1 and name P2. Otherwise, it is set as in other cases.
For all other cases
In this case, the SOAP fault code is set to namespace "http://sap.com/xi/XI/Message/30" and name category.area.code, where category, area, code represent the XI error category, area, and code values, respectively.
SOAP detail
If parameter ApplicationFault is set
The SOAP detail child is set to the XI application payload. If, however, the payload extraction mode is set to Envelope, the application payload is taken as the SOAP envelope and the SOAP detail content is set to its body content. Similarly, if the extraction mode is set to Body, the application payload is taken as the SOAP body and the SOAP detail content is set to its content.
Otherwise
No SOAP detail content is set in this case.
Examples
XI error element
<sap:Error ...>
<sap:Category>XIAdapterFramework</sap:Category>
<sap:Code area="MESSAGE">GENERAL</sap:Code>
<sap:AdditionalText>Failed to determine a receiver agreement for the given message.</sap:AdditionalText>
</sap:Error>
SOAP fault element
<soapenv:Fault>
<faultcode xmlns:ns1="http://sap.com/xi/XI/Message/30">ns1:XIAdapterFramework.MESSAGE.GENERAL</faultcode>
<faultstring>Failed to determine a receiver agreement for the given message.</faultstring>
<detail/>
</soapenv:Fault>
Help appriciated
Regards,
Venu.
Edited by: Venugopalarao Immadisetty on Sep 24, 2009 3:39 PM

Using Receiver SOAP Axis adapter and I am getting the below exception
XI error element
<sap:Error ...>
<sap:Category>XIAdapterFramework</sap:Category>
<sap:Code area="MESSAGE">GENERAL</sap:Code>
<sap:AdditionalText>Failed to determine a receiver agreement for the given message.</sap:AdditionalText>
</sap:Error>
and above exception how do I convert as a SOAP Fault message..
SOAP fault element
<soapenv:Fault>
<faultcode xmlns:ns1="http://sap.com/xi/XI/Message/30">ns1:XIAdapterFramework.MESSAGE.GENERAL</faultcode>
<faultstring>Failed to determine a receiver agreement for the given message.</faultstring>
<detail/>
</soapenv:Fault>
Any idea what modules need to add in Receiver SOAP Axis adapter.

Error while passing URL Dynamically in SOAP AXIS adapter..!!

Hi ,
Idoc> XI>SOAP-AXIS
I am doing a scenario where I need to pass the URL dynamically in SOAP-AXIS adapter by taking the RCVPRN of Idoc.
If
RCVPRN = 100 , message has to go to http://10.190.25.16:8210/file/receiver
RCVPRN = 200 , message has to go to http://10.190.25.16:8210/file/receiver2
RCVPRN = 300 , message has to go to http://10.190.25.16:8210/file/receiver3
I used the below UDF and it is working correctly and generating the URL dynamically .
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey keyHeader1 = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/SOAP", "TServerLocation");
conf.put(keyHeader1, a);
return "";
The value is coming in SOAP document as expected like below.
<sap:DynamicConfiguration xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:Record namespace="http://sap.com/xi/XI/System/SOAP" name="TServerLocation">http://10.190.25.16:8210/file/receiver3</sap:Record>
</sap:DynamicConfiguration>
I used the below Configuration modules in receiver SOAP-AXIS adapter as suggested in Note 1028961.
AF_Adapters/axis/AFAdapterBean ---> afreq
AF_Adapters/axis/HandlerBean ---> xireq
AF_Adapters/axis/HandlerBean ---> dc
AF_Adapters/axis/HandlerBean ---> remover
AF_Adapters/axis/HandlerBean ---> trp
AF_Adapters/axis/HandlerBean ---> xires
AF_Adapters/axis/AFAdapterBean ---> afres
xireq -> handler.type-> java:com.sap.aii.axis.xi.XI30OutboundHandler
dc -> handler.type-> javasap.aii.axis.xi.XI30DynamicConfigurationHandler
dc ---> key.1 ---> write http://sap.com/xi/XI/System/SOAP TServerLocation
dc ---> location.1 ---> context
dc ---> value.1 ---> transport.url
remover ---> handler.type ---> java:com.sap.aii.axis.soap.HeaderRemovalHandler
remover ---> namespace ---> http://sap.com/xi/XI/Message/30
trp ---> handler.type ---> java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
trp ---> module.pivot ---> true
xires ---> handler.type ---> java:com.sap.aii.axis.xi.XI30OutboundHandler
and I am getting the below error in SOAP-AXIS channel at the point java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender.
2009-03-02 15:23:44 Success Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
2009-03-02 15:23:45 Error Axis: error in invocation: (500)internal server error
2009-03-02 15:23:45 Error MP: Exception caught with cause (500)internal server error
2009-03-02 15:23:45 Error Exception caught by adapter framework: (500)internal server error
2009-03-02 15:23:46 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: (500)internal server error: (500)internal server error.
2009-03-02 15:23:46 Error The message status set to NDLV.
Kindly let me know if anyone has any idea what might be wrong?
Note : The given URL is correct one because I cross checked by passing them normally by giving directly in adapter and they are all working and the message is going to receiver.
Thanks
Deepthi

Hi Stefan,
>> dc -> handler.type-> javasap.aii.axis.xi.XI30DynamicConfigurationHandler
>> dc ---> key.1 ---> write http://sap.com/xi/XI/System/SOAP TServerLocation
>> dc ---> location.1 ---> context
>> dc ---> value.1 ---> transport.url
>> Try read instead of write
When I tried with this, I am getting the below error "Connection refused ".
Success Axis: entering HandlerBean
Success Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
Error Axis: error in invocation: java.net.ConnectException: Connection refused
Error MP: Exception caught with cause java.net.ConnectException: Connection refused
Error Exception caught by adapter framework: ; nested exception is: java.net.ConnectException: Connection refused
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: ; nested exception is: java.net.ConnectException: Connection refused: java.net.ConnectException: Connection refused.
Success The message status set to WAIT.
It is going successfully when I tried sending directly. Looks like Dynamic Configuration is not working for SOAP-AXIS.
Any Suggestion?
Thanks
Deepthi.

Problem accessing Application Ejb Jar files from Apache Axis jars

I have deployed an EAR application, with a structure as shown below,
MyApp.ear
|____ MyApp_Ejb.jar
|____ axis.war
|_____ WEB-INF
|_____ lib (This contains all axis specific jars)
The application deploys just fine. But when i goto happyaxis.jsp and try to view all the web services that have been deployed. I get an exception "No provider type matches QName '{http://xml.apache.org/axis/wsdd/providers/java}SDL".
Here SDL is a custom provider that i have written and all the required files for the provider are available in MyApp_Ejb.jar.
I do not get as to why the axis.jar is not able to find classes in MyApp_Ejb.ear, when both these are in the same ear.
Now i know i can add a utility jar to a war files classpath by adding a classpath line in the War file MANIFEST.MF. But since MyApp_Ejb.jar is defined as a Web Module this solution too doesnt help.
Separating the provider related files from MyApp_Ejb.jar is not possible since there is too much dependance of other files within that jar.
So i am looking for a solution where in i can continue to have MyApp_Ejb.jar as my ejb module as well as the axis related jars can find the required classes within MyApp_Ejb.jar. some way of sharing the ejb jar across to axis jars.
Thanks in advance.
Vicky

I have deployed an EAR application, with a structure as shown below,
MyApp.ear
|____ MyApp_Ejb.jar
|____ axis.war
|_____ WEB-INF
|_____ lib (This contains all axis specific jars)
The application deploys just fine. But when i goto happyaxis.jsp and try to view all the web services that have been deployed. I get an exception "No provider type matches QName '{http://xml.apache.org/axis/wsdd/providers/java}SDL".
Here SDL is a custom provider that i have written and all the required files for the provider are available in MyApp_Ejb.jar.
I do not get as to why the axis.jar is not able to find classes in MyApp_Ejb.ear, when both these are in the same ear.
Now i know i can add a utility jar to a war files classpath by adding a classpath line in the War file MANIFEST.MF. But since MyApp_Ejb.jar is defined as a Web Module this solution too doesnt help.
Separating the provider related files from MyApp_Ejb.jar is not possible since there is too much dependance of other files within that jar.
So i am looking for a solution where in i can continue to have MyApp_Ejb.jar as my ejb module as well as the axis related jars can find the required classes within MyApp_Ejb.jar. some way of sharing the ejb jar across to axis jars.
Thanks in advance.
Vicky

Sender Soap Axis error in PI 7.31

Hi Experts,
We are using PI7.31
We got a requirement to extract XML from a exchange rate URL on daily basis and send it to ECC from PI.
I followed the below link to configure the sender SOAP Axis channel.
http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/01/05/michals-pi-tips-exchange-rates-from-an-xml-file-on-a-web-page--rest-axis
Required class files for Axis are installed in the system.
The channel is showing error as
Channel Status : Administrator error
Log: Adapter has not provided any status information about the channel
faile to initilize: com.sap.aii.af.service.cpa.CPAObjectNotfoundException: Couldnt retrieve binding for the given channel id.
Please help on the same.
Thanks,
Pavi

Hi Pavi,
Please check if the installed axis class files are installed properly.
http://host:port/XIAxisAdapter/MessageServlet
Please use above URL to check if axis class files are installed appropriately.
Hope after installing axis class files u have restarted the java stack.
hope this helps.
thanks and regards,
Praveen T

Sender SOAP Axis adapter

Hello Experts,
my scenario is to pick the data from web service and pass it to ECC side.
as i need to pick XML file from web service i used SOAP Axis adapter. configured as given in michal's blog.
the channel in running no errors in RWB, still its not picking the data.
Michal's PI tips: Exchange Rates from an XML file on a web page - REST, AXIS
your inputs on this...
regards,
chinna

Hi ,
I have confifured the same folw, it's working for me. please provide if you are getting any error.
Regards
srinivas

How to set content type in SOAP AXIS sender adapter

Hi All,
I am trying to fetch the data from an URL which has special characters(like Ä, ï) using SAP PI - SOAP AXIS adapter. I am facing the below error in the channel.
“error during receive: java.io.UnsupportedEncodingException: charset: utf-8”
I need to set the content type as ISO-9958-1 but there is no such option present in the SOAP AXIS sender Adapter. Please let me know if there is any way to set the content type and fetch the data successfully.
Thanks,
Konda

Hi Sudha,
I have tried textcodepageconversion, Message
Transformation and Annomizer beans but didn't help and this error is in sender SOAP AXIS adapter.
Thanks,
Konda

SOAP AXIS sender adapter response message

Hi all,
In our scenario a 3rd party app. is sending a request to our Sender SOAP Axis adapter. The message contains attachments and uses MTOM features. When receiving I have no problems. BUT when I sent a response I the SOAP AXIS adapter sents the attachmnt I received back.
Why does the AXIS adapter sents a response back with our attachment we received???? Any ideas? I tried to use a custom module to delete that part, but It cannot be edited. The modules input is just our normal message. Afterwards the attachment gets added...
Thanks

Not really sure about this, but have you tried to disable the Keep-Attachment option in the adapter (but if you're doing sync Axis comm., I don't think it would work as it would remove attachments when receiving them) ...
Chris

SOAP AXIS jars issue

Similar Messages

Maybe you are looking for