Re: Wrapped/Literal WSDL issue.

Well, there are errors in the originally generated WSDL-- The type definitions are defined as SOAP Encoding types (tns2 namespace) rather than XSD types (default namespace), and I suspect that .NET would barf on these types. I can't tell you why RC3 is generating the funky > values for the attribu

Re: Axis sends weird SOAP requests

It's true that, based on the WSDL definition for the getAll Products operation, Axis should send an empty body: . I would call this a bug. But, it's also true that this WSDL is not WS-I compliant becuase you have multiple operations with the same wire signature (an empty body). Systinet is able to

Re: rpc/literal vs document/literal, and returning a list of objects

And just to clarify... The difference between doc/literal and wrapped/literal is in the way you invoke the service -- the contents on the wire (the structure of the SOAP message) will be identical. In doc/literal, you input an object (javabean), and you return an object (javabean). In wrapped/lit

Re: Can't invoke method with multiple arguments

ethod(Document body); > public void method(SOAPEnvelope req, SOAPEnvelope resp); > > That seems to say to me that document/literal can have several Elements > in the body. > > I implemented a web service that accepted several Element objects. It > worked fine, except that I had

Re: calling MessageService sample with .NET client

For easiest interoperability with .NET, I suggest you use the "wrapped" style. .NET does allow you to send raw XML, but to do so you have to use a low-level API. In other words, you can't invoke the service using a WebReference. To do that you should use "wrapped" style. -Anne On Thu, 10 Feb 20

Re: Can't invoke method with multiple arguments

This is not a bug -- this is a requirement of SOAP. The child element of the SOAP body indicates to the SOAP processor how to handle the request. This child element must provide a unique signature so that the SOAP processor can figure it out. The SOAP specification doesn't specify how to process mo

Re: Error "Unable to load schema with target namespace" in XMLSpy.

The WSDL is valid. xmlspy should be able to load an inline-defined namespace. On Mon, 07 Feb 2005 14:53:57 +0100, THIBAULT Joseph <[EMAIL PROTECTED]> wrote: > And this is the generated wsdl : > > > targetNamespace="http://sr.services.accesservicessipsr"; > xmlns:impl="http://sr.services.access

Re: Next Generation Web Services presentation

Dennis, Great presentation -- Thanks! I disagree with you about UDDI, of course. UDDI is an important component for enterprise SOA management and governance. I don't see very many people using it for dynamic discovery, but many firms that have deployed a large number of services rely on UDDI to k

Re: Whois

There are 4 or 5 WhoIs services listed at www.xmethods.org. Anne On Wed, 2 Feb 2005 20:18:12 +0100 (CET), Tomek Minkowski <[EMAIL PROTECTED]> wrote: > > Hi, > I guess this is off-topic, but I guess you' re the guys that might > know the thing... > Is there an integrated

Re: Issues with .NET clients to axis service

Simon's correct: .NET supports both RPC/encoded and Document/Literal. But it does not support RPC/Literal, and that's what this WSDL is using. I suggest you convert your service to Document/Literal using the wrapped convention. Anne On Wed, 2 Feb 2005 14:39:42 -0600, Brown, Mike <[EMAIL PROTECT

Re: Problem using Axis RC2 against JBoss 4.0.1

For some reason I can't open the attached WSDL file, but there's nothing wrong with specifying xmlns="" in an unqualified element. In fact, assuming that the is an unqualified element, it's required. So I don't think this is a bug in Axis. If JBoss is rejecting the xmlns="" attribute, then it's a

Re: WS-I compliancy problem for generated wrapped WSDL

Eugene's point is that he attempted to do deploy a wrapped style service using only an implementation and a WSDD file (which Axis claim to do), but the generated WSDL document produced errors. It did, in fact generate a doc/literal "wrapped" style service (not rpc/encoded), but there are still err

Re: How to create a private UDDI registry with Axis?

UDDI.org provides a hosted v3 test registry. IBM, Microsoft, SAP, and NTT all supply replicated nodes in that registry. See http://www.uddi.org/register.html for the URLs of these registry nodes. Systinet also provides a hosted test registry. See http://www.systinet.com/uddi/web. But if your proj

Re: apachesoap namespace is not found

The namespace is valid, but there's no schema associated with it. Therefore other SOAP implementations aren't able to resolve elements or attributes from that namespace. On Wed, 19 Jan 2005 15:42:08 -0700, Steven Dahlin <[EMAIL PROTECTED]> wrote: > In using the Java2WSDL app or by handcoding I am

Re: SOAP Intermediaries

Not sure what you mean by Axis not supporting intermediaries. You can certainly route messages to and from Axis through intermediaries. Typically today, most people use a web services management (WSM) or enterprise service bus (ESB) product to implement intermediaries. These intermediary products

Re: Document/Literal : bad part name in axis server response

wo tags is necessary. Is it unnecessary overhead, or is it > something to make certain client tools happy? > > > Bill > > Anne Thomas Manes wrote: > Clarification: > Bug: In document/literal mode, Axis generate a tag > when writing out the return value; it shouldn't.

Re: wrapped/literal: complex return value

t? > > Also, does your answer implay that a scalar return value can be represented > simply like this? > > > Hello World! > > > And the WSDL would be this? > type="xsd:string"/> Bill > > > Anne Thomas Manes wrote: > If you want yo

Re: Document/Literal : bad part name in axis server response

Clarification: > Bug: In document/literal mode, Axis generate a tag when > writing out the return value; it shouldn't. That tag only makes sense in > wrapped/literal mode. (This is what Ann was saying.) Axis should generate a tag only when using RPC style. It should not generate the tag whe

Re: wrapped/literal: complex return value

If you want your return value to be a User object, then that should be your return structure, not getUserResponse. i.e., John Smith 10 Main St. The output message should be defined so: - Anne On Wed, 12 Jan 2005 18:41:24 +0900, Bill Keese <[EMAIL PROTECTED]> wrote: > I have a few ques

Re: Is lower case first letters oblicatory always in wsdl?

It shouldn't matter. What errors are you getting? On Mon, 10 Jan 2005 11:17:44 +0200, Ilkka Heinonen <[EMAIL PROTECTED]> wrote: > Hello All, > > Thank You, Anne, from your reply for last question. > http://www.newsarch.com/archive/mailinglist/axis/user/msg08622.html > > Using WSDL2Java, seems

Re: ClassCastException parsing fault with 1.2RC2

I believe that the element is invalid. The detail element is defined so: Therefore the content in the detail should be specified within a qualified child element or attribute, but not as string content within . Anne On Mon, 10 Jan 2005 15:31:07 -0500, Rich Bramante <[EMA

Re: Problem generating code with WSDL2java

You need to add an definition to the WSDD that maps the message element qname to the method name. See http://www.osmoticweb.com/axis-wsdd/operation.htm - Anne

Re: Object as parameters

See http://www.burtongroup.com/weblogs/annethomasmanes/archives/2004/04/000187.html -Anne On Thu, 6 Jan 2005 16:40:08 -, Suzy Fynes <[EMAIL PROTECTED]> wrote: > How does the "wrapped" style work? > > -Original Message- > From: Anne Thomas Manes [mailto:

Re: Axis - .Net Interop Problems

Brian, In XML Schema, in order to reference an element or type from another schema, you must first import the namespace into the schema. You need to add the following import statement to the second schema: http://valueobject.util.app.willyloman.com"/> And this import statement to the third sche

Re: Famous "Migration from Soap to Axis" problem

I can't definitively answer your basic question regarding performance, but based on anecdotal evidence, I expect you to experience a 5x or better performance improvement when switching from SOAP to Axis. The article you cited regarding Axis doc/literal and DOM refers only to the Axis "message" sty

Re: Document/Literal : bad part name in axis server response

Even though there is a work-around, this is still a bug. When using document/literal, Axis must generate a response message according to the structure defined in the schema in the WSDL. It should generate its own function return value only when using RPC style. - Anne On Fri, 07 Jan 2005 17:34:59

Re: Problem generating code with WSDL2java

Your WSDL isn't valid. You've mixed rpc and document styles, plus you have attributes in your top level input and output elements. You may not use attributes in your top-level input or output element when using either rpc or wrapped styles. You must use document style. Change your binding definitio

Re: Object as parameters

It doesn't matter. If you prefer to use parameters, use the "wrapped" style. If you prefer to use an object, use the "document" style. Anne On Wed, 5 Jan 2005 10:04:18 -, Suzy Fynes <[EMAIL PROTECTED]> wrote: > > > > > > > Hi, > > > > When creating a web service in Axis that wil

Re: Is Axis generating bad WSDL, or is .NET's wsdl.exe broken?

It's a bug. Please file a bug report. - Anne On Sat, 1 Jan 2005 11:41:40 -0500, Donnie Hale <[EMAIL PROTECTED]> wrote: > Simon, > > I appreciate the response. If you know, how do I get Axis to not insert that > prefix when it auto-generates the WSDL? Is it a bug, and should I submit a > new bug

Re: WSDL critique?

Well... You're using RPC/encoded, and you're using SOAP encoding arrays. And although these aren't Java-specific, they will cause interop problems with .NET. If you want to ensure interoperability with .NET, you should stick with WS-I compliance and use the "wrapped" style. Anne On Sun, 02 Jan

Re: WS-RM support?

Ah -- the challenge with using abbreviations... I typically associate WS-RM with WS-ReliableMessaging. The OASIS spec is called WS-Reliability. WS-Reliability is not gaining any traction among the vendors and is likely to wither away. Meanwhile, Systinet and Cape Clear have released production im

Re: java2wsdl ant task for document/literal

Just to clarify: On Wed, 22 Dec 2004 09:52:19 +0100, WAJSBERG Julien RD-BIZZ <[EMAIL PROTECTED]> wrote: > Ephemeris Lappis a écrit : > > >Despite my problems with the java2wsdl task, i have finally use a 'wrapped' > >axis wsdl to generate my client stubs for a single operation service that > >ta

Re: message style == document/literal ? (and valid signature ?)

Answers inline... On Tue, 21 Dec 2004 23:50:24 -0500, tony k <[EMAIL PROTECTED]> wrote: > Hi All, > > I'm relatively new to web services and axis, so forgive me if this is old > hat, > but i have a few questions that i was hoping the more learned may be able to > answer. > > (1) if i wanted to

Re: I'm Stucked with Axis if I use " " in my WSDL?

You need to import your second schema into your first schema in order to reference the HelloWorld element. Like so: http://ce.vtt.fi/HelloWorld/HelloWorld.wsdl"; xmlns="http://www.w3.org/2001/XMLSchema";> http://ce.vtt.fi/HelloWorld/HelloWorld.xsd"/> Regards, Anne

Re: WSDL2Java & import

You must use to import a schema, not . something like this: ... ... Then you must reference elements from the schema using their fully qualified element names (bar:...) Anne On Tue, 28 Dec 2004 20:10:52 +0100, laura baño <[EMAIL PROTECTED]> wrote: > Hello ever

Re: Problem with Namespace in request envelope

Can you supply us with the WSDL file? The SOAP Body element (the message name -- in your case "GetAddressFor AddressID") is required to be a qualified element. In an rpc-style message, the namespace qualifier must be defined in the namespace attribute in the definition in the WSDL binding. In a

Re: Problem with {User defined type} having array of {User defined type} with RPC-Literal

Note that Axis doesn't really support RPC/Literal. It kinda supports it from a client perspective, but there's no Axis WSDD "style" attribute value that corresponds to RPC/Literal. I suggest you use Wrapped Document/Literal instead. (Note that .NET does not support RPC/Literal, either.) Anne On

Re: wsdl2java does not understand the 'soapAction' attribute in /definitions/portType/operation

There's no need to do this. In an rpc/encoded WSDL, the message part must reference a type, not an element. It's perfectly legal to reference an xsd type. So the original WSDL description is fine: The error was caused by the erroneously placed soapAction attri

Re: wsdl2java does not understand the 'soapAction' attribute in /definitions/portType/operation

Christian, There is a problem with your WSDL. You have a soapAction attribute specified on the wsdl:portType/wsdl:operation element, which is not permitted: http://localhost:8090/action/HelloWorld.Execute"; parameterOrder="nameParam"> The soapAction attribute b

Re: Java Client accessing a .NET Web Service

WS-I Basic Profile prohibits use of SOAP encoding, but rpc/literal style is permitted. Unfortunately, .NET does not support rpc/literal, therefore I suggest you stick with document/literal or wrapped document/literal only. Anne On Fri, 17 Dec 2004 12:00:31 +0100, HG <[EMAIL PROTECTED]> wrote: > H

Re: Java Client accessing a .NET Web Service

Regarding the IBM presentation referenced at http://www.dsg.cs.tcd.ie/~dowlingj/ teaching/ds/tutorials/AxisVeryAdvanced.pdf Although I concur with the design best practices recommendations he makes on page 2, there are a number of errors in the presentation. For example, his example SOAP message

RE: Serialization Compatibility

Bad idea. Always avoid collections. Use an array instead. -Original Message- From: jay limfueco [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 15, 2004 2:52 AM To: [EMAIL PROTECTED] Subject: Serialization Compatibility Hi, I'm currently working on a web service that should support

RE: Serialization Compatibility

Bad idea. Always avoid collections. Use an array instead. -Original Message- From: jay limfueco [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 15, 2004 2:52 AM To: [EMAIL PROTECTED] Subject: Serialization Compatibility Hi, I'm currently working on a web service that should support

RE: Remote reference!

ate remote references. Anne -Original Message- From: Paul Libbrecht [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 15, 2004 3:45 AM To: [EMAIL PROTECTED] Subject: Re: Remote reference! Le 15 déc. 04, à 00:53, Anne Thomas Manes a écrit : > SOAP doesn't support remote referenc

RE: Remote reference!

ate remote references. Anne -Original Message- From: Paul Libbrecht [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 15, 2004 3:45 AM To: [EMAIL PROTECTED] Subject: Re: Remote reference! Le 15 déc. 04, à 00:53, Anne Thomas Manes a écrit : > SOAP doesn't support remote referenc

RE: Remote reference!

SOAP doesn't support remote references. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 14, 2004 7:38 AM To: Axis User mail list Subject: Remote reference! Hi all! How are remote references to a web service implement in axis at client side? T

RE: Remote reference!

SOAP doesn't support remote references. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 14, 2004 7:38 AM To: Axis User mail list Subject: Remote reference! Hi all! How are remote references to a web service implement in axis at client side? T

RE: Newbie Axis / Dotnet ArrayofString problem

This is a known soap encoding interoperability problem between .NET and Axis. In my opinion, Axis interprets the SOAP specification correctly by using soapenc:string rather than xsd:string, but .NET doesn't know how to interpret soapenc:string. For better interoperability, you should use documen

RE: Newbie Axis / Dotnet ArrayofString problem

This is a known soap encoding interoperability problem between .NET and Axis. In my opinion, Axis interprets the SOAP specification correctly by using soapenc:string rather than xsd:string, but .NET doesn't know how to interpret soapenc:string. For better interoperability, you should use documen

RE: Help needed in invoking a doc/lit web service.

When defining a document/literal style service, your input message must contain at most one body part. You cannot list each of your input elements as separate parts in the input message definition. You must define a wrapper element for your two input parameters and reference this one element in you

RE: Help needed in invoking a doc/lit web service.

When defining a document/literal style service, your input message must contain at most one body part. You cannot list each of your input elements as separate parts in the input message definition. You must define a wrapper element for your two input parameters and reference this one element in you

RE: Best Practice

our code in a relatively easy manner without the need of creating a WSDL first which is perfect. Anne Thomas Manes wrote: > I'm thinking about reusability. > > Picture yourself a couple of years from now when your company has a few > thousand services deployed. Like most compani

RE: Best Practice

our code in a relatively easy manner without the need of creating a WSDL first which is perfect. Anne Thomas Manes wrote: > I'm thinking about reusability. > > Picture yourself a couple of years from now when your company has a few > thousand services deployed. Like most compani

RE: Best Practice

WSDL the server and clients use. Perhaps my approach is heresy. If it is, I'd like to know how my concerns can be countered. Thanks! Anand On Tue, 16 Nov 2004, Anne Thomas Manes wrote: : Technically, an "import" is importing a namespace, not the schema or WSDL : file that creates th

RE: Best Practice

WSDL the server and clients use. Perhaps my approach is heresy. If it is, I'd like to know how my concerns can be countered. Thanks! Anand On Tue, 16 Nov 2004, Anne Thomas Manes wrote: : Technically, an "import" is importing a namespace, not the schema or WSDL : file that creates th

RE: Best Practice

Basic Profile suggests according to schema imports and wsdl imports in respect to namespaces.?   /Henrik   - Original Message - From: Anne Thomas Manes To: [EMAIL PROTECTED] Sent: Tuesday, November 16, 2004 2:45 PM Subject: RE: Best Practice

RE: Best Practice

Basic Profile suggests according to schema imports and wsdl imports in respect to namespaces.?   /Henrik   - Original Message - From: Anne Thomas Manes To: [EMAIL PROTECTED] Sent: Tuesday, November 16, 2004 2:45 PM Subject: RE: Best Practice

RE: Best Practice

I was a little confused by your import structure – I wouldn’t expect to use at all. My suggestion is as follows:   Define standalone element schema (what you call type-schema).   Define standalone input/output message schema (what you call message-schema).  

RE: Best Practice

I was a little confused by your import structure – I wouldn’t expect to use at all. My suggestion is as follows:   Define standalone element schema (what you call type-schema).   Define standalone input/output message schema (what you call message-schema).  

RE: Best Practice

Typically I prefer not to use a bunch of different schemas with a service (e.g., one schema for each element and type). In order to reference an element (or type) from one schema (a) in another schema (b), you must explicitly import the (a) schema (and define a namespace declaration) into t

RE: Best Practice

Typically I prefer not to use a bunch of different schemas with a service (e.g., one schema for each element and type). In order to reference an element (or type) from one schema (a) in another schema (b), you must explicitly import the (a) schema (and define a namespace declaration) into t

RE: Help! String xs:attributes not supported? (java.lang.reflect.InvocationTargetException)

In Java, "string" is a simple type; "String" is not. The question is why did Axis map your CurrencySymbolT type to "String" rather than "string", and since it did so, why does the code expect a simple type. Since this is all generated code, I'd say this is a bug. Please file a bug report. As a wor

RE: Help! String xs:attributes not supported? (java.lang.reflect.InvocationTargetException)

In Java, "string" is a simple type; "String" is not. The question is why did Axis map your CurrencySymbolT type to "String" rather than "string", and since it did so, why does the code expect a simple type. Since this is all generated code, I'd say this is a bug. Please file a bug report. As a wor

RE: soap body request missing operator in document/literal style

Marcos, A document/literal message should contain at most one body message part. You have defined three. You need to define a wrapper element for your three body elements. For better interoperability, I suggest you use the "wrapped" style. Give the wrapper element the same name as your operation,

RE: soap body request missing operator in document/literal style

Marcos, A document/literal message should contain at most one body message part. You have defined three. You need to define a wrapper element for your three body elements. For better interoperability, I suggest you use the "wrapped" style. Give the wrapper element the same name as your operation,

RE: Maximum Interoperability with "Map" objects

data, or using a custom serializer/deserializer, or using data binding in combination with Axis. I don't think it's good to design your web services interfaces around the limitations of the current platform, though (especially since the platforms are all becoming more capable as time goe

RE: Maximum Interoperability with "Map" objects

data, or using a custom serializer/deserializer, or using data binding in combination with Axis. I don't think it's good to design your web services interfaces around the limitations of the current platform, though (especially since the platforms are all becoming more capable as time goe

RE: how datatpes are mapped in xml schema syntax

The JAX-RPC specification [1] defines standard mappings of Java types to XML types. Current products (including Axis) support JAX-RPC 1.1. [1] http://java.sun.com/xml/downloads/jaxrpc.html - Anne -Original Message- From: Martin Hamel [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 0

RE: how datatpes are mapped in xml schema syntax

The JAX-RPC specification [1] defines standard mappings of Java types to XML types. Current products (including Axis) support JAX-RPC 1.1. [1] http://java.sun.com/xml/downloads/jaxrpc.html - Anne -Original Message- From: Martin Hamel [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 0

RE: Maximum Interoperability with "Map" objects

Mark, Designing a WSDL contract refers to the process of designing your SOAP interface based on the XML messages you intend to exchange (defined using XML Schema) rather than based on the Java interface of your service agent. The XML Schema type system doesn't support Hashtables, Maps, Lists, et

RE: Maximum Interoperability with "Map" objects

Mark, Designing a WSDL contract refers to the process of designing your SOAP interface based on the XML messages you intend to exchange (defined using XML Schema) rather than based on the Java interface of your service agent. The XML Schema type system doesn't support Hashtables, Maps, Lists, et

RE: WSDL2Java does not generate custom exception

t I try to experiment and debug or ask advice on this mailing list to see if somebody else has solved this or a similar issue. Regards Steve Quoting Anne Thomas Manes <[EMAIL PROTECTED]>: > Steve, > > I'm quoting the specs. Per the specs, faults must be defined as > doc

RE: wsdd schema

I’ve never seen the schema, but here’s a great reference: http://www.osmoticweb.com/axis-wsdd/   From: Samir Shaikh [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 27, 2004 3:57 PM To: [EMAIL PROTECTED] Subject: wsdd schema   Hi,   Does anyone know where I can

RE: DocumentBuilder could not parse it? Why?

Title: DocumentBuilder could not parse it? Why? Certain parsers barf on the xmlns:xml namespace declaration (even though it’s valid).   From: Muthusamy, Elavarasan [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 27, 2004 4:07 PM To: [EMAIL PROTECTED] Subject: DocumentBuilder c

RE: WSDL2Java does not generate custom exception

ld be found. To get over this just edit the WSDL before generating the java code to change the QNames to be unique within an operation. All then works fine. If you already have an impl class generated from an earlier run you will need to either rename it or remove it. Regards Steve Quoting An

RE: WSDL2Java does not generate custom exception

Note, though, that fault messages MUST be defined as document/literal rather than rpc/encoded, per the WSDL 1.1 specification [1]: 3.6 soap:fault The soap:fault element specifies the contents of the contents of the SOAP Fault Details element. It is patterned after the soap:body element (see sect

RE: How do I safely evolve data structures?

A lot of it depends on the semantics of the interface. How relevant is this removed attribute to the existing client applications? Can you generate a default value for the attribute for these existing clients and still have it work? One of the easiest ways to make this work is to intercept incomin

RE: How do I safely evolve data structures?

A lot of it depends on the semantics of the interface. How relevant is this removed attribute to the existing client applications? Can you generate a default value for the attribute for these existing clients and still have it work? One of the easiest ways to make this work is to intercept incomin

RE: Looking for XSD for http://xml.apache.org/axis/

Axis 1.1 returns axis:Server.userException where it should return soapenv:Client. Because these fault codes are defined in a separate namespace, technically, this isn't a bug. But a developer should have the choice to return the standard soapenv fault codes. This issue has been fixed in Axis 1.2.

RE: Looking for XSD for http://xml.apache.org/axis/

Axis 1.1 returns axis:Server.userException where it should return soapenv:Client. Because these fault codes are defined in a separate namespace, technically, this isn't a bug. But a developer should have the choice to return the standard soapenv fault codes. This issue has been fixed in Axis 1.2.

RE: SAXException trying to deserialize this fault

There are two problems with this fault message: 1- The element must be the first and only child element in the element. It cannot be a child of the element. If you want to return the information in the fault, it must be encoded within the element. 2- Content in the message must be namespace q

RE: SAXException trying to deserialize this fault

There are two problems with this fault message: 1- The element must be the first and only child element in the element. It cannot be a child of the element. If you want to return the information in the fault, it must be encoded within the element. 2- Content in the message must be namespace q

RE: WSDL2Java and Basic Profile

Please file a bug report. Thanks! -Original Message- From: Dan Ciarniello [mailto:[EMAIL PROTECTED] Sent: Thursday, October 14, 2004 2:56 PM To: [EMAIL PROTECTED] Subject: Re: WSDL2Java and Basic Profile Anne Thomas Manes wrote: >Dan, > >The child elements (, , and ) are d

RE: WSDL2Java and Basic Profile

Please file a bug report. Thanks! -Original Message- From: Dan Ciarniello [mailto:[EMAIL PROTECTED] Sent: Thursday, October 14, 2004 2:56 PM To: [EMAIL PROTECTED] Subject: Re: WSDL2Java and Basic Profile Anne Thomas Manes wrote: >Dan, > >The child elements (, , and ) are d

RE: Weird error message when using WSDL2JAVA generated classes

I suspect that the service is expecting a wrapper element called DocumentGetCollection rather than DocumentGetCollectionRequest, although that's not what the WSDL indicates. Can you ask the service developer to supply you with the WSDD of the service and a sample SOAP request message from C# that

RE: Weird error message when using WSDL2JAVA generated classes

I suspect that the service is expecting a wrapper element called DocumentGetCollection rather than DocumentGetCollectionRequest, although that's not what the WSDL indicates. Can you ask the service developer to supply you with the WSDD of the service and a sample SOAP request message from C# that

RE: Array Objects

Please explain what you mean in more detail. With Axis/SOAP you send and receive messages --- but you can’t “call” an array of objects. You can send an array of objects to a service, and you can receive an array of objects from a service. What would you like to do?   Anne   From

RE: Array Objects

Please explain what you mean in more detail. With Axis/SOAP you send and receive messages --- but you can’t “call” an array of objects. You can send an array of objects to a service, and you can receive an array of objects from a service. What would you like to do?   Anne   From

RE: axis IPv6 support?

Axis doesn't work directly with IP, so it's unaware of whether you're using IPv4 or IPv6. So whether or not it supports IPv6 depends on the environment that you've deployed Axis in (servlet engine, JVM, etc.) - Anne -Original Message- From: William Fitzgerald [mailto:[EMAIL PROTECTED] Se

RE: axis IPv6 support?

Axis doesn't work directly with IP, so it's unaware of whether you're using IPv4 or IPv6. So whether or not it supports IPv6 depends on the environment that you've deployed Axis in (servlet engine, JVM, etc.) - Anne -Original Message- From: William Fitzgerald [mailto:[EMAIL PROTECTED] Se

RE: WSDL2Java and Basic Profile

Dan, The child elements (, , and ) are defined as local elements (defined inside a complex type), and therefore must be unqualified. Therefore the elements must include the "no default" namespace definitions (xmlns=""). If you prefer to make these element qualified, you can add the elementFormDefa

RE: WSDD configuration problems

k!) You suggested to switch from rpc/encoded to document/literal. What would I have to do for that (in terms of configuration) and what impact would that change have on my service implementation?? Thanks Florian -Ursprüngliche Nachricht- Von: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Ges

RE: beanMapping in WSDD

You can have more than one tag in a WSDD. You cannot specify more than one bean class in the same tag.   Anne   From: Suzy Fynes [mailto:[EMAIL PROTECTED] Sent: Thursday, October 14, 2004 10:48 AM To: [EMAIL PROTECTED] Subject: beanMapping in WSDD     Hi,   Can there be

RE: namespaces

Each qname maps to only one class, so you must define a different beanMapping for each bean class. Anne -Original Message- From: Suzy Fynes [mailto:[EMAIL PROTECTED] Sent: Thursday, October 14, 2004 3:07 PM To: [EMAIL PROTECTED] Cc: 'Anne Thomas Manes' Subject: RE: namespace

RE: namespaces

A qname (qualified name) is a name that consists of a namespace prefix (the characters before the colon) and a local name (the characters after the colon). For example, in the qname "wsdl:portType", "wsdl" is the namespace prefix, and "portType" is the local name. A namespace prefix is an abbreviat

RE: [*** Mogelijke SPAM ***] - RE: newbie: namespace error - Enco ded IP

Because your schema specifies elementFormDefault="qualified", then all local elements (including 2 and manager must be qualified with the "urn:tempura-org:RISC" namespace. Child elements do not "inherit" the parent's namespace unless the parent defines a default namespace (a namespace declaration w

FYI: I sent a note to WS-I regarding the bug in the 1.1 profile

-Original Message- From: Christopher B Ferris [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 13, 2004 1:57 PM To: Anne Thomas Manes Subject: Re: FW: Error in the Basic Profile Thanks Anne! I've forwarded to the bpwg list and we'll add it to the errata. Cheers, Christop

RE: WSDD configuration problems

One problem with your WSDL is that two of the elements in your Con type reference a type (impl:ArrayOf_soapenc_string) that hasn't been defined: As a result, any operation that exchanges the Con type or the ArrayOfCon type won't work. You need to add a type definition for this type. (or add a

RE: WSDL2Java and Basic Profile

Interesting. I think you found a bug in the WS-I Basic Profile. According to the WSDL 1.1 specification [1] and the latest version of the WSDL 1.1 XML Schema [2], the definitions/binding/operation/input element does not include the @message attribute. Therefore the sample in the WS-I Basic Profile

RE: operation wrapper in soap message

Johannes, In the wrapped style, the name of your input message element must be the same as your operation name. If the operation name is CONVERTDATA_IPC_PVA, then your input message element should also be called CONVERTDATA_IPC_PVA. Alternatively, if your input message element is called CONVReque

  1   2   3   4   5   6   7   8   9   >