Evaluation of SOAP implementations

Hi,
I'm currently evaluating SOAP to implement a web-services-type application to front a existing system. The server is certainly Java-based, but the client can be anything. I'm a complete newbie with SOAP, so please bear with the idiotic-type questions.
1. Are there still interoperability issues with SOAP implementations between Sun/Apache and Microsoft? I've read several articles on this, but they are dated at least 1-2 years ago. Any glaring issues currently?
2. The AppServer is currently on Java1.4.0. Any known issues?
3. I've tried using the jwsdp to implement a simple (and raw) SOAP service. Anyone with a recommendation whether jwsdp will suffice or would Apache Axis be a better candidate? What does Axis provides that jwsdp doesn't if i already have a http-based MVC framework that I have to re-use?
4. A more general question: Must I deploy a WSDL for my SOAP serivces?
Many thanks in advance.

Hello,
Try to roll back the time of the computer to a few days back until you are able to perform an edition upgrade.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

XMLServer problem with Strings. SOAP implementation

hi,
I've tried to export a Service Objet with XMLServer.
The SO consists of a method that will be called by a JAVA client :
execute (String param) : String
There is no problem when this method returns a String with no special caracters. But when it contains some 'e', for example, the Java client is no more able to get the response.
The error deals with the SOAP envelop of the response,
the Java client crashes :
SOAP Fault; code=SOAP-ENV:Server string=XMLSvr.ProtocolSOAP.getResponseText: Internal Error - no response envelope
I use UDS 5.0 on NT
The Java client uses Apache.SOAP packages
Is this a problem of compatibility between the two SOAP implementations ??
Please help me ...
matt

Hi Matt,
UDS 5.0.1 is able to generate a SOAP Server and Java Proxies (Java clients) but there are some limitations in the current implementation (Does not have support for array of string for example...). I would suggest you to check http://knowledgebase.iplanet.com/ikb/kb/articles/7655.html for further info abou those limitations (by the way, all the questions and answers except one, are from an email I sent to the Iplanet guys last year... :-)

SOAP Implementation missing methods

Hello,
I am developing a document based SOAP web service and I wish to add a
DOM Document to the SOAP Body. Looking at the Java 2 Platform
Enterprise Edition 1.4 specification on the Sun web site I have found
the following method "public SOAPBodyElement addDocument(Document
document)", which does exactly what I require. Although when I attempt
to call this method I get the following exception:
java.lang.AbstractMethodError:
weblogic.webservice.core.soap.SOAPBodyImpl.addDocument(Lorg/w3c/dom/Document;)Ljavax/xml/soap/SOAPBodyElement;
Has this method not been implemented in Weblogic 8.1? Any suggestions
would be very much appreciated.
Thanks, Stuart

Hi Stuart,
The addDocument(org.w3c.dom.Document) method was introduced in SAAJ 1.2. The SAAJ
implementation in WLS 8.1 is version 1.1. SAAJ 1.2 will be supported in a future
service pack or release.
For now, you can still achieve what it sounds like you want to do (i.e. send the
XML contained in an org.w3c.dom.Document to a "document-style" web service, as
the immediate child element of the <SOAP-ENV:Body> element, in the SOAP request
message), using the javax.xml.rpc.Call object. You just need to call the setProperty(Call.OPERATION_STYLE,
"document") method, on the Call object you create in your web service consumer
code. You don't have to do this with a Stub model web service consumer, because
the WSDL will (or should) have a style="document" attribute, on the <soap:binding>
element :-)
Regards,
Mike Wooten
Stuart Williamson <[email protected]> wrote:
Hello,
I am developing a document based SOAP web service and I wish to add a
DOM Document to the SOAP Body. Looking at the Java 2 Platform
Enterprise Edition 1.4 specification on the Sun web site I have found
the following method "public SOAPBodyElement addDocument(Document
document)", which does exactly what I require. Although when I attempt
to call this method I get the following exception:
java.lang.AbstractMethodError:
weblogic.webservice.core.soap.SOAPBodyImpl.addDocument(Lorg/w3c/dom/Document;)Ljavax/xml/soap/SOAPBodyElement;
Has this method not been implemented in Weblogic 8.1? Any suggestions
would be very much appreciated.
Thanks, Stuart

Problem making choice of soap implementation

hi,
I am trying to use soap to transfer data (in the form of xml documents ) between a client and server and also invoke remote procedures.
I checked out the apache implementation of soap, but i have heard that it is too slow.
could anyone suggest which implementation to use (that should suffice for my needs) and if possible attach some sample code to transfer a list of words (array of strings) between client and server.
please reply at [email protected]

You **heard** that the Apache implementation was too slow. And was it? You want us to suggest an application implementation that should suffice for your needs. I know nothing about the Apache implementation, but then I know nothing about your needs except that you want to transfer a "list of words". (10 words? A million words?) You don't have a speed requirement, so use Apache.

[URGENT] UTF-8 issue in weblogic SOAP implementation

Guyz,
I am finding an issue with **weblogic.xml.saaj.MessageFactoryImpl** SOAP message factory mplementation class of weblogic. When it creates SOAP from inputstream which includes portuguese characters it does not recognise those characters.
Any idea how to solve this issue?
Chinmoy

Will this really be a problem? UTF-8 is a superset of US-ASCII, I believe,
          so there should be no incompatability. This is assuming that you will only
          be sending latin characters in the form, since the recieving end can only
          accept latin characters. If this is NOT true, then they need to use UTF-8.
          Otherwise, I would test it and see what happens.
          "Volker Mader" <[email protected]> wrote in message
          news:3d3326c4$[email protected]..
          >
          > Hi there,
          >
          > can anybody help me.
          > I have a webapp in wls 6.1 sp2. All of the web is utf-8 based, so i set
          the charset
          > in the page-directive and the html content type to utf-8. Also I set the
          <input-charset>
          > Tag in weblogic.xml to utf-8 for context "/".
          > Problem: I want to send a from out of this webapp to another server which
          serves
          > a iso-8859-1 based application.
          > How can I do that?
          >
          > Thanks for help
          > Volker

Evaluation of XI implementation

Hi XI experts,
We have a requirement to receive EDIFACT format file from customer for Sales Order Creation.
Though there is only one message, IT head would like to build an integration system for future.
The translation from EDIFACT to IDoc in XI is quite simple, correct?
Actually from my point, I only need a converter that can convert EDIFACT to IDoc.
Then I can run standard report or write code for IDoc inbound processing.
If creation confirmation is needed, we can use standard EDI output, then translation from IDoc to EDIFACT is needed.
Is that a waste of resource to use XI in our company?
Any good suggestion for me?
Btw, could you please provide an estimated cost for XI implementation including hardware, software, installation, maintenance etc.
Thanks.
Legend.

Hi Legend,
How many EDI integrations required with SAP?, if the number of integrations very few then you can think about implementing integration without PI.
If you want use converted, then you have to invest money on that too.. What I would recommend you is write some JAVA modules to convert EDIFCAT messages in to desire out put, this can be done with some efforts(JAVA Experts can help you) then place these files in FTP, then process it, In this case you are avoiding middleware.
If your integrations more then consider about going for PI or any other middleware, but Standard SAP XI will not support conversion of EDIFACT messages in to IDoc, you have to use Conversion agent or See burger adapter, it involves more cost.
PI licensing cost depending how much data flow happened between SAP to NON-SAP and Non SAP u2013Non SAP . SAP-SAP integration free as per my knowledge.
If you want to know licensing cost and hardware better to contact SAP they will help you.
Regards,
Raj

Sample soap implementation

Hi
Has any one tried out the SOAP Sample on IAS?
I found out that there is no source code available for the SOAP sample.
(Though iplanet documentation says so..
<http://developer.iplanet.com/appserver/samples/soap/docs/helloworld.html>)
Please let me know if any one has tried out any other sample soap
application?
regards
Sushil

The source is definately available. Check out
$IAS_ROOT/ias-samples/soap/helloworld/src and
$IAS_ROOT/ias-samples/soap/cart/src.
David
@i wrote:
Hi
Has any one tried out the SOAP Sample on IAS?
I found out that there is no source code available for the SOAP sample.
(Though iplanet documentation says so..
<http://developer.iplanet.com/appserver/samples/soap/docs/helloworld.html>)
Please let me know if any one has tried out any other sample soap
application?
regards
Sushil

BEA SOAP implementation for WL5.1

Can anyone point me to a step by step guide for setting this up.
I have already read and followed the Soap.htm that is included in the
download, but I am getting nothing.
Among my apparent problems:
[ServletEntityResolver] : Could not resolve entity '-//Sun Microsystems,
Inc.//DTD Web Application 2.2//EN'. Check your
dtd reference.
[DescriptorLoader] : Could not find the WebLogic specific XML descriptor
WEB-INF/weblogic.xml. If this Web application
relies on the WebLogic specific XML descriptor, this may result in
misconfigured application.
Wed Mar 28 13:11:38 GMT+08:00 2001:<I> <ServletContext-soap-webapp>
extracting classfiles to c:\weblogic\myserver\_tmp_war:
When I try runclient.cmd I consistently get an error opening the socket
The other thing I have noticed is that the classpath in the runclient.cmd
file seems to differ to what it should probably be set too.
Any help would be most appreciated
cheers
Jay

Can anyone point me to a step by step guide for setting this up.
I have already read and followed the Soap.htm that is included in the
download, but I am getting nothing.
Among my apparent problems:
[ServletEntityResolver] : Could not resolve entity '-//Sun Microsystems,
Inc.//DTD Web Application 2.2//EN'. Check your
dtd reference.
[DescriptorLoader] : Could not find the WebLogic specific XML descriptor
WEB-INF/weblogic.xml. If this Web application
relies on the WebLogic specific XML descriptor, this may result in
misconfigured application.
Wed Mar 28 13:11:38 GMT+08:00 2001:<I> <ServletContext-soap-webapp>
extracting classfiles to c:\weblogic\myserver\_tmp_war:
When I try runclient.cmd I consistently get an error opening the socket
The other thing I have noticed is that the classpath in the runclient.cmd
file seems to differ to what it should probably be set too.
Any help would be most appreciated
cheers
Jay

SOAP in XI: message use="encoded" and binding/@style="rpc"

Hi
Hope somebody who is familiar with XIs SOAP implementation could give the answer for my questions. Problem is that the SOAP server is not working but I am afraid that the reasons are not really simple.
In our company we have to provide some SOAP services. I have entered as much as I could in IR ... including a simple scenario. Then imported the scenario to ID and the wizard created a number of agreements and determinations...
As I need to describe the service to external parties, then I used IDs Web Service definition tool to generate the WSDL.
But as the external messaging framework (for us a preprogrammed SOAP client) is fixed, I noticed that there are some differences that might matter.
XI generated WSDL where SOAP binding has
wsdl:binding/soap:binding/@style="document" but I would need it to be "rpc"
And the second thing is that in binding message bodies have attribute @use="literal" but as the messages should have several parts then it should be "encoded" (and encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
also is needed then).
Could somebody explain if these may be the reasons why the soap server does not work. And if there is a way to define soap interface so that it would have above mentioned properties as needed.
A easy question also... I would need for a method to have an empty message... inside soap body there should be just a tag with the message name and no content. But I can not figure out how to create a message type with no datatype.
Thanks for any input!

Hi, Stefan
Thanks for the answer. To clear my questions: we want to deploy XI as the SOAP server (sry I have not figured out if it is a sender or receiver channel by name - all this inbound-outbound naming in XI is quite complex). Our SOAP server/XI is actually just one part of a big SOAP network and MAFIA it uses rpc styled SOAP messages.
The note is really useful, but still it does not give any hint how to make a RPC styled SOAP interface. So the problem is still up for me. As I am not very familiar with WSDL bindings and SOAP... for the message it self, is there any difference as for the RPC vs DOCUMENT style is discussed? Is it possible that the physical structure of a SOAP envelope could be the same?
And the second question: is there a way in IR to define several parts for a message. Something like:
<message name="isiku_andmed">
<part name="paring" type="tns:isiku_andmed_paring" />
<part name="keha" type="tns:isiku_andmed_keha" />
</message>

How to install Soap on the (Apache) Oracle HTTP Server

Hi,
Does anyone know how to install SOAP on the Oracle HTTP Server? I downloaded a soap version (it seems that the standard version comes without SOAP) from the xml.apache.org site and followed the installation instructions as far as I could (only Tomcat is described). However, no 'soaping'!!! Maybe I'm overlooking something because I cannot imagine that it should be difficult.
Thanks in advance!
Hans

Hans, the SOAP implementation is part of OC4J. You get it out of the box. Check out how to use the out-of-the-box implementation in the tutorials on Web services with Oracle9i JDeveloper at:
http://otn.oracle.com/tech/webservices/htdocs/series/content.html
These tutorials/samples use the implementation of SOAP/WSDL that Oracle calls J2EE Web Services and this is the long term direction of Oracle's Web services implementation. This implementation is what Oracle will be evolving to Sun's Java Web Services Developer Pack as it finalizes into J2EE 1.4.
If you want to use Oracle/Apache SOAP, this too is included in OC4J but its support is being deprecated in future releases of Oracle9iAS in favour of the J2EE Web Services implementation. To find it, check out the OC4J/soap/webapps/ directory for the soap.ear file (it is in a slightly different spot if you are using the full Oracle9iAS R2 but still within the soap directory structure. Simply add <application name="soap" path="../../../soap/webapps/soap.ear" auto-start="true"/> to your OC4J server.xml and <web-app application="soap" name="soap" root="/soap" /> to your OC4J http-web-site.xml, re-start and away you go.
Finally, just to be sure, SOAP support in Oracle9iAS did not appear until 1.0.2.2.x and higher. If using 1.0.2.1 or less, you are correct, there is no SOAP support.
Mike.
Most folks that try out the J2EE Web Services find it is pretty easy to use so

Accessing non-weblogic SOAP

Hello,
I'm trying to access some simple web services which are implemented using
some Perl module (don't ask ....).
After I've gotten their WSDL file, I can successfully generate stubs using
the clientgen ant task.
However, when I try to access the webservice from within my EJB's, I get the
following error message:
An IOException was thrown trying to access the WSDL at the given URL.
java.io.FileNotFoundException: Response: '411: Length Required' for url:
'http://petest01:8082/cgi-bin/WebStore.cgi'
It seems as if the perl SOAP implementation doesn't allow me to check their
WSDL file. Just sending the SOAP POST messages works fine.
I explicitly specified the 'saveWSDL' option to the clientgen task, but it
still tries to access the WSDL file at runtime. Any way to resolv this
issue?
Regards,
Francois Staes.

Hi Francois,
The JAR file generated by the <clientgen> Ant task, has a static WSDL inside it.
To get your JAX-RPC client to use it, write code that looks like this:
MyService_Impl service = null;
MyServicePort port = null;
try
// There are two constructors for every XXX_Impl class.
// The one that accepts a wsdlURL (as a String) will
// request the WSDL from the service provider. The
// no-arg one will just use the statis WSDL in the
// client.jar generated by the <clientgen> Ant task.
service = new MyService_Impl();
port = service.getMyServicePort();
MyObject response = port.myServiceOperation();
Again, this will cause the WLS client-side JAX-RPC classes, in the webserviceclient.jar,
to use the static WSDL (in the client.jar generated by the <clientgen> Ant task)
to invoke the target web service. It will not send a request to the target web
service to retrieve it's WSDL, because it already has it.
Regards,
Mike Wooten
Francois Staes <[email protected]> wrote:
>
Hello,
I'm trying to access some simple web services which are implemented using
some Perl module (don't ask ....).
After I've gotten their WSDL file, I can successfully generate stubs
using
the clientgen ant task.
However, when I try to access the webservice from within my EJB's, I
get the
following error message:
An IOException was thrown trying to access the WSDL at the given URL.
java.io.FileNotFoundException: Response: '411: Length Required' for url:
'http://petest01:8082/cgi-bin/WebStore.cgi'
It seems as if the perl SOAP implementation doesn't allow me to check
their
WSDL file. Just sending the SOAP POST messages works fine.
I explicitly specified the 'saveWSDL' option to the clientgen task, but
it
still tries to access the WSDL file at runtime. Any way to resolv this
issue?
Regards,
Francois Staes.

Web Service WLS9.2 and WLS6.1 SOAP compatibility

We have a Web Service (running on WLS6.1) which has been published for a long time, and many customers have developed their own clients.
Now we must upgrade our Web Service from WLS6.1 to WLS9.2. In practice we had to re-develope the Web Service starting form the original WSDL.
The new WSDL is identical to the original one, and the business code inside has obviously been kept the same.
The new Java Test Client that we generated with clientgen (WLS92) works fine, but we need to guarantee total compatibility for all the clients developed for the 6.1 version.
Unfortunately testing our new Web Service (WLS9.2) with our old java Client (developed with WLS6.1), we found that the SOAP implementation of arrays has changed, and therefore the old client is not compatible with the new Web Services.
Is this a known issue? Is there a workaround or a solution to this problem?
== WLS6.1 array "listaPacchetti " SOAP implementation ==
<listaPacchetti xsi:type='SOAP-ENC:Array' xmlns:bean='java:smash.webservices.bean' SOAP-ENC:arrayType='bean:PacchettoBean[2]'>
<item xsi:type='bean:PacchettoBean' xmlns:bean='java:smash.webservices.bean' >
<numeroSmsResidui xsi:type='xsd:int'>2908</numeroSmsResidui>
<flagOnOffNet xsi:type='xsd:int'>1</flagOnOffNet>
<numeroSmsIniziali xsi:type='xsd:int'>4000</numeroSmsIniziali>
<idPacchetto xsi:type='xsd:string'>9693</idPacchetto>
<cessato xsi:type='xsd:int'>0</cessato>
<dataScadenza xsi:type='xsd:string'>28-02-2008</dataScadenza>
</item>
<item xsi:type='bean:PacchettoBean' xmlns:bean='java:smash.webservices.bean' >
<numeroSmsResidui xsi:type='xsd:int'>1866</numeroSmsResidui>
<flagOnOffNet xsi:type='xsd:int'>0</flagOnOffNet>
<numeroSmsIniziali xsi:type='xsd:int'>2000</numeroSmsIniziali>
<idPacchetto xsi:type='xsd:string'>9694
</idPacchetto>
<cessato xsi:type='xsd:int'>0</cessato>
<dataScadenza xsi:type='xsd:string'>28-02-2008</dataScadenza>
</item>
</listaPacchetti>== WLS9.2 array "listaPacchetti " SOAP implementation ==
<listaPacchetti>
<numeroSmsResidui>2908</numeroSmsResidui>
<flagOnOffNet>1</flagOnOffNet>
<numeroSmsIniziali>4000</numeroSmsIniziali>
<idPacchetto>9693</idPacchetto>
<cessato>0</cessato>
<dataScadenza>28-02-2008</dataScadenza>
</listaPacchetti>
<listaPacchetti>
<numeroSmsResidui>1866</numeroSmsResidui>
<flagOnOffNet>0</flagOnOffNet>
<numeroSmsIniziali>2000</numeroSmsIniziali>
<idPacchetto>9694</idPacchetto>
<cessato>0</cessato>
<dataScadenza>28-02-2008</dataScadenza>
</listaPacchetti>Any help will be appreciated!
Thank you
Laura

Hi
Thanks for your reply
I downloaded OC4J 10.1.2.0.2 and ran it as as a standalone server.
I read the blog you linked and made the changes to the web.xml for the webservice. All of which I was able to do using the property palette in jdev 10.1.2.1.0.
I deployed my webservice to my oc4j standalone server and it appeared as a new application. I editied the orion-web.xml for the new application manually.
When I point my browser at the webservice I get the test page which allows me to pass parameters to the webserive. I invoke the webservice (which does a HTTP GET according to the test page) and the webservice runs. No user and password is needed though.
What is the expected behaviour? I was hoping that the webservice wouldn't run until I supplied the admin user name and password
paul

EncodingStyle error in JWSDP 1.1 generated SOAP XML?

Hi,
I ran wscompile to generate some stubs for a simple "fortune cookie" web service. I know this service works fine because I have tested it with clients using other toolkits. So the stubs are generated, I use them to call the service and it fails. I trapped the XML being sent to the service, it is included below. An "encodingStyle" is being inserted into one of my parameter elements, but it is not being given a value so it is invalid. Can anyone tell me whether this is a bug in JWSDP or how to fix it so that this value is set correctly or is not set at all and defaults to the parent's encodingStyle?
<?xml version="1.0" encoding="UTF-8"?>..
<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="tallan.com/FortuneCookieRequest"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<env:Body>
<ns0:fortuneRequest env:encodingStyle="">
<ns0:minLines>1</ns0:minLines>
<ns0:maxLines>1</ns0:maxLines>
</ns0:fortuneRequest>
</env:Body>
</env:Envelope>..

For a SOAP response to be deserialize, com.sun.xml.rpc.encoding.SOAPDeserializationContext.verifyEncodingStyle() will be called, but SOAPDeserializationContext only pushed an empty string in the encodingStyleContext stack. It assumes the SOAP response received will tell it about encoding styles in the response; but for some SOAP implementations (such as Delphi, and maybe .NET?), this is not true.
A workaround is to open your SOAP client stub source file (generated by wscompile, you have to keep it), finding the below text:
protected void _readFirstBodyElement
Insert the following statement below it:
deserializationContext.pushEncodingStyle(SOAPConstants.NS_SOAP_ENCODING);
Then Delphi/.NET web services work happily with JWSDP generated clients.

SOAP Performance ????

Dear all,
Compared to RMI, CORBA, what is the performance of SOAP, especially when used in distributed computing?
I think the peformance would be quite low, because of the large overhead involved in XML format, and the text (instead of binary data) used to transmit data over Internet.
So if this is true, when we are using SOAP, we are actually sacrifice the performance all the way?
Any one can help explain this for me?
Thanks!

Richard,
Yes, SOAP is quite a bit slower than those other technologies.
There main reason for using SOAP is interoperability. RMI only
works between Java endpoints. SOAP implementations interoperate
with any SOAP implementation. Corba is also supposed to be this
way but interoperability is not what it should be I believe.
Another advantage of SOAP over HTTP is the ability to go through
firewalls without punching holes in it.
There is also work going on to improve SOAP performance to be nearly the same as RMI.

SOAP support in WLS6.0

I hear that SOAP support is "built in" to 6.0, but is not yet documented and
won't be documented until February. Does anyone know if this support is the
Apache implementation or something else?

FYI - quoted from the WLS 6.0 FAQ....
Does WebLogic Server 6.0 support SOAP?
WebLogic Server 6.0 does not support SOAP; however, BEA provides an
alpha-quality SOAP implementation at
http://developer.bea.com:80/techtracks/xml/index.jsp.
Alex Thomas <[email protected]> wrote in message
news:3a42444e$[email protected]..
>
Can't see anything in WL6 yet. I heard that a separate, probablyunsupported, SOAP
component would be made available. This is a non-trivial task if oneincludes UDDI,
WSDL etc etc.
cheers
alex
"Robert Cahn" <[email protected]> wrote:
I hear that SOAP support is "built in" to 6.0, but is not yet documented
and
won't be documented until February. Does anyone know if this support is
the
Apache implementation or something else?

Evaluation of SOAP implementations

Similar Messages

Maybe you are looking for