The log4j messages occur because you need to have log4j.properties or
log4j.xml in your classpath. The class
"org.w3c.dom.ranges.DocumentRange" is in the xml-apis.jar that comes
with the Xerces library - make sure you have that in your classpath also.
Tom Gordon
[EMAIL PROTECTED] wrote:
Hi,
Ananth,
The schema should be imported with "schemaLocation" not "location".
Tom Gordon
Ananth T. Sarathy wrote:
I tried that, but I keep getting errors. Is there something I am doing
wrong with these? The WSDL2Java is giving me an error that SearchText
isrefrenced not defined but it is defined in
Ananth,
The problem has to do with capitalization, not castor. The complex type
"searchParameters" in your schema has to match the capitalization of
your operation parameter (in retrieveProducts) as defined in your
server-config.wsdd. I'm not sure how you got things in this state ...
generati
27;t stick the header in there.
Thanks again,
Mike
TMG wrote:
Mike,
Without seeing the wsdl, I can only speculate as to how it was
implemented. That said, normally the first argument is the header
object with the stub, and the generated code moves it to the proper
place in the soap messag
Mike,
Without seeing the wsdl, I can only speculate as to how it was
implemented. That said, normally the first argument is the header
object with the stub, and the generated code moves it to the proper
place in the soap messages.
For example, using a stub:
MyLocatorServiceLocator locator =
Greg,
Without being able to review all the parts, my first guess is that you
have inconsistencies with your namespace. It appears you are using an
URN namespace xmlns:ns="urn:notification:voxsurf.com" in the wsdd, and
the wsdl has a URL namespace xmlns:"http://notification.voxsurf.com";.
Tom
It is my understanding that with document/literal, "message"s must be
specified using syntax, and that you
can NOT use .
Thus, the AddOrderRequest and GetOrderRequest messages need to reference
elements from the schema vs. defining types. With document/literal, you
can validate
ted me
to test it for them. I would ask that question on the xmlbeans list or
look through its archives. The included xbean jar in my sampel comes
from the Beehive http://incubator.apache.org/beehive project which
imports it as well and relies on V2 code.
cheers,
Jonathan
-----Original Message
Jonathan Colwell wrote:
I'm not familiar with xmlbeans version 1 since I have worked only with
the v2 code base. Is there a particular requirement to use 1.0.3 or are
you just using that because it is the release indicated on the xmlbeans
site?
The info on the site says v2 is unstable (which I
Jonathan,
I'm trying to use the serializer/deserializer in the war file (as
indicated below) with xmlbeans version 1.0.3 ... and I get compile
errors in XmlBeanSerializer (lines # 85, 251) and in XmlBeanDeserializer
(lines #66) because of differences in xmlbeans versions.
Specifically, the erro
Christian,
I think the type for the part name (nameParam) must refer to an element
(or complex type) defined in your schema type, not a xsd:string.
Refering to message:
Change the type to an element in the wsdlns namespace, and you shouldn't
get the error.
As
Christian,
Maybe the third time is the charm :).
Change the message to be:
I had the right words, wrong wsdl :).
Tom Gordon
TMG wrote:
Sorry,
Typo below:
As in should have PART =
TMG
TMG wrote:
Christian,
I think the type for the part name (nameParam) must refer
Sorry,
Typo below:
As in should have PART =
TMG
TMG wrote:
Christian,
I think the type for the part name (nameParam) must refer to an
element (or complex type) defined in your schema type, not a xsd:string.
Refering to message:
Change the type to an element
Michael,
The server services throw a RemoteException, that's what you "catch" in
the client. If a handler, either before or after the service is called,
throws an exception, it is usually an AxisFault.
Tom Gordon
Michael Merz wrote:
Bcc: [EMAIL PROTECTED]
I'm autogenerating my clients using the
ts see the WSDL I coded, instead of an Axis generated one.
*/TMG <[EMAIL PROTECTED]>/* wrote:
snip...
I would like to add a header to several of my services to require some
simple authorization (using CVS tree of Axis 1.2RC2).
An example of one of the service's wsdl binding is a follows:
http://schemas.xmlsoap.org/soap/http"/>
Please, before opening another JIRA bug, please test with the latest CVS
tree of RC2.
Bug #1678 had a similar symptom/problem which was fixed. There is not
enough information in this message for me to tell if the problem is
identical.
Thanks,
Tom Gordon
Davanum Srinivas wrote:
Please open a J
Nige,
UDDIs are there own topic, so I don't want to clutter this list.
To get started, take a look at:
http://www.uddi.org/
http://ws.apache.org/juddi
The Apache jUDDI project has its own mailing list, etc... if you go down
that path.
Tom Gordon
Nige White wrote:
TMG wrote:
Nige,
As a
Nige,
As an FYI ...
Another way to accomplish dynamic endpoints would be to use a UDDI (e.g.
jUDDI), and have the client locate services using a standard interface.
Tom Gordon
Nige White wrote:
[EMAIL PROTECTED] wrote:
Have you thought about SOAP headers? The first response could include
a heade
Christian,
Create a client-config.wsdd file with whatever descriptor information
you want to use, then make that file available in the classpath.
Tom Gordon
Christian Kalkhoff wrote:
Hi khs,
thank you very much. What i cannot understand is how to set this option
for an axis client. :)
Christian
A
David,
I have the same problem as you described in your e-mail to the Axis user
list, regarding schema attributes of type String (java.lang.String :) ).
Walking through the RC2 code, and comparing the code w/ 1.1, it appears
something got dropped when the modules were refactored. Meaning, it is
21 matches
Mail list logo
