Apparently the client is sending an element GetCapabilities (with no
namespace) while the service is expecting getCapabilities.
Jeff
- Original Message -
From: Richard Holzmeier [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, February 12, 2005 2:06 PM
Subject: doc/literal service
Apparently, whatever web service was invoked has returned an unexpected type
or there is an incorrect type mapping in the client deployment descriptor.
Possibly the wrong web service was invoked, or there is some problem on the
server side.The client is expecting to end up with a
Frank,
Thanks for the article. Using saaj to construct WS requests seems better
than jumping through the various hoops that are necessary for dynamic
invocation in axis for doc/lit services, in cases where it's easy for the
client to directly construct the document that is transmitted in the
Here is a wsdl-centric way of looking at the 'wrapped' form:
If the wsdl is for a doc/lit operation, regardless of wrapping, the wire
format is fixed by the wsdl. If the request message has parts p1..n
specified by elements e1..n, the soap body must be
Body
e1.../e1
...
en.../en
Is wrapped supposed to have meaning only on the server side (where it
determines how arguments are passed to the implementation method for the
operation), or also on the client side (where it would determine whether the
document that makes up the soap body of a doc/lit operation must be
supplied,
xsd:any is not a defined type. You probably mean xsd:anyType.
- Original Message -
From: Samuel Solon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, December 15, 2004 3:08 PM
Subject: Element with type=xsd:any
I'm using WSDL to define messages that have one (or more) elements
The wsdl might contain something like this:
types
schema targetNamespace=ns elementFormDefault=qualified ...
xmlns=http://www.w3.org/2001/XMLSchema;
element name=echo2
complexType
sequence
element name=s1
If the clients can be told by some other means what URL to use to access
your service, and all know to ignore what's in the wsdl, then anything goes.
If *any* client (existing now or in future) must figure it out from the
wsdl, then the wsdl must contain a usable URL for the service, in the sense
Please read about wrapped vs. not-wrapped doc/lit web services in the Axis
user guide and wiki.
You need to define (in the wsdl) a WS that takes a single document. The
root element of that document can contain two string elements. If you use
the wrapped style in the deployment descriptor for
I recently converted an rpc/encoded operation to doc/lit and was able to
reuse the old implementation (more or less) by deploying the operation as
wrapped. This was using Axis 1.1 in Tomcat 4.1.30. Now, having upgraded
to Axis 1.2RC1, the service deploys in Tomcat, apparently successfully, but
-
From: Jeff Greif [mailto:[EMAIL PROTECTED]
Sent: 14 October 2004 09:04
To: [EMAIL PROTECTED]
Subject: Re: IncompatibleClassChangeError in Axis-1.2-RC1
I was getting exactly the same exception. The problem went
away when I made sure that the versions of axis.jar, saaj.jar,
xercesImpl.jar
the deployment spec
for the operation. What was needed was to provide a type mapping with a
different deserializer/serializer pair for anyURI.
Jeff
- Original Message -
From: Jeff Greif [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, October 13, 2004 11:46 PM
Subject: deployment form
When a wsdl operation is defined to be doc/lit, the org.apache.client.Call
setOperation() methods seem to make unexpected assumptions about the form of
the argument parameters, both in number and type. I tested this in
axis-1_2RC1 using the client program pasted below. Clearly I must be
missing
The big problem is the doctype which IIRC is only legal in the document
prolog before the root element; hence not in the Body of the soap message.
If it weren't for this, the document could be one of the arguments of an RPC
web service call, or the single element or one of its descendant elements
There is no way in WSDL or XML Schema to define the names of the array
elements used in SOAP encoding, which is underspecified.. The schema type
for soap:ArrayType specifies any element to be used for the array
elements. They are completely arbitrary. It would be OK, if very perverse,
if some
I'm using the generic web-service client style to invoke a
doc/lit web service. My code contains a section like this:
Call call = (Call)
service.createCall();
call.setTargetEndpointAddress( new java.net.URL(endpoint) );
call.setOperationStyle("document");
There are some other ideas and the general principle here:
http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/DeployedServiceTocall
Jeff
- Original Message -
From: Anand Natrajan [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September 14, 2004 7:30 AM
Subject: Re:
A speculation (I'm not an expert):
If you have
wrapper someatt=somevalue
part1.../part1
part2.../part2
/wrapper
being converted to a method call on the server:
ServiceClass.someMethod(part1, part2)
the attributes are lost. There is no way in wsdl to specify parts
Sorry, this advice is incorrect.
xsd:include is a way of building up the components in a single namespace
from separate fragment schemas. The schema specified by xsd:include
*must* have the same target namespace as the including schema (or neither
must have a target namespace). The namespace
Since nobody has answered definitively, I'll hazard a wild speculation that
not mangling might produce the name 'default' as one of the classes, fields,
methods or identifiers, which would be illegal since default is a reserved
word in java. An example of what might be generated:
class
You would crack the wsdl for the operations. Determine the types of the
parts (or the elements in doc/lit), find out if they are complex types, and
if so, register an ElementSerializer or Deserializer (depending on whether
an input or return part) for the corresponding xml type or element name.
this.
thanks,
dims
On Sat, 15 May 2004 12:23:18 -0700, Jeff Greif
[EMAIL PROTECTED] wrote:
You would crack the wsdl for the operations. Determine the types of the
parts (or the elements in doc/lit), find out if they are complex types,
and
if so, register an ElementSerializer or Deserializer
In this code snippet from org.apache.axis.message.RPCHandler, around line
260 in the axis-1.2 beta sources,
if(null != destClass dser == null
destClass.isAssignableFrom( org.w3c.dom.Element.class )){
//If a DOM element is expected, as last resort always allow
In previous versions of Axis, using attachments required javax.mail classes
and javax.activation classes. These had to be separately downloaded from
axis and came with their own licenses. They can be found either in the J2EE
distribution (from Sun) or individually. Many people use the
MessageIt appears that this is not exactly best practice, although the WSDL
1.1 spec is ambiguous and some processors for it are loose enough to allow
it.
More recently (in the deliberations over WSDL 1.2) I believe it was
established that wsdl:import may only appear as a child of
org/apache/axis/server/server-config.wsdd (in axis.jar) deploys it
Read the docs about wsdd options to find out about lifetime, etc.
Read the architecture and user guides to find out about handlers.
Jeff
- Original Message -
From: Senthil_KM
To: [EMAIL PROTECTED]
Sent: Thursday,
NachrichtThe static method
org.apache.axis.MessageContext.getCurrentContext()
returns the MessageContext of the current request. From that you can find
out just about anything (see the Axis FAQ and user guide and javadocs for
MessageContext).
Jeff
- Original Message -
From: Zedler,
Look at the documentation for org.apache.axis.client.AdminClient (which is
used to (un)deploy services). It also has a command 'list' which lists the
configuration of each service. The server side is
org.apache.axis.utils.Admin which has a static method listConfig producing
an xml document.
Jeff
You can have one java class for all complex types -- use org.w3c.dom.Element
or some simple wrapper class that might also include the xml type. You need
to set up serializer/deserializer pairs for all such combinations. The WSDL
would be read to determine these type mappings.
Jeff
-
- Original Message -
From: Jeff Greif [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, February 05, 2004 1:55 PM
Subject: Use of Message services
For obscure reasons, I am interposing a adaptor web service between a
client
and the target web service, in order to manipulate
For obscure reasons, I am interposing a adaptor web service between a client
and the target web service, in order to manipulate the SOAP envelopes sent
by the client and returned by the target service.
Presumably this could be done better using handlers, but I have to defer
that approach until it
put wsdlFile/myWsdlFile.wsdl/wsdlFile as a child of the service
element
in your deployment descriptor and put the wsdl file in axis/WEB-INF/classes/
Jeff
- Original Message -
From: Kartik [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, January 30, 2004 10:51 AM
Subject: How to tell
These comments are rather speculative and not
reflective of much expertise in this area
1. Turn on some logging (or look in the
logs that already exist) to see where the exception is thrown.
2. Most likely, to use the client code you
will need to set up a security policy that permits access
try document.getDocumentElement().normalize()
Jeff
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, December 09, 2003 6:41 AM
Subject: SOAP to DOM
In a handler (axis BasicHandler type), I need to transform the soap part
of
the message into a Document
XML Schema for SOAP messageI think there are bigger challenges. The soap
envelope schema must allow arbitrary content for the body and header
elements and sets processContents=lax for those, so the guts of a specific
SOAP message may not be validated by the SOAP processor if insufficient
- Original Message -
From: BLIS Webmaster (Patrick Houbaux) [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 28, 2003 1:21 PM
Subject: Strategy for WSDL versioning?
Hi all,
Does somebody has any good idea about the strategy to adopt for versioning
an API exposed as a
I believe that Axis is generating an incorrect soap message. A bug report
should be submitted if none exists for this problem already.
The elements sort, locale and price are not explicitly nillable in the
schema. They should be omitted from the message (as minOccurs=0 allows)
in order to
No, bar and baz need not be global elements (direct children of schema) in
order to be in the target namespace of the schema, if their 'form' infoset
property is qualified. This can be done overall for the schema, using
elementFormDefault=qualified or on individual element declarations.
The root
If you have several schemas in a wsdl file that refer to one another, the
one making the reference must import the other **in order to validate
against the schemas**. Axis definitely, and .Net likely do not validate the
soap messages because performance would suffer, and probably because there
is
Also, overloaded methods are an area where either the server or client
software are liable to do a bad job. It's my impression that if you're
operating in a tightly controlled environment where you can test the client
varieties and server code (and not expect random users to be invoking your
Actually, there seems to a spec-to-spec inconsistency. In XML Namespaces
1.0, the start characters for NcName are limited to '_' and Letter, so '.'
is not allowed. In XML Namespaces 1.1 (with Candidate Recommendation
status), they apparently are going to say that the start character for an
http://ws.apache.org/wsif
- Original Message -
From: Cory Wilkerson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, August 13, 2003 12:10 PM
Subject: wsif nightly builds
Does anyone know what the wsif stuff is in the nightly builds? WS-I
compliant build?
Just curious,
Cory
I think so, and if you just run the WSDL file through xerces with validation
turned on, it will tell you definitively.
Jeff
- Original Message -
From: Anne Thomas Manes [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, August 14, 2003 6:33 PM
Subject: Re: question regarding axis in
The correct type is xsd:boolean.
Jeff
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, August 10, 2003 6:53 AM
Subject: axis throwing a exception for bool..
Hi ,
While parsing a soap response ( response is below - from GSOAP server)
axis
is throwing
I think that when you use doc/lit operations, you must provide a each with a
distinct SoapAction in the bindings, e.g.
wsdlsoap:soapAction=http://mycompany.com/mySubtract; .
This might not be necessary if the Wrapped style is used, but better to be
safe.
Jeff
- Original Message -
From:
Could you clarify why you don't think attributes such as xsi:type should be
valid in doc/lit.
Suppose your document is described by
element foo type='bar'/
complexType name=bar abstract=true
...
/complexType
complexType name=bar1
extension base=bar
...
/extension
/complexType
...
This is an artifact from SOAP 1.1 which has caused me a lot of trouble.
Here's some information:
1. This type has two 'out-of-band' concepts outside of XML Schema.
a. the wsdl:arrayType attribute (which does not appear in the PSVI of
the schema) tells the WSDL processor that the type is an
If I understand correctly, you're not doing anything wrong. I believe Axis
is only supposed to register the existence and location of this imported
file, and to use it if it needs to. Similarly for any client code that
reads the wsdl. The human reader has to find it manually and look at it.
I think (but am not certain) the SoapAction which appears in the http
headers is crucial for doc/lit.
Jeff
- Original Message -
From: Cory Wilkerson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, July 10, 2003 11:12 AM
Subject: doc/literal method names
How could Axis possibly
It can only return an xsi:type if you give that type a name, rather than
make it anonymous.
Jeff
- Original Message -
From: Daniel Aschwanden [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, June 29, 2003 12:00 PM
Subject: xsi:type base type in simpleType/restriction
Hi,
I
The problem *may* be in the generated wsdl. The soap:body elements in the
binding introduce a new namespace
http://bmdcs2.janbe.jnj.com/PILOT_SOAP/message/
which is not the target namespace of the wsdl. On the other hand, the
abstract operation, message and part names are in the target
A pure speculation: Certain strings might be interned in a symbol table and
compared for equality by address rather than content. Restarting the web
server might create a second Axis servlet, with a new symbol table, while
some component somewhere might be holding on to the first symbol table (or
I currently have a SOAP rpc over Http web service using Axis
in Tomcat. The object (called Dispatcher) implementing the service
communicates with other back end processes.
There now needs to be a pure HTTP service (using GET with
query strings on the URL) which would ideally be handled by
You probably followed the Axis instructions and installed your own copy of
xerces jars. This doesn't work because Tomcat already has its own, and
there is a significant difference between them. Either use Tomcat's xerces
jars, or (maybe this will work) replace the ones Tomcat is using (which are
java.io.StringWriter
- Original Message -
From:
Ghershony, Arie
To: '[EMAIL PROTECTED]'
Sent: Wednesday, February 12, 2003 11:23
AM
Subject: Type
But
it doesn't recognize the class StringWriter!!
Thanks
Aria
use XMLUtils.PrettyElementToWriter
- Original Message -
From:
Ghershony, Arie
To: '[EMAIL PROTECTED]'
Sent: Wednesday, February 12, 2003 12:49
PM
Subject: Type Jeff Greif
[[EMAIL PROTECTED]]
Hi,
I
still receive an error:
clientaxis\Battle
In an old message on this list, I saw that one
could specify
service name="foo"
...
param
name="wsdlURL" value="/axis/foo.wsdl"/
to provide a wsdl file. Does the axis
web.xml need to be modified to support this, and where in webapps/ subtree of a
Tomcat installation would the file have
Sorry to reply to my own post, and sorry for asking too simple a question.
I seem to have figured this out.
Jeff
- Original Message -
From: Jeff Greif
To: [EMAIL PROTECTED]
Sent: Wednesday, January 29, 2003 12:16 PM
Subject: using a wsdl file, rather than generating via ?wsdl
In an old
Is it possible to specify in a server deployment
.wsdd(for a service provided by the axis 1.1beta webapp in Tomcat 4.1.18)
that the soap responses should not use multirefs? I know how to turn it
off in Axis clients, but not how to configure it to be off in a server.
Does the whole axis
I deployed a service, apparently without problems, but when requesting the
url?wsdl for it, there is a problem with namespaces in the WSDL generator
(as shown in the stack trace below).
Is there something that can be added to the .wsdd file to make this problem
disappear? Is there a chance that
Try
java org.apache.axis.client.AdminClient list
You might need to specify the port also, using, e.g., -p 8080
Jeff.
- Original Message -
From: Ma, Yongjie [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 21, 2003 2:18 PM
Subject: How to Override ?WSDL to generate WSDL file
Sounds like a problem with namespaces (e.g. the default namespace vs. no
namespace).
- Original Message -
From: Sean Leach [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, January 20, 2003 8:15 AM
Subject: Bug/Wierdness in reading config file after class update
Environment: Resin
In the schema for urn:test, is the element form qualified or unqualified?
If unqualified, the generated stuff is probably correct.
Look in the root of the schema for elementFormDefault=. The elements are
only namespace-qualified if this attribute is present and has the value
qualified, or if the
Hi Nirmal,
Thanks very much for this explanation. Does it also contain the essentials
of the answers to the questions in
http://marc.theaimsgroup.com/?t=10419034102r=1w=2
(subject: (de)serializers for message parts specified by elements, rather
than types)? I neglected to mention in that
In many .wsdl descriptions, element style of message part
specification is used, e.g.,
types
schema
element
name="foo"
complexType .../
/element
element
name="bar"
complexType
.../
/element
/schema
/types
message name="foobarIn"
part name="fooPart"
element="foo"/
/message
Two documents [1,2] on the wsif site refer to a
dependency on j2ee.jar. #1 claims it is optional, if you have
activation.jar and javamail.jar, and do not need EJB and JCA providers. #2
claims it is required and does not mention activation.jar and
javamail.jar. Clearly, it would be required
Put a log4j.properties file in your classpath *ahead* of axis.jar containing
something like this (the first group of lines are critical for what you're
trying to accomplish).
# Set root category priority to INFO and its only appender to CONSOLE.
#log4j.rootCategory=DEBUG, CONSOLE
It doesn't matter, except for display purposes.
Just a guess, but probably doc is produced by parsing a pretty-printed XML
text. The parser may have an option to strip ignorable whitespace (e.g.
extra spaces between attributes inside start tags, whitespace in element
content where the DTD or XML
Chapter and verse from http://www.w3.org/TR/xmlschema-1
2.2.1.2 Simple Type Definition
A simple type definition is a set of constraints on strings and information
about the values they encode, applicable to the ·normalized value· of an
attribute information item or of an element information item
The logging configuration file is in axis.jar, called log4j.properties or
something similar. If you make a copy of it, tweak it to turn on debug
logging, and put the copy ahead of axis.jar in your class path, you'll get
what you need. This information is somewhere in the Axis docs, but I can't
Based on a quick reading of the SOAP 1.2 specs, it appears that in WSDL, the
abstract message contains parts, some of which in the binding may be
designated as soap headers or attachments. Does this mean that in theory,
an Axis or WSIF client need only provide the input parts as named in the
Note: This is only a grossly speculative guess.
If you're doing this on a Windows system, particularly an older version of
Windows NT, you may have a problem with the speed of reverse DNS lookup,
arising from some aspect of the network setup. This post (occurring in a
completely different
I have a version of the WSIF DynamicInvoker client which handles complex
types in input and output. I try exactly the same WS invocation (of
Amazon's service) with the WSIFDynamicProvider flavors _ApacheAxis and
_ApacheSOAP. Things work fine with the Soap Provider against the 2002/10/14
nightly
I've hit (and worked around) a problem with a WSDL-described web service,
and cannot tell at the moment whether the problem is with the WSDL
description or with WSIF/Axis. If the latter, I'll cheerfully submit a bug
report.
I'm working with a WSIF client program derived from the DynamicInvoker
I access the same webservice (the getSummary operation of
http://live.capescience.com/wsdl/AirportWeather.wsdl ) using the
WSIFDynamicProvider for Apache SOAP provider and the WSIFDynamicProvider for
Apache Axis. The SOAP provider generates an HTTP header for SOAPAction:
SOAPAction:
75 matches
Mail list logo
