On 5/25/12 11:05 PM, Jim Stafford wrote:
> I have been able to remove all API calls from the resource methods and
> have written a custom JSON marshaller that works off the RESTEasy
> annotations. Sweet.
>
The Jettison issues you encountered should be fixed.
Bill
--
Bill Burke
JBoss, a divisi
Wahoo! All is well with RESTEasy 2.3.3.Final (with JBoss 7.1.1 and CDI
beans.xml) and adding the @Annotations to the input arguments.
That goes for other annotations like @BadgerFish as well
...
@BadgerFish
public Response putJSONLinkBadgerfish(
@BadgerFish Link link)
I would
Ok, The problem is that you also have to annotate the link parameter:
@PUT @Path("attributes")
@Consumes(MediaType.APPLICATION_JSON)
@Produces(MediaType.APPLICATION_JSON)
@Mapped(namespaceMap = {
@XmlNsMap(namespace = "http://ejava.info";, jsonName = "ejava"),
})
public
I apologize really for this. I have shown Jettison zero love since
Jackson came into the picture, mainly because I feel it is inferior.
Have you used Jackson? If you chose Jettison over it, why?
On 5/17/12 12:33 PM, Jim Stafford wrote:
>> a) works in controlled Maven unit test environment but
> a) works in controlled Maven unit test environment but not when deployed to
> JBoss 7
You are right. I failed to realize that the jackson and jettison .jars
are now part of the application server and not part of the deployed
WAR when I first reported this. I will enable the jettison settings.
>
On 5/17/12 10:39 AM, Bill Burke wrote:
> If its all right with you, let's figure out exactly what you need and
> what bugs exist so that you don't have to do manual json.
>
> On 5/15/12 7:07 PM, Jim Stafford wrote:
>> fyi...I ended up removing all built-in JSON marshalling and replacing
>> with m
If its all right with you, let's figure out exactly what you need and
what bugs exist so that you don't have to do manual json.
On 5/15/12 7:07 PM, Jim Stafford wrote:
> fyi...I ended up removing all built-in JSON marshalling and replacing
> with manual calls to Jettison for both demarshalling JS
fyi...I ended up removing all built-in JSON marshalling and replacing
with manual calls to Jettison for both demarshalling JSON inputs and
marshalling JSON outputs before it was all over. I ran into cases
where
a) it worked fine using Jetty in the unit test/Maven environment and
returned different
You logged this as a JIRA too right? This is scheduled to be looked at
for 2.3.4 that I hope to start work on soon. My queue is full at the
moment.
On 5/13/12 11:22 PM, Jim Stafford wrote:
> I am encountering an error while demarshalling a JSON object as input
> to a JAX-RS method. After some
