You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by fachhoch <fa...@gmail.com> on 2010/03/08 17:44:15 UTC
good practices for @WebParam
My service needs input to provide response.
right now My service needs 5 input parameters for response , of which 3
are string and 2 are dates
should I use a Object to get all these parameters or 5 seperate parameters
? which is better ?
becasue My service is used by third party , I need suggestions on which is
the better way ?
--
View this message in context: http://old.nabble.com/good-practices-for---%40WebParam-tp27823960p27823960.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: good practices for @WebParam
Posted by Bartłomiej Chmielewski <ba...@gmail.com>.
W dniu 09.03.2010 06:35, Coder One pisze:
> One Request class with all parameters inside...better for evolution of signatures...
>
>
>
> ----- Original Message ----
> From: Ron Grimes<rg...@sinclairoil.com>
> To: "users@cxf.apache.org"<us...@cxf.apache.org>
> Sent: Mon, March 8, 2010 9:21:39 AM
> Subject: RE: good practices for @WebParam
>
> I would argue that 5 separate parameters would be best. If for no other reason, it's easier to build test requests with a tool like SOAPUI.
>
> Ron
>
>
We use in our company separate parameters and it works good. Aggregation
class for request is also good solution - probably worthy of
consideration. Both solutions are easy to test with SoapUI.
Regards,
Bartłomiej Chmielewski
Re: good practices for @WebParam
Posted by Coder One <co...@yahoo.com>.
One Request class with all parameters inside...better for evolution of signatures...
----- Original Message ----
From: Ron Grimes <rg...@sinclairoil.com>
To: "users@cxf.apache.org" <us...@cxf.apache.org>
Sent: Mon, March 8, 2010 9:21:39 AM
Subject: RE: good practices for @WebParam
I would argue that 5 separate parameters would be best. If for no other reason, it's easier to build test requests with a tool like SOAPUI.
Ron
-----Original Message-----
From: fachhoch [mailto:fachhoch@gmail.com]
Sent: Monday, March 08, 2010 9:44 AM
To: users@cxf.apache.org
Subject: good practices for @WebParam
My service needs input to provide response.
right now My service needs 5 input parameters for response , of which 3
are string and 2 are dates
should I use a Object to get all these parameters or 5 seperate parameters
? which is better ?
becasue My service is used by third party , I need suggestions on which is
the better way ?
--
View this message in context: http://old.nabble.com/good-practices-for---%40WebParam-tp27823960p27823960.html
Sent from the cxf-user mailing list archive at Nabble.com.
RE: good practices for @WebParam
Posted by Ron Grimes <rg...@sinclairoil.com>.
I would argue that 5 separate parameters would be best. If for no other reason, it's easier to build test requests with a tool like SOAPUI.
Ron
-----Original Message-----
From: fachhoch [mailto:fachhoch@gmail.com]
Sent: Monday, March 08, 2010 9:44 AM
To: users@cxf.apache.org
Subject: good practices for @WebParam
My service needs input to provide response.
right now My service needs 5 input parameters for response , of which 3
are string and 2 are dates
should I use a Object to get all these parameters or 5 seperate parameters
? which is better ?
becasue My service is used by third party , I need suggestions on which is
the better way ?
--
View this message in context: http://old.nabble.com/good-practices-for---%40WebParam-tp27823960p27823960.html
Sent from the cxf-user mailing list archive at Nabble.com.