Hi again,
I've had a little bit more of a look into my issue with the differing
parameter names between my two WSDLs and realised what's happening. My
services.xml looks like the following:
service name=GigListingsService
descriptionNicks Gig Service./description
parameter
Keith,
Please find both versions of my wsdl attached. Note that these are the
files generated using Maven java2wsdl at buildtime that I then go on to use
with Maven wsdl2java to get my client stubs.
http://www.nabble.com/file/p19285397/NicksGigs.wsdl NicksGigs.wsdl
Thanks for your speedy reply Keith. I have been using the following code to
test today:
String epr =
http://localhost:8089/NicksGigs-war-Axis2/services/GigListingsService;;
portal = new NicksGigsServiceV2Stub(epr);
Options options = portal._getServiceClient().getOptions();
Great OK that is all clear now. I'd just like to correct my code I posted
before since I set the CONTENT_TYPE property instead of the MESSAGE_TYPE
property and the former doesn't work as required (in fact I don't know what
it actually does since they both set the Content-Type header but only
I have now generated the httpbindings using wsdl2java with a version 2.0 wsdl
and the operation has been added to the EPR as desired and I can do POST
getGigsIn(London), POST getMostActiveArtist() and GET
getMostActiveArtist() without any problems which is great. The headers for
both GET and
Hi Nick,
See My comments inline
On Tue, Sep 2, 2008 at 11:10 PM, Nick Steel [EMAIL PROTECTED]
wrote:
I have now generated the httpbindings using wsdl2java with a version 2.0
wsdl
and the operation has been added to the EPR as desired and I can do POST
getGigsIn(London), POST
Hi Nick,
Sorry I couldn't get back to you sooner. Was held up with some travel
last week. So here goes, see my comments inline. (As a summary could
you try this with 1.4.1 as I did fix some REST bugs for this release)
On Thu, Aug 21, 2008 at 6:12 PM, Nick Steel
[EMAIL PROTECTED] wrote:
Hi,
Thank you Jay and Keith for your replies. I've upgraded to version 1.4.1 but
this had made no difference. Below is a really simple version of my code
taking the options used by Jay in his working service but I can still only
get the correct response using getGigsIn() with POST, every other
Hi Nick,
If you want to invoke a service using REST then its better to generate
the client stub for the httpBinding (and when doing so I recommend you
to use ?wsdl2 instead of ?wsdl). This is what describes the REST
interface of the service. This is where it will contain details of the
URL the
Keith,
I had no idea ?wsdl2 even existed, I've no idea how I managed to miss this
but I will hunt for it tomorrow and give it a go. Thanks very much this
reply, what you say aout the EPR has definitely cleared some things up for
me and hopefully I can now go on to get this to work.
Just to be
On Tue, Sep 2, 2008 at 2:11 AM, Nick Steel
[EMAIL PROTECTED] wrote:
Keith,
I had no idea ?wsdl2 even existed,
Axis2 supports both WSDL 1.1 and WSDL 2.0. And the WSDL 2.0
HTTPBinding can describe a REST interface for your service in a nice
manner.
I've no idea how I managed to miss this
but
I havn't been able to progress any further with Axis2 and REST, doesn't
anyone have any ideas about these issues?
Nick
--
View this message in context:
http://www.nabble.com/Axis2-REST-client-and-server-questions-%28Data-bindings%2C-Headers%2C-Performance%29-tp19087933p19183617.html
Sent from
Hi Nick,
Sorry I missed this. I'll have a look at this and get back to you.
Thanks,
Keith.
On Wed, Aug 27, 2008 at 9:06 PM, Nick Steel
[EMAIL PROTECTED] wrote:
I havn't been able to progress any further with Axis2 and REST, doesn't
anyone have any ideas about these issues?
Nick
--
View
Working with Axis2 and REST differs a little based on whether you are doing
POSTs or GETs. I have been using Axis2 for REST as well as SOAP, but I
don't use code generated stubs. I am using the ServiceClient to invoke my
services. In that context, I set the following Options on the
Hi,
I've recently started looking at using the REST support in Axis2 to invoke
my web service instead of the currently used SOAP calls and I have a number
of issues I can't work out for myself. Any help with these would be great.
I've been using Axis2 version 1.3 (and then also tried 1.4 in
15 matches
Mail list logo
