3) Are these files always needed when offering a web service via SOAP?
WSDL files are very useful if you want to publish your web service into some
UDDI registry.
BR,
Csilla
Has anybody developed an Applet client for a webservice using apache-soap
and xerces?? Does it work on Internet Explorer 6.0 without changing the
code for the library? (i changed the part as suggested in the mail below).
If code was modified, please let me know what changes has to be made.
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 30, 2002 12:37 PM
...
A WSDL file provides a complete technical description of your
web service. It describes
Let's not overstate things. It provides enough information to
generate proxy signatures. It doesn't
I am getting the following error when using the
client(Address Book).
The soap server is installed on iplanet.
Please help!
Ouch, the call failed:
Fault Code = SOAP-ENV:Server.Exception:
Fault String =
Hi Gary,
Let's not overstate things. It provides enough information to
generate proxy signatures. It doesn't provide complete
information for technically correct use of the web service.
WSDL does provide enough information to invoke functions of any web-service.
And the main benefit is
Please unsubscribe me
Gary,
Okay. Perhaps I am overstating things a little bit. WSDL doesn't
describe semantic information. It doesn't describe application
semantics (e.g., you must call open before action). It doesn't
describe business semantics (payment terms, service level agreements,
etc.). It doesn't
in other words, a verbose IDL :-)
Frank
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 30, 2002 1:42 PM
To: [EMAIL PROTECTED]
Subject: RE: WSDL?
Gary,
Okay. Perhaps I am overstating things a little bit. WSDL doesn't
describe semantic
I was only pointing out something that I think all programmers know,
but then tend to forget when it's their job to do it (myself
included). And that's that it's rarely easy to use an interface
properly based only on the function signatures, whether those
signatures are JavaDoc based or WSDL
Not exactly. IDL doesn't tell you how to talk to a service. IDL contains
only the type information. WSDL says you what transport protocol you have to
use, how to 'bind' SOAP to this transport protocol, etc.
Radovan
- Original Message -
From: Frank Sauer [EMAIL PROTECTED]
To: [EMAIL
Interface definition is certainly the largest chunk, but WSDL is
extensible, allowing rich descriptions to be added to the core. While the
core specification doesn't provide complete information for technically correct use
of the
web service, such information could be easily added to WSDL.
To add to what Anne is saying here
From a practical standpoint, many toolkits out there - some *very* widely
used - strictly require WSDL files for client configuration / proxy
generation, so although WSDL is not required by the SOAP protocol per se, if
you are interested in having your
There is a more basic problem here
Actually generally web-services architecture doesnt have a notion of
session
maintenance.
so calling 'open' before 'action' sort of doesnt make sense in case of
web-services.
The SOAP protocol doesn't yet have such a concept, however an application
This is probably a pretty basic question but I'm not sure I should be
implementing what the specification for the project defines...
I am creating a system where different development groups are implementing
a pre-defined SOAP service. It's possible that the service implementors
will not use
Hi,
your idea is right. You should define an interface in wsdl for your service.
Everybody who wants can download this definition and create a soap-service
with any language he wants.
Addiotionally, you can use uddi to discover the implementations and
advertise your interface. But this is a bit
The original architect specified that the objects should be passed in as
XML instead of objects to support a non-Java SOAP service implementations.
Well, one of SOAP's key features is the ability to pass around objects
(actually data structures)
in an interoperable manner.
It seems to me
Hello,
I'm trying my first steps in SOAP and Java (also .NET).
I've made a simple Hello World-app with .NET (should work as server :^) ).
The client should run in TomCat 4.0.1. As I could read in the
Apache-SOAP-docu the communication can be implemented as rpc-based or as
message-based. I've no
Look in the mailing list archives. I posted links to an example
sometime within the past 4 months. If you can't find it, see
Chapter 13 of Java XML Programming from O'Reilly, which is
all about message-style SOAP.
-Chris
[EMAIL PROTECTED] wrote:
Hello,
I'm trying my first steps in SOAP and
Shawn,
I'm not sure that I understand your terminology, but my answer assumes
that your term object inputs refers to the SOAP RPC style and XML
inputs refers to the SOAP Document style.
A SOAP service should be implementation-independent regardless of whether
you are passing XML documents
Hi there,
Has anyone out there used CapeConnect and CapeStudio by CapeClear? I'm
evaluating the software and would like to hear some comments from the user
community. We want to deploy web services (written mostly as Java classes),
for use in a Java, VB, and ASP environment. We're using:
Is this distinction necessary ? Isn't messaging a special case of RPC.
I recently moved from SOAP_2_2 to Axis. And axis doesn't seem to
differentiate the two.
Thanks for any insight.
ram
Ramanathan
We're using the JAXM package to generate SOAP Messages with code out of the
JAXM package. And I've been told one can (will be able to) use JAXM with
Axis.
Something like the following.
MessageFactory mf = MessageFactory.newInstance();
SOAPMessage msg = mf.createMessage();
SOAPPart sp =
It is undeniably the best web service implementation/solution for the needs
you have spec'd below. I have been using their CapeConnect version 2.02
since July of last year. Their support and advice regarding the web service
space has been incredibly valuable. It is worth the money of you are
Simon,
We've done some work at a large insurance firm using
both CapeStudio and CapeConnect in a WebLogic 6.1
WLE environment. Similar to your use case, we were
able to make our WL EJB's WLE IDL available for use
in a Java VB client environment using CapeStudio.
Out of the vendors that we
(I apologize for advertising on the Apache SOAP list, but Simon did ask...)
Simon,
I suggest you also look at Systinet WASP.
WASP Developer for JBuilder is free. It's a plug-in that's tightly
integrated with JBuilder. (A plug-in is also available for NetBeans and
Forte, plus there are command
25 matches
Mail list logo
