You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by GOBE HOBONA <ge...@hotmail.com> on 2006/06/02 00:16:09 UTC
Multiple methods in RPC-based service
Hello,
Hopefully somebody might be able to shed some light.
I have a class called CatalogueService which implements two methods
getSearchResults() and getRecord() in that order.
I have specified RPCMessageReceiver as my messagereceiver.
Surprisingly, the REST endpoint reference appears to only expose the first
method implemented in the CatalogueService class. The second method throws
an "HTTP response code: 500".
When I switch the methods around the previously working method throws the
error and the previously mulfunctioning method starts working.
Is this behaviour expected?
My service.xml file reads:
<service name="NEEDSService">
<description>
North East Environmental Data Server Web Service Container.
</description>
<messageReceivers>
<messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out"
class="org.apache.axis2.rpc.receivers.RPCMessageReceiver" />
</messageReceivers>
<parameter name="ServiceClass"
locked="false">uk.ac.ncl.needs.ws.CatalogueService</parameter>
</service>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Multiple methods in RPC-based service
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Thats a bug :)
can you please help me to re generate the problem .
GOBE HOBONA wrote:
> Hello,
>
> Hopefully somebody might be able to shed some light.
>
> I have a class called CatalogueService which implements two methods
> getSearchResults() and getRecord() in that order.
>
> I have specified RPCMessageReceiver as my messagereceiver.
>
> Surprisingly, the REST endpoint reference appears to only expose the
> first method implemented in the CatalogueService class. The second
> method throws an "HTTP response code: 500".
>
> When I switch the methods around the previously working method throws
> the error and the previously mulfunctioning method starts working.
>
> Is this behaviour expected?
>
> My service.xml file reads:
>
> <service name="NEEDSService">
> <description>
> North East Environmental Data Server Web Service Container.
> </description>
> <messageReceivers>
> <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out"
> class="org.apache.axis2.rpc.receivers.RPCMessageReceiver" />
> </messageReceivers>
> <parameter name="ServiceClass"
> locked="false">uk.ac.ncl.needs.ws.CatalogueService</parameter>
> </service>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
--
Thanks,
Deepal
................................................................
~Future is Open~
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Multiple methods in RPC-based service
Posted by Anne Thomas Manes <at...@gmail.com>.
By definition, a "REST" interface does not expose multiple methods. In fact,
defining any specific method (rather than the generic GET, POST, PUT, DELETE
methods) is unRESTful. A POX interface can expose multiple methods, but if
your goal is to design a REST-compliant resource, then you should comply
with the REST architecture.
See this excellent blog post on the difference between REST and "STREST":
http://duncan-cragg.org/blog/post/strest-service-trampled-rest-will-break-web-20/
Anne
On 6/2/06, GOBE HOBONA <ge...@hotmail.com> wrote:
>
> I have placed the source at the following URL
>
> http://www.students.ncl.ac.uk/g.e.hobona/rsrc/project001.zip
>
> It's only about five or so classes and the entry point is
> CatalogueService.java
>
> Gobe
>
>
> >From: Deepal Jayasinghe <de...@opensource.lk>
> >Reply-To: axis-user@ws.apache.org
> >To: axis-user@ws.apache.org
> >Subject: Re: Multiple methods in RPC-based service
> >Date: Fri, 02 Jun 2006 10:12:11 +0530
> >
> >If it is behave like that , then that definitely a bug :)
> >
> >can you please help me to re generate the problem .
> >
> >GOBE HOBONA wrote:
> >
> > > Hello,
> > >
> > > Hopefully somebody might be able to shed some light.
> > >
> > > I have a class called CatalogueService which implements two methods
> > > getSearchResults() and getRecord() in that order.
> > >
> > > I have specified RPCMessageReceiver as my messagereceiver.
> > >
> > > Surprisingly, the REST endpoint reference appears to only expose the
> > > first method implemented in the CatalogueService class. The second
> > > method throws an "HTTP response code: 500".
> > >
> > > When I switch the methods around the previously working method throws
> > > the error and the previously mulfunctioning method starts working.
> > >
> > > Is this behaviour expected?
> > >
> > > My service.xml file reads:
> > >
> > > <service name="NEEDSService">
> > > <description>
> > > North East Environmental Data Server Web Service Container.
> > > </description>
> > > <messageReceivers>
> > > <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out"
> > > class="org.apache.axis2.rpc.receivers.RPCMessageReceiver" />
> > > </messageReceivers>
> > > <parameter name="ServiceClass"
> > > locked="false">uk.ac.ncl.needs.ws.CatalogueService</parameter>
> > > </service>
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-user-help@ws.apache.org
> > >
> > >
> > >
> >
> >--
> >Thanks,
> >Deepal
> >................................................................
> >~Future is Open~
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
Re: Multiple methods in RPC-based service
Posted by GOBE HOBONA <ge...@hotmail.com>.
I have placed the source at the following URL
http://www.students.ncl.ac.uk/g.e.hobona/rsrc/project001.zip
It's only about five or so classes and the entry point is
CatalogueService.java
Gobe
>From: Deepal Jayasinghe <de...@opensource.lk>
>Reply-To: axis-user@ws.apache.org
>To: axis-user@ws.apache.org
>Subject: Re: Multiple methods in RPC-based service
>Date: Fri, 02 Jun 2006 10:12:11 +0530
>
>If it is behave like that , then that definitely a bug :)
>
>can you please help me to re generate the problem .
>
>GOBE HOBONA wrote:
>
> > Hello,
> >
> > Hopefully somebody might be able to shed some light.
> >
> > I have a class called CatalogueService which implements two methods
> > getSearchResults() and getRecord() in that order.
> >
> > I have specified RPCMessageReceiver as my messagereceiver.
> >
> > Surprisingly, the REST endpoint reference appears to only expose the
> > first method implemented in the CatalogueService class. The second
> > method throws an "HTTP response code: 500".
> >
> > When I switch the methods around the previously working method throws
> > the error and the previously mulfunctioning method starts working.
> >
> > Is this behaviour expected?
> >
> > My service.xml file reads:
> >
> > <service name="NEEDSService">
> > <description>
> > North East Environmental Data Server Web Service Container.
> > </description>
> > <messageReceivers>
> > <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out"
> > class="org.apache.axis2.rpc.receivers.RPCMessageReceiver" />
> > </messageReceivers>
> > <parameter name="ServiceClass"
> > locked="false">uk.ac.ncl.needs.ws.CatalogueService</parameter>
> > </service>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
> >
>
>--
>Thanks,
>Deepal
>................................................................
>~Future is Open~
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Multiple methods in RPC-based service
Posted by Deepal Jayasinghe <de...@opensource.lk>.
If it is behave like that , then that definitely a bug :)
can you please help me to re generate the problem .
GOBE HOBONA wrote:
> Hello,
>
> Hopefully somebody might be able to shed some light.
>
> I have a class called CatalogueService which implements two methods
> getSearchResults() and getRecord() in that order.
>
> I have specified RPCMessageReceiver as my messagereceiver.
>
> Surprisingly, the REST endpoint reference appears to only expose the
> first method implemented in the CatalogueService class. The second
> method throws an "HTTP response code: 500".
>
> When I switch the methods around the previously working method throws
> the error and the previously mulfunctioning method starts working.
>
> Is this behaviour expected?
>
> My service.xml file reads:
>
> <service name="NEEDSService">
> <description>
> North East Environmental Data Server Web Service Container.
> </description>
> <messageReceivers>
> <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out"
> class="org.apache.axis2.rpc.receivers.RPCMessageReceiver" />
> </messageReceivers>
> <parameter name="ServiceClass"
> locked="false">uk.ac.ncl.needs.ws.CatalogueService</parameter>
> </service>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
--
Thanks,
Deepal
................................................................
~Future is Open~
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
XML representantion of Axis objects
Posted by Carlos Bazílio <ca...@yahoo.com.br>.
Dear,
I've been trying to obtain an XML representantion of an Axis object. I've been
using the wsdl2java task. Is it possible to do it using the generated
classes? And with the Axis project?
Thanks in advance and best regards,
Carlos
__________________________________
http://www.inf.puc-rio.br/~bazilio
---------------------------------
Abra sua conta no Yahoo! Mail - 1GB de espaço, alertas de e-mail no celular e anti-spam realmente eficaz.