RE: AXIS Serialization / Deserialization problem with namespace prefixes

Title: Message Chris, The difference is coming from being fully qualified to the namespace and not fully qualified. In your first example, bob is assumed to be part of http:/blah, where as in your second example it is explicitly set. Depending on how your WSDL is constructed, clients will

RE: AXIS Serialization / Deserialization problem with namespace prefixes

quot;unqualified" or do not include the attribute. I recommend the former.) Anne On 5/10/06, Griffin, Mark [EMAIL PROTECTED] wrote: Chris, The difference is coming from being fully qualified to the namespace and not fully qualified. In your first example,

RE: Strange WSDL Namespace Issue

@ws.apache.orgSubject: Re: Strange WSDL Namespace Issue The WSDL appears to be valid, and clearly indicates that the element belongs to the "urn:www.pgn.wbmethod:servicerequesttypes" namespace. How did you configure the service?Anne On 4/19/06, Griffin, Mark [EMAIL PROTECTED]

Strange WSDL Namespace Issue

I have what I thought was a simple doc/literal wrapped style WSDL. I'm trying to do WSDL first design. I'm using Axis .94 to generate the server side code. That all goes okay. When a request comes in I'm getting a error which I've attached. I understand that this is a namespace issue but what

RE: wsdl2java or java2wsdl

Title: Message James, areyou talking about a specific to Axis question about why you would design your interface prior to writing the implementation or are your talking about a more general best practice when it comes to web services? I'm not sureif there is any technical advantage that

RE: wsdl2java or java2wsdl

have experienced. Are you certain these occurred because the WSDL was generated, also was this using Axis' java2wsdl or some other SOAP servers tools? James -Original Message-From: Griffin, Mark [mailto:[EMAIL PROTECTED] Sent: 24 February 2006 13:25To: axis-user

Doc/literal Wrapped

Has anyone run into issues with doc/literal wrapped using Eclipse 3.1 with the new WTP 1.0 toolset. It uses Axis which supports doc/literal wrapped but for some reason it doesn't seem to work within the tool. It works fine from the command line using Axis 1.3. Basically its not generating the

RE: Doc/literal Wrapped

should be the same. markg -Original Message- From: Griffin, Mark Sent: Tuesday, February 21, 2006 8:36 AM To: axis-user@ws.apache.org Subject: Doc/literal Wrapped Has anyone run into issues with doc/literal wrapped using Eclipse 3.1 with the new WTP 1.0 toolset. It uses Axis which

RE: Doc/literal Wrapped

: Doc/literal WrappedIn the wrapped convention, the message input element local name must be the same as the operation name (element="ns:operation-name"). It doesn't matter what you call the input message. Most people name the input message "operationRequest". Anne

RE: Doc/literal Wrapped

/literal WrappedTalk to the folks at Eclipse... On 2/21/06, Griffin, Mark [EMAIL PROTECTED] wrote: Agreed but Eclipse is notsupporting that although Axis is. Kind of strange since they are using Axis. markg -Original Message-From: Anne Thomas

RE: WSDL2Java Bug?

Anybody run into this? markg -Original Message- From: Griffin, Mark Sent: Monday, February 13, 2006 10:39 AM To: axis-user@ws.apache.org Subject: WSDL2Java Bug? I've run into an issue with Axis 1.3 using WSDL2Java. It appears to work okay when I use a wsdl file that imports an xml

WSDL2Java Bug?

I've run into an issue with Axis 1.3 using WSDL2Java. It appears to work okay when I use a wsdl file that imports an xml schema located on the local file system. When I try to use an import that references the same schema but via http, it gives the error below. The schema is accessible via

RE: wsdl2java does not generate class-files for complexTypes

Christian, Don't know if this will work for you, but I had a similar problem. Using the -W option which turned off wrapped support worked for me. I was able to then generate the classes. Not completely sure why other than something to do with the way axis is interpreting the wsdl. I thought my

RE: WSDL2Java with DocumentLiteral Issue

Follow-up, I figured this out. I need to specify the -W option since I was using doc/literal and not wrapped. Works fine now. markg -Original Message- From: Griffin, Mark Sent: Friday, November 18, 2005 1:30 PM To: 'axis-user@ws.apache.org' Subject: WSDL2Java with DocumentLiteral Issue

WSDL2Java with DocumentLiteral Issue

I working on some compatibility testing with Axis 1.3. I'm having some difficultly getting the WSDL2Java to generate the java classes based on the defined types in the WSDL. I would expect a couple of bean classes to be generated based upon the WSDL I'm using. This would be consistent with the