Normally, with Apache SOAP you would write a Java class into which the rowset,
defined as a sequence of rows, can be de-serialized. The case below would be a
bit trickier, since the return parameter XML includes the schema, so I doubt
Apache SOAP would successfully parse it, but perhaps Axis coul
Your attempt to send XML as a string parameter will not work. The XML in the
string will be "escaped", e.g. the '<' will be converted to '<'.
A simple way to get the correct format is to create Java beans for the parameter
data and map the class to the BeanSerializer. For example,
class TRestr
Hi,
I noticed that HP-SOAP fails all the interop
tests with Apache SOAP2.2+:
http://www.apache.org/~rubys/ApacheClientInterop.html
We compare the wire messages, but still cannot
figure out what cause the problems that we pass
all axis tests but fail ApacheSOAP tests.
We will appriciate it if yo
Hi,
I'm having a problem invoking a service deployed in apache server with
tomcat 3.3 using GLUE 2-2 client.
The service name is notify(DirNotificationData data) where
DirNotificationData is a user defined object.
This service worked fine when using an apache soap client.
Here is the request s
Lior,
What is the nature of the error, e.g., are you getting a SOAP Fault? If so, can
you post the text of the fault?
Scott
- Original Message -
From: "Lior Weintraub" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 09, 2002 11:44 AM
Subject: glue client apache server
Hello Scott,
Thanks for answering so fast.
The soap fault is :
No Deserializer found to deserialize a
'http://www.themindelectric.com/package/emblaze/:DirNotificationData' using
encoding style 'http://schemas.xmlsoap.org/soap/encoding/
This is the SOAP Fault as received :
Lior,
The issue is probably the namespace associated with DirNotificationData. GLUE
is using http://www.themindelectric.com/package/emblaze/ . Having not used
GLUE, I do not know how you might change this. However, it is possible to
change your Apache SOAP service to accept this by simply addi
Hi all,
I've tried to create an infrastructure to allow to
automatically configure the SSL communication with SOAP. My problem is
that the creation of the keystores and certificates using
keytool is not possible with different versions of JDK
(keytool).
For example, I'm using JDK 1.3.0 on
I am not Sam, but I ran the interop test from my box using both SOAP 2.2 and
SOAP 2.2+, the latter being last night's build. From what passes over the wire
for the string test (as captured by TcpTunnelGui, see below), things look fine
to me. The only difference in the response is the use of the
I've poked around the code with no definitive answer, but I am suspicious of
something. It appears all other servers are specifying
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; somewhere in
the response. I am wondering whether the ability of Apache SOAP to handle the
"defa
I believe I have located a bug in the current Apache SOAP source that prevents
the default encoding from being correctly applied.
The SOAPMappingRegistry class, a subclass of XMLJavaMappingRegistry, now support
chaining, i.e. an instance has a parent, with the parent being null for the
"root" ins
Committers:
I believe I have located a bug in the current Apache SOAP source that prevents
the default encoding from being correctly applied.
The SOAPMappingRegistry class, a subclass of XMLJavaMappingRegistry, now support
chaining, i.e. an instance has a parent, with the parent being null for t
Hi Scott,
I tried as u suggested.
But now, it is not generating the expected request XML. It's omitting the
child tags of "Restrictions" and "Properties" tags.
Do u think it has got something to do with QName(nameSpaceURI, localPart)?
Following is my java code (as suggested by u)...
//
Sorry, my original message may not have been clear on this, but you must also
map TRestrictionList and TPropertyList to the BeanSerializer. Basically, any
class you want to serialize must be mapped. The only built-in mapping are for
Java primitives (e.g. int), wrappers (e.g. Integer) and a few o
Hi Scott,
Thank you so much for u'r fact response. Sorry to bother u again and again.
I mapped TRestrictionList and TPropertyList to BeanSerializer.
I also added the get/set methods to these classes.
when i call invoke, i'm getting the following exception (now the request is
not at all submitte
There are two ways (I think) to overcome this:
1. Use public fields instead of get/set methods, which allows you to capitalize
the first character.
2. Use a BeanInfo (I think).
I chose #1 intentionally, since it requires less typing ;).
Scott
- Original Message -
From: "Yalavarthi, Vas
16 matches
Mail list logo