We've implemented a test RPC style web service using the following methods:
1. EJB handler with manually created deployment descriptor.
2. WSDL2Java (thus RPC provider) with auto-generated deployment descriptor.
Note that both web services implement identical operations in their
implementation cla
We've implemented a test web service using the following two methods:
1. EJB ha
I have a service similar to math in samples. I wrote a wsdd
and a client (I'm not usnig wsdl or wsdl2java).If I run the TCP monitor shows
the following messages (given bellow).
My question is :::
Is it a
wrapped service?
4.1 2.2
And the reply is:
6.3
Anne,
I understand that we can process XML payload delivered by AXIS run-time
via JAXB.
However, is it possible to make AXIS process a message (e.g., non-SOAP message)
that contains a XML payload given the .xsd schema for the payload?
E.g., given a message stream that represents a raw XML pa
Hi all,
I'm trying to write a wrapped web service without using wsdl.
I have some simple basic questions,
1. Where should I put the xml schema ? Should it be inside
wsdd or should I put a reference to it in the wsdd ?
2. I read something like this written by
Anne ;
The main reason
Hi,
I'm a bit perplexed by this one. We had a webservice running fine and the
client I built using axis wsdl2java working with it just fine, until about a
week ago. Now on the first call to the service I get a RemoteException
thrown, and a stackTrace print shows a SAXException deserializing.
T
Title: Message
I've
been spending time getting familiar with Axis deployment descriptors (wsdd
files). I've been looking through the various deploy.wsdd files that
accompany the Axis samples and I see "service" elements that have the following
"provider" attribute values:
provider="Handle
Tony,
Axis MESSAGE style tells Axis that you don't
want to use the Axis serialization engine. In this case Axis delivers the
contents of the SOAP body directly to the application as a DOM element. Your
application can process the XML as it sees fit (e.g., using JAXB).
Note that this styl
Title: WSDL2Java... Is all that REALLY necessary?
Wendy,
Yes, you can have Web services without RMI. If your
applications wants to work with raw XML, and not have Axis translate it for
you, then you should use the MsgProvider (style="message").
Although you wouldn't be using the Axis
ser
There's no doubt that the first version of the JAX-RPC API has been focused
on the RPC convention. It's an artifact of Sun's previously distorted view
that SOAP (JAX-RPC) is for RPC-style (i.e., simple, trivial work) and ebXML
(JAXM) is for messaging (real business interactions). But I think Sun ha
Sorry, I misposted the question. It's supposed to be sent to Ant group.
> -Original Message-
> From: Roman Rytov
> Sent: Sunday, August 03, 2003 13:51 PM
> To: [EMAIL PROTECTED]
> Subject: Several basic questions
>
>
> I have an XML that is HTML-encoded (< instead of < and so
> on).
I have an XML that is HTML-encoded (< instead of < and so on). This
XML is store in a property.
I need:
1. To decode it;
2. Parse and get certain values and attributes;
3. Replace in a template file some strings by the parsed data;
4. Save the replaced template.
In these targets I'm lack of the
I am calling a webservice (managed by apache-gsoap) which is returning a
bool type .
I am setting the return type on the axis side as XSD_BOOLEAN .
While parsing the response axis is throwing the following exception :
Can somebody help in identifying the problem here ..
**
13 matches
Mail list logo
