axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Davanum Srinivas <d...@yahoo.com>
Subject RE: WS-Adressing issue
Date Thu, 01 Apr 2004 15:41:56 GMT
Tom,

Plz throw the code. I'll run the tests.

-- dims

--- Tom Jordahl <tomj@macromedia.com> wrote:
> 
> So I have (1) going now.  Still having trouble with all-tests (before my
> changes even) so I may have to throw the code over the wall.
> 
> I'll work on (2) right now.  Shouldn't be too bad.
> 
> --
> Tom Jordahl
> Macromedia Server Development
> 
> -----Original Message-----
> From: Glen Daniels [mailto:glen@thoughtcraft.com] 
> Sent: Thursday, April 01, 2004 10:32 AM
> To: axis-dev@ws.apache.org
> Subject: Re: WS-Adressing issue
> 
> Tom:
> 
> This should do two things - 1) allow specification of individual SOAP
> actions in the <operation> in WSDD, and 2) allow a service option in WSDD to
> do the same things as the command-line Java2WSDL option, i.e. end up calling
> emitter.setSOAPAction("OPERATION").  Even just doing the 2nd one for now
> would be fine.
> 
> Also, the code in fromJava.Emitter should really be generating a URI for the
> soapAction value, not just using the operation name directly....
> 
> Thanks,
> --Glen
> 
> ----- Original Message ----- 
> From: "Tom Jordahl" <tomj@macromedia.com>
> To: <axis-dev@ws.apache.org>; "'Richard Martin'" <rmarti@essex.ac.uk>
> Sent: Thursday, April 01, 2004 10:25 AM
> Subject: RE: WS-Adressing issue
> 
> 
> >
> > The pieces are all there for the operation description in WSDD to provide
> > the SOAPAction.
> >
> > I should have something checked in today....
> >
> >
> > --
> > Tom Jordahl
> > Macromedia Server Development
> >
> > -----Original Message-----
> > From: Davanum Srinivas [mailto:dims@yahoo.com]
> > Sent: Thursday, April 01, 2004 8:46 AM
> > To: Richard Martin
> > Cc: axis-dev@ws.apache.org
> > Subject: Re: WS-Adressing issue
> >
> > Richard,
> >
> > No. It's not a bad practice. Please open a bug in JIRA saying that there
> is
> > no way in the
> > deploy.wsdd to specify a soap action for an operation. Also, let's keep
> the
> > conversation on the
> > mailing list (not private) as others may chime in.
> >
> > thanks,
> > dims
> >
> > --- Richard Martin <rmarti@essex.ac.uk> wrote:
> > > Yes it does. I am using the wsdl generated by Service?wsdl and using
> > > that as an input to WSDL2Java to generate the stubs. This must be the
> > > source of the problem.
> > >
> > > Is there a way to change the behaviour of ?wsdl so that it generates the
> > > SOAP action?  command line Java2WSDL specifies a --soapAction OPERATION
> > > switch to "force soapAction to the name of the Operation". Is usage of
> > > the ?wsdl generated files concidered bad practice?
> > >
> > > Regards,
> > >
> > > Richard
> > >
> > > Davanum Srinivas wrote:
> > >
> > > >Does your WSDL explicitly sets the soap action to ""?
> > > >
> > > ><soap:operation soapAction=""/>
> > > >
> > > >thanks,
> > > >dims
> > > >
> > > >--- Richard Martin <rmarti@essex.ac.uk> wrote:
> > > >
> > > >
> > > >>Hi WS-Addressing developers!
> > > >>
> > > >>I've come across a slight problem while trying to implement
> > > >>WS-Addressing. I'm very hesitant to call this a bug as I don't have
> the
> > > >>knowledge to make that judgement so I thought I'd run the problem by
> > you.
> > > >>
> > > >>Within the WS-Addressing package is a ShortTutorial.txt (very helpful,
> > > >>thankyou!). This contains a code snippet with a method which sets up
> > > >>most of the Addressing headers, specifically the Action header (which
> is
> >
> > > >>set to urn:action). By using this method I managed to get a very
> simple
> > > >>HelloWorld web service working using Addressing, and have verified
> using
> >
> > > >>tcpmon that the correct SOAPHeader elements are being sent (and
> > recieved).
> > > >>
> > > >>However, when the Action header is not created (specifically in the
> case
> >
> > > >>of the generated Stubs), this causes AddressingHeaders.getAction()
to
> > > >>return null in the AddressingHandler, which in turn causes the
> > > >>AddressingHandler to attempt to create an Action Header from
> > > >>MessageContext.getSOAPActionURI() which returns an empty String ("").
> > > >>This is because, within the stub classes, the soapAction is set as:
> > > >>_call.setSOAPActionURL(""). The result is an exception complaining
> about
> >
> > > >>the empty string.
> > > >>
> > > >>My question is threefold.
> > > >>
> > > >>First of all, am I doing anything wrong? If so please tell me and
> ignore
> >
> > > >>the next questions!
> > > >>
> > > >>Second of all, is the setting of the soapAction to "" within stubs
> > > >>desireable? or is it required to conform with a specification?
> (perhaps
> > > >>this is better for the axis-dev group).
> > > >>
> > > >>Third of all: within the context of WS-Addressing, given that the
> Action
> >
> > > >>header cannot be generated from the soapAction for stubs (or indeed
> for
> > > >>non-stub clients when Call.setSOAPActionURL() has not been called),
> what
> >
> > > >>should be done when there is no user-specified Action header element?
> > > >>Should there be a default (perhaps "urn:action" as used in the
> > > >>ShortTutorial ?)
> > > >>
> > > >>Regards,
> > > >>
> > > >>Richard
> > > >>
> > > >>
> > > >>
> > > >
> > > >
> > > >=====
> > > >Davanum Srinivas - http://webservices.apache.org/~dims/
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> > =====
> > Davanum Srinivas - http://webservices.apache.org/~dims/
> >
> >


=====
Davanum Srinivas - http://webservices.apache.org/~dims/

Mime
View raw message