Hi
Can you please post a sample resource class and this Employee object ?
@FormParams get translated to WADL parameters of type 'query'...FormParam("") should result in individual Employee properties such
as 'manager' being listed as parameters, but I'd like to 'manager' actually refers to another complex object or not...
cheers, Sergey
----- Original Message -----
From: "Sharma, Abhishek" <[email protected]>
To: <[email protected]>
Sent: Wednesday, February 17, 2010 10:13 AM
Subject: how to send Nested object in RESTful webservice
I am planning to use CXF as my Webservice development framework. The java code is already written using spring and hibernate. The
requirement is to expose the service layer in Model as web service and their method as web methods in probably both SOAP and REST.
As a proof of concept I found CXF to work excellently with my application but
I've still some open issues/questions:
Questions specific to RESTful web services:
1. We have @IgnoreProperty for SOAP based services what is the corresponding
property for RESTful mode?
2. How to send Nested object in REST?
Details: I've to add an employee which has a @ManyToOne relationship with the
manager object. Now WADl says
<param name="manager" style="query" />.
How can I send the entire object as query parameter? I've used
add(@FormParam("") Employee employee) web method to publish.
Or Do I need to put any annotation over getManager() in my Employee pojo?
1. How to do exception handling for REST like we have SOAPFault in soap based
webservices
Question specific to General design:
In my web methods I am passing entire object while search/update. For now code is using only a few values inside the object and
ignoring the rest. What should be the behavior in case of webservice as the client might pass values in request which are actually
ignored by the web method. For this I just want to know what standard web service architecture recommends?
Thanks for help
Regards,
Abhishek
The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.
=
