Accepting a SOAP message that contains fault elements

Hi,
I am trying to create a webservice that will accept a valid soap messages that
contains faults. Actual functionality required is to accept a valid soap message
with or without faults. For this, I created separate methods in my java class
(one for normal flow and one that will handle fault elements) that implements
my web service. I need to manipulate the soap message for both cases. Hence, I
created separate handlers to do this task. I created two handler chains in my
web-services.xml one for handling soap messages that contains faults and one for
handling soap messages that doesn't contain faults. The web services was successfully
deployed and works fine for soap messages that doesn't contain fault. But, if
I send a soap message with faults the client (that calls my webservice) is not
even hitting my web service. It gets a HTTP
500. Can anybody help me on this ?
Thanks,
Ganesh Balachandran

Hi Ganesh,
Which version of weblogic server you are using? Can you turn on verbose in
client side? You can give a "-Dweblogic.webservice.verbose=true" to client
side JVM. We need to see what your soap message with fault looks like.
Thanks,
-Neal
"Ganesh" <[email protected]> wrote in message
news:[email protected]..
>
Hi,
I am trying to create a webservice that will accept a valid soap messagesthat
contains faults. Actual functionality required is to accept a valid soapmessage
with or without faults. For this, I created separate methods in my javaclass
(one for normal flow and one that will handle fault elements) thatimplements
my web service. I need to manipulate the soap message for both cases.Hence, I
created separate handlers to do this task. I created two handler chains inmy
web-services.xml one for handling soap messages that contains faults andone for
handling soap messages that doesn't contain faults. The web services wassuccessfully
deployed and works fine for soap messages that doesn't contain fault. But,if
I send a soap message with faults the client (that calls my webservice) isnot
even hitting my web service. It gets a HTTP
500. Can anybody help me on this ?
Thanks,
Ganesh Balachandran

Similar Messages

How to create a element that contain a element generated in another document

Hi,anybody.
I want to create a element that contained a element generated in another document.The following is my coding:
doc1 = new XMLDocument();
ele1 = (XMLElement)doc1.createElement("AAA");
doc2 = new XMLDocument();
ele2 = (XMLElement)doc2.createElement("BBB");
ele2.appendChild(doc2.createTextNode("bbb"));
XMLNode ele = (XMLNode)ele2.cloneNode(true);
ele1.appendChild(ele);
but there is a DOMException,Node doesn't belong to the current document.
Thanks in advance.
null

Hi Marc,
it is currently not possible to check for values in other tables within different repositories (main tables).
If you want to check for values in flat lookup tables, use the "Fields" menu in the expression editor. You will get sth like this:
IS_NULL(Category.Item)
whereas "Category" could be a lookup table (flat, hierarchy, taxonomy) and "Item" a field in it.
Checking across qualified lookup tables is only possible in a very restricted manner.
Hope that helps.
Christian

I cannot send a photo nor a text message that contains a photo

I cannot send a photo nor a text message that contains a photo from my iphone. My cellular is on & my Wi-Fi. I have tried sending a photo with both on, WiFi off & cellular on, and WiFi on with cellular on. What else can I try?

Try a reset: hold down the home button along with the sleep/wake button until you see the apple, then let go. (No data loss)

Resending SOAP messages that failed

Hi All
I have a SOAP -> XI -> SOAP service.
I receive lots of messages at the same time from the sender webservice, when delivering to the receiver webservice a couple of messages will go into this webservice and some will say to be delivered, and then after a while turn to system error. Is there a way that I can get these messages to resend (or send till successful) because the error it comes back with when not getting into the receiver webservice is - soap fault: SOAP header ReliableMessaging was not understood. The messages should be fine I jsut don't think that the receiver side has a queue that can handle the load.....
Thanks
Clinton

Hi Udo
Thanks for your reply
The message that I am getting inside the AFW queue (get there with this url - http://sapxi:58000/MessagingSystem/receive/AFW/XI) and the message that i get is this -
2006-08-09 11:10:47 Success SOAP: request message entering the adapter
2006-08-09 11:10:47 Success SOAP: completed the processing
2006-08-09 11:10:49 Success The message was successfully received by the messaging system. Profile: XI URL: http://sapdxi:58200/MessagingSystem/receive/AFW/XI
2006-08-09 11:10:49 Success Using connection AFW. Trying to put the message into the receive queue.
2006-08-09 11:10:49 Success Message successfully put into the queue.
This message is inside the Message Monitor with <b>To be delivered</b> status.
Is there a way to not just let the message be put into the queue but let it send to the the webservice.
Thanks
Clinton

I receive an error message that the Photoshop Elements Organizer has stopped working

WHEN I LOG ON TO ADOBE PHOTOSHOP I GET A MESSAGE THAT ELEMENTS ORGNIZER HAS STOPED WORKING THIS A NEW PROGRAM THAT I JUST LOADED ON MY COMPUTER

Which OS are you on and which version of PSE you have?
Thanks
Andaleeb

How do I print the complete email message that contains a conversation?

When printing an email that has a thread or conversation only the most recent of the threads is printed.
When I select the email to print, I click the "see more from" to preview the full conversation.
I have downloaded the Mail app update just released. I am printing to an HP Officejet Pro 8500 printer.
This problem occurs on both my MBA mid 2011 and iMac late 2012, runing Mavericks.
I have also noted that if I use the export to pdf, from the Mail, File menu it creates the same type of output. that is only the most recent email is in the pdf.
This was not a problem with earlier versions of OS X

Thanks for the suggestions.
Just discovered that if you uncheck the "Orginize by Conversation" in the view menu, the most recent message will show the complete conversation. Which you can then print or export to pdf.
This is not a global setting, as each folder seems to retain its unique setting.
This behavior is completely different than previous versions of OS X's Mac Mail.

Implement a SOAP Request in an SSIS Package that sends a SOAP Message (Env) with Authentication Info, Receives XML FIle?

We need a small SSIS package to pass a SOAP message to a SOAP server and receive the response xml message.
We have the SOAP Endpoint, SOAP Action, and SOAP Message (which contains authentication elements). They work in a Talend Data Integration job (using
Talend's tSOAP component). A screenshot showing the Talend job and the configuration of the tSOAP component
is attached.
We need to implement the same thing in a Microsoft SQL Server 2012 SSIS package but haven't been able to get an SSIS Web Services task to work.
We haven't been able to configure it to pass the SOAP Action and SOAP Message.
How should this be accomplished in SSIS?
kholberger

I guess I was not clear. The Talend job works perfectly (and it took only a few minutes to configure).
I need to replicate the SOAP request function in an SSIS package. I've been trying to configure an SSIS Web Services Task to do that without success.
The SSIS Web Service Task asks for the .wsdl file, which I provide (though the Talend component
does not ask for it), but the SSIS WST does not ask for the SOAP Action or SOAP message. The target web service is protected by a security gateway that rejects the SSIS WST request. Somehow, the Talend tSOAP component sends the
SOAP message, which contains the security definition and authentication credentials (you can see part of that in the screen shot) which the endpoint accepts.
The question is: "How does one implement a SOAP web service request in an SSIS package that sends the SOAP Message".
Thanks.
kholberger

WSDL, custom datatypes, fault element name issues

Hello all,
I am having a LOT of problems with BEAs webservices. I am posting
this here in the hope that someone can help me and tell me what I am
doing incorrectly. I am running
WebLogic Server 7.0 SP1 Mon Sep 9 22:46:58 PDT 2002 206753
WebLogic XMLX Module 7.0 SP1 Mon Sep 9 22:54:41 PDT 2002 206753
Background:
My goal is to make my company's product web services aware. I take an
EJB, try to run it through the standard ant tasks and generate a web
services accessible EJB. Sounds pretty easy, but complex types seem
to make this quite difficult.
I have been able to create a web service accessible EJB (only since
7.0.1), but I am quite unhappy with the quality of what I am able to
produce.
I have a datatype which acts as a key, but it does not follow the
javabeans idiom - i.e. it does not have a default constructor or
accessor methods and I am not in the position to change it. I have
created a codec for this class which works and an xml schema (both by
hand). Its name is AgentKey. I have also had to use the autotyper to
create codecs and typemapping entries for java.util.Properties,
I can connect using the WebLogic classes and I am now trying to
interact using MS Excel and Apache's Axis as my test clients.
Issues:
My first question deals with generating a client. There seem to be
two ways to generate a client. Firstly via the <client> subtask of
<servicegen><service>, the second way via <clientgen> task. Since I
am using a custom data type (AgentKey) I have to manually insert the
AgentKey schema into the web-services.xml file generated by
servicegen. When I try to generate a client via the
servicegen/service/client task there is no opportunity for me to
insert this datatype schema information and I therefore get the
following messages (lots of them, but I'm only including one):
[servicegen] WARNINIG: Unable to find a javaType for the xmlType:['java:net.agentis.apml.runtime']:AgentKey.
Make sure that you have registered this xml type in the type mapping
[servicegen] Using SOAPElement instead
BTW: I am also receiving the same problem with java.util.Properties.
BTW: WARNING is misspelt
If I attempt to generate a client class via the <clientgen> task, I
need to supply either a wsdl or ear file as a parameter. I cannot
supply a wsdl file because I haven't deployed the EAR yet (and I don't
want to until the EAR has the client classes in it), and I can't
supply the EAR because I want the ear to include the client classes.
It is a bit of a catch 22 situation. Is there a solution I can't see?
NOTE: it would be very, very nice if you added a schemaMapping
attribute to the <servicegen/service> task so the web-services.xml
file didn't have to be manually hacked. Something similar to the
typemapping attribute already in the servicegen/service task would do
it.
My next problem deals with the validity of the WSDL. I am seeing that
the WSDL created has exceptions defined multiple times. I saw a
message from Manjo saying that it looked like a bug. I agree and
would like to get a copy of the patch. On a more significant note,
when is either SP2 or 7.1 due for release?
Another problem with the WSDL (once you have cleansed the multiple
exception messages) is that the fault elements of the
binding/operation elements require names and they don't have any. For
example, this is straight from the deployed EJB WSDL file:
<binding name="ExampleAgentPortSoapBinding" type="tns:ExampleAgentPort">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="serviceWithPrimitiveDatatypes">
<soap:operation soapAction="" style="rpc"/>
<input>
<soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output>
<soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
<fault>
<soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</fault>
</operation>
<operation ...
The schema definition at http://schemas.xmlsoap.org/wsdl/ says the
fault element require a name attribute:
<complexType name =" tBindingOperationFault">
<complexContent>
<extension base="wsdl:tExtensibleDocumented">
<attribute name="name" type="NCName" use="required"/>
</extension>
</complexContent>
</complexType>
The name of the fault should be the same name as the fault in the
portType definition. In my example the name is "AgentisException" as
evidenced by this snippet:
<portType name="ExampleAgentPort">
<operation name="serviceWithPrimitiveDatatypes">
<input message="tns:serviceWithPrimitiveDatatypes"/>
<output message="tns:serviceWithPrimitiveDatatypesResponse"/>
<fault name="AgentisException" message="tns:AgentisException"/>
</operation>
Once these changes have been made then the WSDL will validate. Are
there plans to fix these bugs?
On a different note, when I try to interact with a method that uses a
custom data type, such as AgentKey, via the "WebLogic Webservice
standard testing home page" the custom data type without a default
constructor cannot be rendered correctly. For instance, the AgentKey
value is:

<agentKey/>
Since I can't deploy a valid WSDL, I can't get either Axis or Excel to
connect to my web services.
When I attempt to invoke Axis' (beta 1.1) wsdl2java I recieve the
following message.
java.io.IOException: ERROR: Fault is missing a name= attribute in operation
"serviceWithPrimitiveDatatypes", in binding {http://sillyurl.com/reallysilly}ExampleAgentPortSoapBinding.
This seems understandable considering the issues I mentioned earlier.
Unfortunately Excel doesn't really give me anything to go with. If I
type in the WSDL URI then it will give me a list of methods I can
invoke, but if I try to add the service I get the very unhelpful "The
Web Service References Tool could not generate the requested code.
Any changes that were made to your project have been rolled back."
Any help with those two issues would be greatly appreciated also.
One final issue is that I cannot seem to fix is taskdef'ing
<servicegen> properly from Ant. I can do the actual taskdef but then
it cannot find classes from within the weblogic.jar. If I run the
setExamplesEnv.cmd first the I don't need to do the taskdef and
everything works fine. Has anyone else had this issue? (we can't run
that command on our clients desktops before we build our build scripts
- anyway, I've put it down to one of those weird Ant classpath
issues.)
In summary:
Problems I can see and would like some help on are:
- multiple exception messages
- fault operations with no name
- the ability to generate client code with complex data types before
the EAR is deployed.
Could the product team add
- a clean way to add in schema datatypes without having to manually
hack the web-services.xml file.
I know this has been quite a long email, but it has been months in the
making. Anyone's time would be greatly appreciated.
Mark Mansour
Agentis Software
[email protected]

Hi Mark,
From your base post:
My next problem deals with the validity of the WSDL. I am seeing that
the WSDL created has exceptions defined multiple times. I saw a
message from Manjo saying that it looked like a bug. I agree and
would like to get a copy of the patch. On a more significant note,
when is either SP2 or 7.1 due for release?I would recommend starting here with support since getting valid WSDL seems to be the root of most of
your issues.
Concerning the upcoming release, I believe it is scheduled for late this quarter; contact Michael
([email protected]) for more information.
Also, at the bottom of this post:
I would just like to see an automated way to do this (I've had to write my own
utility to do this for me :(Does the autotype ant task help in this situation? Have you taken a look at this?
http://e-docs.bea.com/wls/docs70/webserv/anttasks.html#1080062
Thanks,
Bruce
Mark Mansour wrote:
Hiya Bruce,
I will try and get some time to follow this up with the support people too.
In response:
Problems I can see and would like some help on are:
- multiple exception messages
In your client code, you can set the following property to avoid the exceptionmessages so that the typemapping
registry can be setup.
//dont parse wsdl till we set the typemapping
System.setProperty( "weblogic.webservice.servicenamechecking","false" );
This is not a client issue. The WSDL is generating incorrect WSDL. Here is a
little snippet :
<message name="AgentisException" >
<part name="AgentisException" xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
<message name="setTraceLevel" >
<part name="agentKey" xmlns:partns="java:net.agentis.apml.runtime" type="partns:AgentKey"
/>
<part name="intVal" xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:int"
/>
</message>
<message name="AgentisException" >
<part name="AgentisException" xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
As you can see the AgentisException is defined twice (in my real WSDL it is redefined
every time a method has the AgentisException in its interface (which in my case
is 5 times))
- fault operations with no nameI believe the fault issues that you have raised have been addressed in the upcomingrelease that will be
available for beta testing shortly. Contact [email protected] if you
want to participate in the beta.
great. Is there any ETA on the final release date?
- the ability to generate client code with complex data types before
the EAR is deployed.
There is an example to show how to do this: http://dev2dev.bea.com/direct/webservice/dyncmplx.zip
Unfortunately this doesn't solve my problem. I still don't have an EAR or WSDL
file from which I can generate a client to be included in the final EAR file that
gets deployed to the server. My original post explains this a bit better.
Could the product team add
- a clean way to add in schema datatypes without having to manually
hack the web-services.xml file.
Take a look at http://dev2dev.bea.com/direct/webservice/wswa.html#qz50 and others
in this area.
This was more in reference to the building of the web services in the first place
rather than registering custom datatypes at runtime. The manual procedure is
documented at http://edocs.bea.com/wls/docs70/webserv/customdata.html#1058102,
I would just like to see an automated way to do this (I've had to write my own
utility to do this for me :(
Hope this helps,
Bruce
Thanks Bruce.
Mark

Outbound SOAP Message with Attachment

The requirement is to invoke a web service by sending attachments in the outbound SOAP message. The attachment body needs to be assigned in the message flow, using an element E1 extracted from the message incoming into the flow.
I am trying to use attachments variable to set content-type (text/xml) and body using E1. However, these are not getting assigned to attachments variable, as seen by logging the variable.
I was told that $attachments cannot be changed inside the flow (it is marked black in the console unlike the header and body that are marked green). If that is the case, how do we invoke services using attachments from a message flow?
Any pointers would be appreciated.

Hi,
A SOAP message may need to be transmitted together with attachments of various sorts, ranging from facsimile images of legal documents to engineering drawings. Such data are often in some binary format. For example, most images on the Internet are transmitted using either GIF or JPEG data formats. In this document we describe a standard way to associate a SOAP message with one or more attachments in their native format in a multipart MIME structure for transport.
yes it is possible to send attachment with the SOAP.
SOAP Message Packages
A "SOAP message package" contains a primary SOAP 1.1 message. It may also contain additional entities that are not lexically within the SOAP message but are related in some manner. These entities may contain data in formats other than XML. The primary SOAP 1.1 message in a message package may reference the additional entities. Such additional entities are often informally referred to as "attachments." This section describes how to construct SOAP message packages and how SOAP processors will process them.
A SOAP message package is constructed using the Multipart/Related media type, which is defined in RFC 2387. The rules for the construction of SOAP message packages are as follows:
The primary SOAP 1.1 message must be carried in the root body part of the Multipart/Related structure. Consequently the type parameter of the Multipart/Related media header will always equal the Content-Type header for the primary SOAP 1.1 message, i.e., text/xml.
The MIME Multipart/Related encapsulation of a SOAP message is semantically equivalent to a SOAP protocol binding in that the SOAP message itself is not aware that it is being encapsulated. That is, there is nothing in the primary SOAP message proper that indicates that the SOAP message is encapsulated .
For more details you can refer these links
http://www.w3.org/TR/SOAP-attachments
http://www.w3.org/TR/soap12-af/
regards
Aashish Sinha
PS : reward points if helpful

Logging SOAP messages

I need help on how to use handlers in Weblogic Workshop web services. I have the following logging handler from the bea documentation site.
Now, if I want to log my SOAP messages on the server side, do I just need to put the annotation:
* @jws:handler operation="handler.ConsoleLoggingHandler"
at the top of my JWS file? If that is the case, I don't see any messages being logged. Any help will be greatly appreciated.
Thanks.
gtata
package handler;
import java.util.Iterator;
import javax.xml.rpc.handler.MessageContext;
import javax.xml.rpc.handler.soap.SOAPMessageContext;
import javax.xml.soap.SOAPElement;
// for readability, using weblogic API instead of javax.xml.rpc.handler.GenericHandler
// See http://edocs.beasys.com/wls/docs81/webserv/interceptors.html#1060763
import weblogic.webservice.GenericHandler;
* Purpose: Log all messages to the Server console
public class ConsoleLoggingHandler extends GenericHandler
* Handles incoming web service requests and outgoing callback requests
public boolean handleRequest(MessageContext mc)
logSoapMessage(mc, "handleRequest");
return true;
* Handles outgoing web service responses and incoming callback responses
public boolean handleResponse(MessageContext mc)
this.logSoapMessage(mc, "handleResponse");
return true;
* Handles SOAP Faults that may occur during message processing
public boolean handleFault(MessageContext mc)
this.logSoapMessage(mc, "handleFault");
return true;
* Log the message to the server console using System.out
protected void logSoapMessage(MessageContext mc, String eventType)
try
System.out.println("*****************************");
System.out.println("Event: "+eventType);
System.out.println("Endpoint Method: " + getMethodName(mc));
System.out.println("Soap message is: \n " +
com.bea.wlw.runtime.jws.soap.util.SAAJUtil.SOAPPart2String(
((SOAPMessageContext)mc).getMessage() ) + "\n");
System.out.println("*****************************");
catch( Exception e )
e.printStackTrace();
* Get the method Name from a SOAP Payload.
protected String getMethodName(MessageContext mc)
String operationName = null;
try
SOAPMessageContext messageContext = (SOAPMessageContext) mc;
// assume the operation name is the first element
// after SOAP:Body element
Iterator i = messageContext.
getMessage().getSOAPPart().getEnvelope().getBody().getChildElements();
while ( i.hasNext() )
Object obj = i.next();
if(obj instanceof SOAPElement)
SOAPElement e = (SOAPElement) obj;
operationName = e.getElementName().getLocalName();
break;
catch(Exception e)
e.printStackTrace();
return operationName;
}

You can use the logging and tracing functionality to write log statements anywhere in BPEL. refer http://wiki.open-esb.java.net/Wiki.jsp?page=LoggingFromWSBPELActivityInABusinessProcess . But you should keep in mind these are not soap messages that you log. They will be abstract WSDL message instances. If you want to log specifically the soap messages you need the support in HTTP-BC.
If you turn on logging you should see the line number of BPEL where it fails. That should give you some indication. I am not 100% sure, but in the logs, we should be logging the variable which was not initialized. I can't think of any other way to find out which variable caused this exception.
-Kiran Bhumana

Soap Message in webservice

Hello All,
I have a SOAP request as below shich is sent from a client proxy(consumer proxy) in SAP.
POST /blw/annehmen/2/0/ws/sendeWholesaleMeldung
HTTP/1.1..Content-Type: text/xml;
charset=utf-8..Content-Length:23711..accept-language: en..sap-language: E..soapaction: ""..accept: text/xml..
sap-srt_id: 20090804/162628/v1.00_final_6.40/4A71719D8F44393BE10000000AAF5D7F..
user-agent: SAP Web Application Server (1.0;700)..
host: 10.13.21.619:12000..accept-encoding: gzip....
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Header>
     <soap-env:Body>
          <n0:sendeWholesaleMeldungRequest xmlns:n0="http://wholesale.de/portal/blw/v2"
                        xmlns:prx="urn:sap.com:proxy:DWT::700:2008/01/11">
               <n0:Meldung>
                    <n0:Meldungsnummer>Str 313</n0:Meldungsnummer>
                    <n0:Geschaeftsfallart>string 314</n0:Geschaeftsfallart>
                    >
               </n0:Meldung>
          </n0:sendeWholesaleMeldungRequest>
     </soap-env:Body>
</soap-env:Envelope>
I want to send the type of the complex type Meldung like
<n0:Meldung xsi:type="swm:MeldungENTMType">
in the SOAP message that i sent.
Can anyone please let me know how this could be achieved.

No cross posting
Read the "Rules of Engagement"
Regards
Juan

How to send a signed SOAP message with additional HTTP Header fields

Our Partner's integration requirements are that we send them asynchronous SOAP messages, that are digitally signed, and whose HTTP headers contains 5 or 6 additional header fields, of which 3 or 4 will need to be dynamically set during the message mapping. I believe we can use the HTTP adapter for adding new fields to the HTTP header, but don't believe it supports signing. I believe that the SOAP adapter supports signing, but I'm not clear on how to use it to add fields to the HTTP header. What is the most straight-forward way to achieve both the signing of the message and the addition of the HTTP header values?
Thanks,
Kurt

>>>What is the most straight-forward way to achieve both the signing of the message and the addition of the HTTP header values?
Use Java mapping for both.
1) Signing the message
You can digitally sign the soap message using many standard api like WSS4j? or refer Java XML signature API which comes in Jdk1.6.
Refer these links
WSS4J - http://ws.apache.org/wss4j/axis.html
Java XML signature : http://java.sun.com/developer/technicalArticles/xml/dig_signature_api/
2) >>whose HTTP headers contains 5 or 6 additional header fields, of which 3 or 4 will need to be dynamically set during the message mapping
Use Dynamic configuration API to set the additional header fields during message mapping.

Soap message with Attachment

Hi All,
I have a requirement wherin I have to send an attachment(image) along with the soap payload.i.e. the soap message contains the payload and an attachment.For eg. the soap message is as shown below:
<?xml version="1.0" encoding="UTF-8" ?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
    <ns1:MT_Soap xmlns:ns1="http://www.adc.com/sample">
         <Record>
            <FieldXML>abc</FieldXML>
            <FieldAthmt />
         </Record>
      </ns1:MT_Soap>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
How can I include the attachment(which is on a local machine) in the above soap message?
Is it posssible to send the attachment in the field "FieldAtthmt"?
If it is possible to send an attachment with the soap message then how can that attachment be handled in XI?
Thanks in advance,
Vikram

Hi,
A SOAP message may need to be transmitted together with attachments of various sorts, ranging from facsimile images of legal documents to engineering drawings. Such data are often in some binary format. For example, most images on the Internet are transmitted using either GIF or JPEG data formats. In this document we describe a standard way to associate a SOAP message with one or more attachments in their native format in a multipart MIME structure for transport.
yes it is possible to send attachment with the SOAP.
SOAP Message Packages
A "SOAP message package" contains a primary SOAP 1.1 message. It may also contain additional entities that are not lexically within the SOAP message but are related in some manner. These entities may contain data in formats other than XML. The primary SOAP 1.1 message in a message package may reference the additional entities. Such additional entities are often informally referred to as "attachments." This section describes how to construct SOAP message packages and how SOAP processors will process them.
A SOAP message package is constructed using the Multipart/Related media type, which is defined in RFC 2387. The rules for the construction of SOAP message packages are as follows:
The primary SOAP 1.1 message must be carried in the root body part of the Multipart/Related structure. Consequently the type parameter of the Multipart/Related media header will always equal the Content-Type header for the primary SOAP 1.1 message, i.e., text/xml.
The MIME Multipart/Related encapsulation of a SOAP message is semantically equivalent to a SOAP protocol binding in that the SOAP message itself is not aware that it is being encapsulated. That is, there is nothing in the primary SOAP message proper that indicates that the SOAP message is encapsulated .
For more details you can refer these links
http://www.w3.org/TR/SOAP-attachments
http://www.w3.org/TR/soap12-af/
regards
Aashish Sinha
PS : reward points if helpful

SOAP Messaging Missing

Hi buddies,
     Have you ever been suffering from missing messages of SOAP sender adapter?
     The java sender program shows that the messaging has been delivered to XI SOAP adapter successfully, but I cannot find it in neither adapter engine, nor integration engine.
     BTW, our clients use the XFire technology to generate the soap message and send it without any exception to be throw out.
     Any suggestions?
YiNing

if I want to use SOAP sender adapter in asynchronous senario, is there any method that can be used to avoid this issue?
I've been suffering this from gSOAP which using C++, XFire which using Java in different projects.
I found these tools determines whether the receiver system have accepted the soap message by getting the http code 200.
Edited by: YiNing Mao on Jan 29, 2008 5:33 PM

Can't Verify a SOAP message

I have a problem in verifying a SOAP message that I have created my self, after signing the message and then convert it to string, I try to verify it, but it returns false each time, but when I use the Document after siging it without converting it to a string , it works, I really need some one to tell me why is it doing this here is the code for both cases
- Converting Document to String before verifying sugnature
signature.sign(dsc);
TransformerFactory tf = TransformerFactory.newInstance();
Transformer trans = tf.newTransformer();
StringWriter signedXMl = new StringWriter();
trans.transform(new DOMSource(docElement), new StreamResult(signedXMl));
String tempstr = signedXMl.toString();
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
dbf.setNamespaceAware(true);
NodeList nl = null;
DocumentBuilder builder = dbf.newDocumentBuilder();
Document doc = builder.parse(new InputSource(new StringReader(inXML)));
nl = doc.getElementsByTagNameNS(XMLSignature.XMLNS, "Signature");
if (nl.getLength() == 0)
                    System.out.println("In main: ERROR - Cannot find Signature element");
validateElement(nl.item(0),kp);---------------------------------------------------------------------------------------------
- Using the same Document element used in Signing for verification
signature.sign(dsc);
NodeList nl = doc.getElementsByTagNameNS(XMLSignature.XMLNS, "Signature");
validateElement(nl.item(0),kp);----------------------------------------------
both use validateElement function
private static void validateElement(Node signElement,KeyPair kp) {
                 DOMValidateContext valContext = new DOMValidateContext(kp.getPublic(), signElement);
          String providerName = System.getProperty("jsr105Provider","org.jcp.xml.dsig.internal.dom.XMLDSigRI");
          XMLSignatureFactory factory = null;
          XMLSignature signature = null;
          try
               factory = XMLSignatureFactory.getInstance("DOM",(Provider) Class.forName(providerName).newInstance());
               signature = factory.unmarshalXMLSignature(valContext);
               boolean coreValidity = signature.validate(valContext);
               String kiki = null;
               boolean sv = signature.getSignatureValue().validate(valContext);
               //System.out.println("signature validation status: " sv);
               Iterator i = signature.getSignedInfo().getReferences().iterator();
               for (int j=0; i.hasNext(); j++)
                    boolean refValid = ((Reference) i.next()).validate(valContext);
                    String koko = null;
          } catch (Exception e)
               String koko = null;
I really apreciate any input, I don't know what to do

There is no such system as Windows 7 Vista SP2. Either you have Windows 7 or Windows Vista. If your system is Vista, then sending video messages is not available. This feature is only present on Windows 7 and higher systems.

Accepting a SOAP message that contains fault elements

Similar Messages

Maybe you are looking for