RE: Doc/literal Wrapped

2006-02-21 Thread Griffin, Mark
A follow-up to this.  Changing the Operation name to something other
than the Input message name fixes the problem of the beans not being
generated in Eclipse. I don't think this is the way it should work. My
understanding of Doc/literal wrapped is that the operation name and the
input message 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 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 beans for the input and output messages.  I posted this
over in the WTP discussion group but no response.  Just curious if
anyone else has seen it.  I attached the WSDL I using to test. Thanks.



 service.wsdl 
markg

Mark E. Griffin
Developer Services
Progress Energy
[EMAIL PROTECTED]




Re: Doc/literal Wrapped

2006-02-21 Thread Anne Thomas Manes
In 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.
AnneOn 2/21/06, Griffin, Mark [EMAIL PROTECTED] wrote:
A follow-up to this.Changing the Operation name to something otherthan the Input message name fixes the problem of the beans not beinggenerated in Eclipse. I don't think this is the way it should work. Myunderstanding of Doc/literal wrapped is that the operation name and the
input message should be the same.markg-Original Message-From: Griffin, MarkSent: Tuesday, February 21, 2006 8:36 AMTo: axis-user@ws.apache.org
Subject: Doc/literal WrappedHas anyone run into issues with doc/literal wrapped using Eclipse 3.1with the new WTP 1.0 toolset.It uses Axis which supports doc/literalwrapped 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 notgenerating the beans for the input and output messages.I posted thisover in the WTP discussion group but no response.Just curious ifanyone else has seen it.I attached the WSDL I using to test. Thanks.
 service.wsdlmarkgMark E. GriffinDeveloper ServicesProgress Energy[EMAIL PROTECTED]



RE: Doc/literal Wrapped

2006-02-21 Thread Griffin, Mark
Title: Message



Agreed 
but Eclipse is notsupporting that although Axis is. Kind of strange since 
they are using Axis.

markg

  
  -Original Message-From: Anne Thomas 
  Manes [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 21, 2006 
  6:59 PMTo: axis-user@ws.apache.orgSubject: Re: 
  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
  On 2/21/06, Griffin, 
  Mark [EMAIL PROTECTED] 
  wrote:
  A 
follow-up to this.Changing the Operation name to something 
otherthan the Input message name fixes the problem of the beans not 
beinggenerated in Eclipse. I don't think this is the way it should work. 
Myunderstanding of Doc/literal wrapped is that the operation name and 
the input message should be the same.markg-Original 
Message-From: Griffin, MarkSent: Tuesday, February 21, 2006 8:36 
AMTo: axis-user@ws.apache.org 
Subject: Doc/literal WrappedHas anyone run into issues 
with doc/literal wrapped using Eclipse 3.1with the new WTP 1.0 
toolset.It uses Axis which supports doc/literalwrapped 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 
notgenerating the beans for the input and output messages.I 
posted thisover in the WTP discussion group but no 
response.Just curious ifanyone else has seen 
it.I attached the WSDL I using to test. Thanks. 
service.wsdlmarkgMark E. 
GriffinDeveloper ServicesProgress Energy[EMAIL PROTECTED]


service.wsdl
Description: service.wsdl


Re: Doc/literal Wrapped

2006-02-21 Thread Anne Thomas Manes
Talk 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 
  Manes [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 21, 2006 
  6:59 PMTo: axis-user@ws.apache.org
Subject: Re: 
  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
  On 2/21/06, Griffin, 
  Mark [EMAIL PROTECTED] 
  wrote:
  A 
follow-up to this.Changing the Operation name to something 
otherthan the Input message name fixes the problem of the beans not 
beinggenerated in Eclipse. I don't think this is the way it should work. 
Myunderstanding of Doc/literal wrapped is that the operation name and 
the input message should be the same.markg-Original 
Message-From: Griffin, MarkSent: Tuesday, February 21, 2006 8:36 
AMTo: axis-user@ws.apache.org 
Subject: Doc/literal WrappedHas anyone run into issues 
with doc/literal wrapped using Eclipse 3.1with the new WTP 1.0 
toolset.It uses Axis which supports doc/literalwrapped 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 
notgenerating the beans for the input and output messages.I 
posted thisover in the WTP discussion group but no 
response.Just curious ifanyone else has seen 
it.I attached the WSDL I using to test. Thanks. 
service.wsdlmarkgMark E. 
GriffinDeveloper ServicesProgress Energy[EMAIL PROTECTED]





RE: Doc/literal Wrapped

2006-02-21 Thread Griffin, Mark
Title: Message



Yep 
i'm trying, just thought i would give the axis folks a try. more responsive. 
:) Thanks.

markg

  
  -Original Message-From: Anne Thomas 
  Manes [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 21, 2006 
  7:14 PMTo: axis-user@ws.apache.orgSubject: Re: 
  Doc/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 Manes 
  [mailto:[EMAIL PROTECTED]] 
  Sent: Tuesday, February 21, 2006 6:59 PMTo: axis-user@ws.apache.org
  Subject: Re: Doc/literal 
  Wrapped
  In 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
  On 2/21/06, Griffin, Mark [EMAIL PROTECTED] wrote: 
  A 
follow-up to this.Changing the Operation name to something 
otherthan the Input message name fixes the problem of the beans not 
beinggenerated in Eclipse. I don't think this is the way it should 
work. Myunderstanding of Doc/literal wrapped is that the operation 
name and the input message should be the 
same.markg-Original Message-From: Griffin, 
MarkSent: Tuesday, February 21, 2006 8:36 AMTo: axis-user@ws.apache.org Subject: Doc/literal 
WrappedHas anyone run into issues with doc/literal wrapped 
using Eclipse 3.1with the new WTP 1.0 toolset.It uses 
Axis which supports doc/literalwrapped 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 notgenerating the 
beans for the input and output messages.I posted 
thisover in the WTP discussion group but no 
response.Just curious ifanyone else has seen 
it.I attached the WSDL I using to test. Thanks. 
service.wsdlmarkgMark E. 
GriffinDeveloper ServicesProgress Energy[EMAIL PROTECTED]