Frits Walraven wrote:The only disadvantage you have when studying RESTEasy for the WSD exam is for coding Web Service client. The exam topic "Create a web service client for a RESTful web service" assumes you have some basic knowledge coding a Jersey JAX-RS client.
For the exam you can stick to Jersey 1.x (as it conforms to JAX-RS v1.1). If you read the Jersey 2.x manual you willl learn a lot of stuff that is not part of the exam (as it conforms to JAX-RS 2.0).
Here is the link to the Jersey 1.18 manual.
Regards,
Frits
Himai Minh wrote:For this exam, focus on Jersey API. Someone mentioned in this forum that reading the latest Jersey User Guide (version 2.8) from Chapter 1 -5 will help.
But it is still ok to practice with RestEasy. The basic concepts of both RestEasy and Jersey are more or less the same.
Ulf Dittmer wrote:Well ... I'll let the experts answer that. The Exam Topics (which I'm sure you've read by now, short as they are) mention "Create a RESTful web service in a servlet container", amongst other topics. That could conceivably involve deployment steps that are implementation-dependent.
Ulf Dittmer wrote:Jersey is the RI. Since the objective is JAX-RS, though, I would imagine that any conforming implementation would be fine.
Ulf Dittmer wrote:I can't think of a good reason why they wouldn't. Those frameworks do so much for you, and are so easy to use, that it'd be a waste of time to reinvent the wheel, IMO.
Ulf Dittmer wrote:My first question would be: why are you not using a REST framework like Jersey? Implementing all those low-level parts is a lot of work that other folks have already done for you.
Luan Cestari wrote:Is there any error message? I was thinking a little bit more about this problem, i think i was wrong (after looking more the WSDL/XML schema and amazon docs), maybe what it is really missing the Signature parameter.
http://docs.aws.amazon.com/AWSECommerceService/latest/DG/ItemSearch.html
http://docs.aws.amazon.com/AWSECommerceService/latest/DG/TheXMLMessageforanItemSearchSOAPRequest.html
Luan Cestari wrote:I think the problem is this line:
Holder<OperationRequest> operation_request = null;
You must define the operation, which in this case would be the ItemSearch I think.