now I have a strange situation here..
- one resource comes with the natural notation
curl -v -XGET
http://fgaucho.dyndns.org:8080/arena-http/ads
-HAccept:application/json
- other resource comes with the JAXB notation:
curl -v -XGET
http://fgaucho.dyndns.org:8080/arena-http/user/marley
-HAccept:application/json
both deployed in the same package, resources of the same application.
* if you open both URIs in a browser, you can see both resources
contains attributes..
On Wed, Jan 20, 2010 at 3:32 PM, Paul Sandoz <Paul.Sandoz_at_sun.com> wrote:
> Can you recall what changes you made before the natural convention stopped
> working?
>
> Have you verified if your ContextResolver that sets up the natural
> convention configuration is getting registered and invoked?
>
> Paul.
>
> On Jan 20, 2010, at 2:27 PM, Felipe Gaścho wrote:
>
>> I have two files in the META-INF folder:
>>
>> javax.ws.rs.ext.MessageBodyReader
>> javax.ws.rs.ext.MessageBodyWriter
>>
>
>> and now the JSON is still returning with @ symbol for JAXB atributes :
>>
>> curl -XGET http://fgaucho.dyndns.org:8080/arena-http/user
>> -HAccept:application/json
>>
>> what else should I do to have natural notation ?
>> --
>> ------------------------------------------
>> Felipe Gaścho
>> 10+ Java Programmer
>> CEJUG Senior Advisor
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
>> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
>
--
------------------------------------------
Felipe Gaścho
10+ Java Programmer
CEJUG Senior Advisor