SOAP encoding formats and interoperability

Hi,
Being new to Web Services, I have spend quite a bit of time over the past few
days investigating the technology. Based on several newgroup posts and articles
I have found, it appears that for the best performance and scalability, you should
use SOAP document-style encoding [1]. My question is how do the various encoding
formats affect interoperabiliy? The article referenced below indicates that most
of the .NET tools default to using document-style encoding. Is it safe to say
for the best of all worlds (performance, scalability, and interoperability) you
should develop your Web Services using document-style encoding?
1. http://dev2dev.bea.com/products/wlworkshop/articles/Cohen.jsp
TIA,
Kent

Hi Kent,
Yes, doc/lit is the best approach for interop. Also look for guidance
from the WS-I Basic Profile [1]
Hope this helps,
Bruce
[1]
http://www.ws-i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.html
Kent Kvarfordt wrote:
>
Hi,
Being new to Web Services, I have spend quite a bit of time over the past few
days investigating the technology. Based on several newgroup posts and articles
I have found, it appears that for the best performance and scalability, you should
use SOAP document-style encoding [1]. My question is how do the various encoding
formats affect interoperabiliy? The article referenced below indicates that most
of the .NET tools default to using document-style encoding. Is it safe to say
for the best of all worlds (performance, scalability, and interoperability) you
should develop your Web Services using document-style encoding?
1. http://dev2dev.bea.com/products/wlworkshop/articles/Cohen.jsp
TIA,
Kent

Similar Messages

SOAP Encoding and the real need

I just read the below from the site here-
SOAP encoding has fallen out of favor in the Web services community. It is not supported by the WS-I basic profile. So JAX-WS, as the latest incarnation of Java Web services, has disallowed SOAP encoding. JAX-RPC supports SOAP encoding, so if you really must use SOAP encoded messages, stick with JAX-RPC.
I am new to Web Services and am familiar with DOC/Literal only.
Why will anyone want to create a "new" Web service in Encoded format?
What was the real need SOAPEncoding has served when there is a separate standard named XML Schema?
Just curious to explore-

Hello,
The WS-I work constrains the various web service specification to a
functional subset that exhibit the greatest degree of interoperability;
certainly there are many other features (quality of service, security,
attachments, etc.) that are provided by WebLogic web services; this does
not negate the fact that BP 1.0 compliance can be easily achieved.
Regards,
Bruce
Vasudev Kumarjiguda wrote:
>
Hi,
The Basic Profile 1.0 forbids SOAP encoding, yet Bea WebLogic documentation mentions
that RPC-oriented WebLogic Web Service operations use SOAP encoding.
Am I missing something here (since Bea supports the Basic Profile 1.0) ?
thanks
Vasu

HT1351 I've encoded a vinyl LP record into digital format and recorded it onto an usb as MP3 file. But when I tried to copy it onto my ipod classic, I get a message stating "was not copied to the ipod because it cannot be played on this ipod". Why?

I've encoded a vinyl LP record into digital format and recorded it onto an usb as MP3 file. But when I tried to copy it onto my ipod classic, I get a message stating "was not copied to the ipod because it cannot be played on this ipod". Why?

I was refering to the "sample rate", normally 44.1 KHz, the iPod might not be able to play tracks with a non-standard rate. Otherwise I'm not sure what the issue might be.
tt2

Interoperability between apache soap toolkit(client)and ms soap toolkit

Interoperability between apache soap toolkit(client)and ms soap toolkit.Give me an example where i can send and receive a complex data type from apache tomcat in client side to ms soap toolkit on the server side.It is urgent.Plz try to give me a solution as soon as possible.

The toolkits don't have to work together at all. And by the way, you aren't sending the data to the MS toolkit, you're sending it to some MS product that can process the data. Any data that follows the standards should work.

SOAP encoding and Basic Profile 1.0

Hi,
The Basic Profile 1.0 forbids SOAP encoding, yet Bea WebLogic documentation mentions
that RPC-oriented WebLogic Web Service operations use SOAP encoding.
Am I missing something here (since Bea supports the Basic Profile 1.0) ?
thanks
Vasu

Hello,
The WS-I work constrains the various web service specification to a
functional subset that exhibit the greatest degree of interoperability;
certainly there are many other features (quality of service, security,
attachments, etc.) that are provided by WebLogic web services; this does
not negate the fact that BP 1.0 compliance can be easily achieved.
Regards,
Bruce
Vasudev Kumarjiguda wrote:
>
Hi,
The Basic Profile 1.0 forbids SOAP encoding, yet Bea WebLogic documentation mentions
that RPC-oriented WebLogic Web Service operations use SOAP encoding.
Am I missing something here (since Bea supports the Basic Profile 1.0) ?
thanks
Vasu

SOAP to EMAIL and sending the response to SOAP by integration process

Hi,
I need to design a scenario from SOAP TO EMAIL and based on the status of the EMAIL being sent i need to send the response to SOAP using integration.If it is SUCCESSFUL message i need to send success and if the mail is not sent i need to send error .
could some one help how to design the Integration process for this scenario?will help me what steps i need to use for this .
Thanks
Rajesh

Hi Rajesh,
You can achieve this by making synchronous Interfaces.
1) create Synchronous Outbound and Inbound Service Interface.
2) So you will need to create a response mapping as well.
You get a response from mail adapter in the following format, use this as response Message Type:
- <xim:MailReceipt xmlns:xim="http://sap.com/xi/XI/Mail/30">
<Server>smtp://xx.xxx.xx.xx</Server>
<Greeting>wlg-exht2.XYZ.com Microsoft ESMTP MAIL Service ready at Fri, 28 Jan 2011 20:10:28 +1300</Greeting>
<Format>XIALL</Format>
<UseMailPackage>false</UseMailPackage>
<Encoding>base64</Encoding>
<Subject>Sync Test</Subject>
<From>"From e mail address</From>
<To>"To e mail address"</To>
<Date>2011-01-28T07:10:29Z</Date>
<MailID>1.2.3</MailID>
</xim:MailReceipt>
By this I think you can give the status of Mail.
Regards,
Aravind

SOAP-XML Format

Hi all,
I have a basic doubt regarding SOAP-XML format.
Why the message in XI is transformed as SOAP-XML instead of just XML. What is the advantage of using SOAP concept?
Thanks in advance.
Regards
Bhanu.

Hi,
Basically used for exchanging information in a decentralized, distributed environment
A Web service is a software system designed to support interoperable machine-to-machine interaction over a network. It has an interface described in a machine-processable format (specifically WSDL). Other systems interact with the Web service in a manner prescribed by its description using SOAP messages, typically conveyed using HTTP with an XML serialization in conjunction with other Web-related standards.
One typical use of SOAP attachments is
*for transporting intact, binary data
such as image files.
*For another example, your system may need to transport
XML documents to other parts of the system without the overhead of
validating them. These XML documents that do not need to conform to your
particular schema or DTD can be passed as attachments.
*By using SOAP attachments, the SOAP message body is much smaller
because it contains only a reference to the data and not the data itself.
*Using attachments can be more efficient because smaller SOAP messages are
processed more quickly than very large messages, and the translation of the
data to Java objects is reduced for attachments.
*SOAP attachments are implemented by wrapping the SOAP message and one
or more attachments in an envelope of Multipurpose Internet Mail Extensions
(MIME).
Regards,
Nutan

How to decoding and encoding PNG and GIF images?

I could decode and encode JPEG images using following create functions which are in com.sun.image.codec.jpeg package.
JPEGImageDecoder decoder = JPEGCodec .createJPEGDecoder(inputStream);
JPEGImageEncoder encoder = JPEGCodec .createJPEGEncoder(outputStream);
But I dont know required package and functions to decode and encode PNG and GIF images. Please help me.

Is the API that hard to follow?
ImageIO.read( file/stream/url)
ImageIO.write( image, format (e.g. PNG, GIF(1), JPEG), file/stream what have you)
1) Not sure if Java supports GIF saving, it might if you install JAI, or Java 6.

XML parser not able to find encoding format of xml file with jre1.4.2

Hi
I am using jre1.4.2_05 and Weblogic 8.1 version and i have a problem with finding encoding format of xml file.
I need to parse a xml file and need to find which encoding format that xml is based on that i need to change logic.
Need to know after parsing each xml file what encoding format the xml is? Here the problem is we are using jre1.4.2_05 by default DOM \ SAX parser is not supported and i looked at few third party parser which are also don't have facility.
But in latest jre 1.5 or jdk1.5 has this feature. Its difficult to the project to upgrade to jre1.5 or more.
Please let me know if you have any idea about the issue.

I had a quick look around and I think you might be able to find them in the support portal...
SAP Support Portal > Software Downloads > SAP Software Download Centre > Support Packages and Patches > Archive for Support Packages and Patches > Archive - Browse our Download Catalog > SAP Connectors.
Let me know if you find them.
Regards,
Stephen.

Converting String To XML Format and send as attachment

Hi
My requirement is to convert String into XML Format and that XML File i have to send as an attachment
can any one one give solution for this Problem.
Thank you
Venkatesh.K

hi,
i m filling the itab first and converting to xml
itab contaning these data
GS_PERSON-CUST_ID   = '3'.
GS_PERSON-FIRSTNAME = 'Bill'.
GS_PERSON-LASTNAME = 'Gates'.
APPEND GS_PERSON TO GT_PERSON.
GS_PERSON-CUST_ID   = '4'.
GS_PERSON-FIRSTNAME = 'Frodo'.
GS_PERSON-LASTNAME = 'Baggins'.
APPEND GS_PERSON TO GT_PERSON.
after conversion data is coming like that
#<?xml version="1.0" encoding="utf-16"?>
<CUSTOMERS>
<item>
    <customer_id>0003</customer_id>
    <first_name>Bill</first_name>
    <last_name>Gates</last_name>
</item>
<item>
    <customer_id>0004</customer_id>
    <first_name>Frodo</first_name>
    <last_name>Baggins</last_name>
</item>
</CUSTOMERS>
but errors are 1) # is coming at the first
                        2)for 'encoding="utf-16"?>', it is not coming perfectly, some other data (iso-8859-1) should come here
can anybody plz solve it.
regards,
viki

SOAP envelope format

Hi,
I must make sample code of web service calls for PHP and Java to our clients. So far I have got it working with PHP but I have trouble to successfuly call web service in Java.
I have generated stub files with wscompile -keep -gen:client config.xml
It makes SOAP envelope, and calls service but there is no response - unfortunetly i cant debug cause from server side, but it must have something to do with SOAP envelope. Server side is done with Microsoft SOAP Toolkit. I have included Java generated envelope and nosoap (PHP)generated envelope (PHP one works). (PS! TimeToSend field is 0 in PHP version and 0.0 in Java, can it be cause?)
Envelope with Java:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://tempuri.org/fmts/message/" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<env:Body>
<ns0:SendSMS>
<MessageText xsi:type="xsd:string">test</MessageText>
<TimeToSend xsi:type="xsd:double">0.0</TimeToSend>
<StatusURL xsi:type="xsd:string"></StatusURL>
</ns0:SendSMS>
</env:Body>
</env:Envelope>
Using nosoap lib for PHP envelope looks like this:
<SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:si="http://soapinterop.org/xsd" xmlns:nu="http://tempuri.org/fmts/message/">
<SOAP-ENV:Body>
<nu:SendSMS>
<MessageText xsi:type="xsd:string">PHP</MessageText>
<TimeToSend xsi:type="xsd:double">0</TimeToSend>
<StatusURL xsi:type="xsd:string"></StatusURL>
</nu:SendSMS>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Found out what was frong. There was password field in envelope (removed it in previous post - and i managed to enter wrong password)

How can I know the encoding format for a file.

I have files encoded in English, Spanish, Japanese etc. I want to know which file has which encoding format while reading.
Can anyone suggest.
Ashish

Language is different from "encoding"...if you mean character encoding. Multiple languages can be represented by a single encoding. The fact that you mix language and encoding in your question confuses me about what you are asking.
If you want to know what language a file uses, you can always use a meta-tag. Or you can do some kind of text analysis based on dictionary lookups to determine language...too complex for my tastes. I think a simple language tag in the file makes more sense.
As for character encoding, you either standardize on a single encoding for all files or again use a meta-tag. If you standardize on a single encoding, you should probably consider one of the Unicode encodings instead of any other character set encoding.
Regards,
John O'Conner

How to change encoding format in OSB?? -- Plz help

Hi,
I have developed a service with all its xsds and wsdls in UTF-8 encoding format. But for now the requirement is ISO-8859-1 format. So for that i right clicked on each XMLs and wsdls, Prperties-->text File encoding -->Others --> IS0-8859-1. But the changes are not getting reflected. Do i have to do anything else other than this?? Pls help me
Regards
Prabhu

Hi Anuj,
The business service and proxy are not http transport based, they are jca transport based. So default is UTF-8.
And more over they are updating the response which they got from the previous osb service using osb service 2. This is the case. Front end team using java to code their applications.
Service1 Output: Jca transport
<OutputParameters xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/BGN/KBGN_API_WEB_PORTAL/PBGN_SEARCH_ADDRESS/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<P_NM_STREET_TYPE>Área Especial</P_NM_STREET_TYPE>
<P_NM_STREET>
Rodovia DF-001 (Gama ao Recanto das Emas)
</P_NM_STREET>
<P_DE_COMPLEMENT>CAUB I</P_DE_COMPLEMENT>
<P_NM_DISTRICT xsi:nil="true"/>
<P_NM_LOCALITY>Gama</P_NM_LOCALITY>
<P_CD_STATE>
DF
</P_CD_STATE>
<P_RETORNO>E0000</P_RETORNO>
<P_MENSAGEM xsi:nil="true"/>
</OutputParameters>
They get these values using java code and update these using service2 that also a jca transport based. The problem is in updating these values.

RPC/SOAP-Encoded Web Service with Workshop

Is there anyway to create a RPC/SOAP-Encoded Web Service with Workshop ? There is an "encoding" attribute in the autotype ant task but no corresponding properties in Workshop.

Hi,
Thanks for the reference.
I have checked both in the wsdl and the Soap message,
rpc property effectively means rpc/encoded. Now that
would say that RPC/Literal is not supported ?
Here are what the messages looks like with rpc and
document properties
Thanks all for making this clear.
document wlw property = Document/Literal
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<ns:getEmployeeResponse xmlns:ns="http://www.openuri.org/">
<ns:getEmployeeResult xmlns:ns="http://www.openuri.org/">
<ns:Address xmlns:ns="http://www.openuri.org/">
<ns:City xmlns:ns="http://www.openuri.org/">Luxembourg</ns:City>
<ns:Country xmlns:ns="http://www.openuri.org/">LU</ns:Country>
<ns:Number xmlns:ns="http://www.openuri.org/">2</ns:Number>
<ns:PostCode xmlns:ns="http://www.openuri.org/">1000</ns:PostCode>
<ns:Street xmlns:ns="http://www.openuri.org/">Bld. Royal</ns:Street>
</ns:Address>
<ns:Age xmlns:ns="http://www.openuri.org/">20</ns:Age>
<ns:Name xmlns:ns="http://www.openuri.org/">Dupont</ns:Name>
<ns:FirstNames xmlns:ns="http://www.openuri.org/">
<ns:String xmlns:ns="http://www.openuri.org/">Jean</ns:String>
<ns:String xmlns:ns="http://www.openuri.org/">Jacques</ns:String>
</ns:FirstNames>
</ns:getEmployeeResult>
</ns:getEmployeeResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
rpc wlw property = RPC/Soap-Encoded
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<ns:getEmployeeResponse xmlns:ns="http://www.openuri.org/">
<getEmployeeResult xmlns:s="http://www.openuri.org/encodedTypes" xsi:type="s:Employee">
<Address xsi:type="s:Address">
<City xsi:type="xsd:string">Luxembourg</City>
<Country xsi:type="xsd:string">LU</Country>
<Number xsi:type="xsd:int">2</Number>
<PostCode xsi:type="xsd:string">1000</PostCode>
<Street xsi:type="xsd:string">Bld. Royal</Street>
</Address>
<Age xsi:type="xsd:int">20</Age>
<Name xsi:type="xsd:string">Dupont</Name>
<FirstNames SOAP-ENC:arrayType="xsd:string[2]" xsi:type="SOAP-ENC:Array">
<String xsi:type="xsd:string">Jean</String>
<String xsi:type="xsd:string">Jacques</String>
</FirstNames>
</getEmployeeResult>
</ns:getEmployeeResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Message was edited by phcollignon at Aug 27, 2004 2:54 AM

Some advice on audio formats and converting tracks

_*Some thoughts about audio formats and conversions. These are all supported by iTunes unless stated otherwise.*_
General principles : there is no point in converting an already compressed track into a higher bit rate - it may seem as if this would give an improved quality, but once information has been lost through compression, there is no recovering it. The sound MAY be improved subjectively through the use of an appropriate EQ setting.
This is not a definitive list : other formats, for example the one used by Real Player, and the ATRAC minidisc codec used by Sony, are not listed : many of the following can be used in iTunes, or are reasonably well-known.
To use one of the available formats, they should be set in the Importing tag in *iTunes Preferences* (Advanced prior to iTunes 8, now in General). Once set, the format is used for importing CDs, but can also be used to convert tracks already in iTunes (using the Advanced menu : +Convert Selection to xxx+ ). It is not used when dropping files onto iTunes, or using Add To Library.
1. _Lossless formats_
Certain high-quality audio formats are "Lossless". This means that if the track is re-converted into the same format (after editing, for example), it will not degrade no matter how many times that is done.
.AIFF - a format (common in Macs) representing full CD quality. Bit-rates are over 1400 kbps; +1 minute of music is approx 10MB.+
.WAV - more or less the same as .AIFF but a Windows format.
*Apple Lossless* - a 'once-only compression', applied to .AIFF or .WAV tracks to retain quality but reduce file sizes. A little (totally inaudible) information is lost, but also a more efficient 'codec' (compression algorithm) is involved. +1 minute = approx 5MB.+
.FLAC - similar to Apple Lossless, but less proprietary (a more open standard). Not supported by iTunes.
2. _'Lossy' formats_
These formats are so-called because each time the conversion is done, the track is re-compressed, and more information is lost even if the file size remains the same. Various quality settings can be chosen, from around 320 kbps (high) down to below 128 kbps, though 128 is reckoned to be the lowest acceptable bit rate to listen to music in stereo.
In general, the higher the input quality, the higher the output quality when 'stepping down'. Therefore an .AIFF track converted directly to 128kbps 'lossy' will sound better than a 256kbps track re-compressed to the same 128kbps.
.MP3 - a standard audio compression format that has been around for many years. Common everywhere, and supported by virtually all contemporary music players. The codec has been improved so that modern MP3s sound markedly better than earlier versions. +1 minute @ 128 kbps = approx 1MB.+
.AAC - a superior codec to MP3 (though the quality gap has narrowed), which has been chosen by Apple as the iTunes format of choice. Nowadays, a track at 128 kbps .AAC will sound around the same quality as the same track at 160 kbps MP3. +1 minute @ 128 kbps = approx 1MB.+
.WMA - Windows' own proprietary lossy codec. It seems to have a bright and sparkly sound compared to MP3, but lacks a decent 'bottom end', i.e. the bass tones are somewhat lacking. Not supported by iTunes. (Can be played using VLC).
.OGG - the open standard Ogg Vorbis format, often held to be superior to MP3 but little-used and therefore not supported in many platforms and players, including iTunes.
When considering which format to use, the most important things to remember are
1. how will these tracks be played back? (on a hi-fi? an iPod? expensive earphones?)
2. the quality will depend finally on the judgement of the listener (some ears are better at telling small differences in quality than others)
3. how much space is available to store (and expand) the music library?
As for quality, a good way to decide is to "audition" different formats. Using one CD track known to you, try importing it at several different formats and bit rates (using iTunes Preferences). Then just play them, see which sounds best to you. In this way I came to decide for myself that AAC @ 256kbps was the best for me +(1 minute = approx 2MB).+

The Windows version of iTunes supports importing of WMA files, converting them to one of the other formats. Mac iTunes offers now support of WMA files at all.
Good point - and if I knew more about iTunes on Windows I would amend that and post a different version of the article in their forum.
I accept the point about .WAV files being used also for compressed formats but didn't want to make it too complicated; the most common use for .WAV I believe, is full quality audio.
On the subject of Lossless compressed audio (FLAC and AL), Wikipedia has this :
_*Difficulties in lossless compression of audio data*_
+It is difficult to maintain all the data in an audio stream and achieve substantial compression.+ +First, the vast majority of sound recordings are highly complex, recorded from the real world. As one of the key methods of compression is to find patterns and repetition, more chaotic data such as audio doesn't compress well. In a similar manner, photographs compress less efficiently with lossless methods than simpler computer-generated images do. But interestingly, even computer generated sounds can contain very complicated waveforms that present a challenge to many compression algorithms. This is due to the nature of audio waveforms, which are generally difficult to simplify without a (necessarily lossy) conversion to frequency information, as performed by the human ear.+
+The second reason is that values of audio samples change very quickly, so generic data compression algorithms don't work well for audio, and strings of consecutive bytes don't generally appear very often. However, convolution with the filter [-1 1] (that is, taking the first difference) tends to slightly whiten (decorrelate, make flat) the spectrum, thereby allowing traditional lossless compression at the encoder to do its job; integration at the decoder restores the original signal.+
+Codecs such as FLAC, Shorten and TTA use linear prediction to estimate the spectrum of the signal. At the encoder, the estimator's inverse is used to whiten the signal by removing spectral peaks while the estimator is used to reconstruct the original signal at the decoder.+
This seems to imply that even Lossless codecs make changes, but it IS a very complex subject. If I could still edit the main article I would remove that bit about AL losing information.

SOAP encoding formats and interoperability

Similar Messages

Maybe you are looking for