After long investigation....
I realized that I forgot to move @QueryParam annotation to service
interface.. :)

Now everything works great with Tapestry 5.3.1 and
tapestry-resteasy-0.3.0-SNAPSHOT :)


On Thu, Jan 26, 2012 at 11:17 AM, Yohan Yudanara
<yohan.yudan...@gmail.com>wrote:

> This error happens when I'm moving  @GET, @Produces, @Path annotations
> from service implementation to service interface.
>
> I've tried using tapestry-resteasy 0.2.1 and tapestry 5.2.6 with
> annotations on service interface, and then the same error happened.
> When I move the annotations to service implementation, everything went
> right.
>
> I'm using Tapestry 5.3, so I need to move the annotations to service
> interface as described on
> http://docs.codehaus.org/display/TYNAMO/tapestry-resteasy+guide.
>
> Do you know how to overcome this problem?
>
> Thanks in advance.
>
> Best regards,
> Yohan Yudanara
>
>
> On Thu, Jan 26, 2012 at 10:54 AM, Yohan Yudanara <yohan.yudan...@gmail.com
> > wrote:
>
>> When I'm using tapestry 5.3.1 with  tapestry-resteasy 5.2.1, I also get
>> similar exception:
>>
>> org.jboss.resteasy.spi.BadRequestException: content-type was null and
>> expecting to extract a body into public abstract java.lang.String
>> MyAuthentication.requestChallenge(java.lang.Long,java.lang.String)
>>         at
>> org.jboss.resteasy.core.MessageBodyParameterInjector.inject(MessageBodyParameterInjector.java:131)
>>         at
>> org.jboss.resteasy.core.MethodInjectorImpl.injectArguments(MethodInjectorImpl.java:114)
>>
>> my rest services is not on autodiscovery package.
>>
>> On Thu, Jan 26, 2012 at 8:56 AM, Yohan Yudanara <yohan.yudan...@gmail.com
>> > wrote:
>>
>>> Hi..
>>>
>>> Sorry for the late reply.
>>> I've tried using tapestry-resteasy 0.3.0-SNAPSHOT with tapestry 5.3.1.
>>> But I've got problem now.
>>>
>>> When I'm accessing All of my REST URL, I've got this exception:
>>>
>>> 26 Jan 2012 08:33:26,965 [WARN] core.SynchronousDispatcher Failed
>>> executing GET /authentication/challenge
>>> org.jboss.resteasy.spi.ReaderException:
>>> org.jboss.resteasy.core.ExceptionAdapter:  : null
>>>         at
>>> org.jboss.resteasy.core.MessageBodyParameterInjector.inject(MessageBodyParameterInjector.java:202)
>>>         at
>>> org.jboss.resteasy.core.MethodInjectorImpl.injectArguments(MethodInjectorImpl.java:123)
>>>         at
>>> org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:146)
>>>         at
>>> org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:257)
>>>         at
>>> org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:222)
>>>         at
>>> org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:211)
>>>         at
>>> org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:525)
>>>         at
>>> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:502)
>>>         at
>>> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119)
>>>         at
>>> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)
>>>         at
>>> org.tynamo.resteasy.ResteasyRequestFilter.service(ResteasyRequestFilter.java:96)
>>>         at $HttpServletRequestFilter_2a4551aa48d.service(Unknown Source)
>>>         at $HttpServletRequestHandler_2a4551aa492.service(Unknown Source)
>>>         at
>>> org.apache.tapestry5.internal.services.IgnoredPathsFilter.service(IgnoredPathsFilter.java:62)
>>>         at $HttpServletRequestFilter_2a4551aa48e.service(Unknown Source)
>>>         at $HttpServletRequestHandler_2a4551aa492.service(Unknown Source)
>>>         at
>>> org.apache.tapestry5.services.TapestryModule$1.service(TapestryModule.java:852)
>>>         at $HttpServletRequestHandler_2a4551aa492.service(Unknown Source)
>>>         at $HttpServletRequestHandler_2a4551aa48c.service(Unknown Source)
>>>         at
>>> org.apache.tapestry5.TapestryFilter.doFilter(TapestryFilter.java:171)
>>>
>>> I've moved the @Path, @Get, and @Produces annotation to interface.
>>> Do you have any clue about this problem?
>>>
>>> Previously, my rest web service working smooth with T 5.2.6 and
>>> tapestry-resteasy 0.2.1
>>>
>>> Thanks in advance..
>>>
>>> Best regards,
>>> Yohan Yudanara
>>>
>>>
>>> On Mon, Jan 16, 2012 at 4:18 PM, Alejandro Scandroli <
>>> ascandr...@codehaus.org> wrote:
>>>
>>>> Hi Yohan
>>>>
>>>> >
>>>> > When does tapestry-resteasy 0.3.0 will be released?
>>>> >
>>>>
>>>>    It will be released in a couple of weeks. I just want to add a new
>>>> Symbol to avoid scanning the ".rest" package if you don't need to.
>>>>
>>>> > Is it stable enough to use it?
>>>> >
>>>>    I think it is but I just recently started to test it in one of my
>>>> projects. There is almost no new code in it, only dependency upgrades.
>>>>
>>>> >
>>>> > I want to upgrade because I need to use resteasy-jaxrs-2.3.0.GA,
>>>> instead of
>>>> > resteasy-jaxrs-2.0.1.GA
>>>> >
>>>>    Please try it out, give it a shot and let me know if you find any
>>>> issues. BTW, are you also going to upgrade to Tapestry 5.3?
>>>>
>>>> > Thank you...
>>>>
>>>>
>>>> Cheers.
>>>> Alejandro.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>
>>
>

Reply via email to