Hi
Thanks for trying these suggestions. Are you thinking of applying the changes
you've referred to
the existing JSONProvider ? That's are you explicitly configuring the existing
JSONProvider in Spring ?
Thats' probably a good idea - that way people can just reuse the existing
provider rather than creating a duplicate...
Please create a JIRA and attach your patch.
Cheers, Sergey
----- Original Message -----
From: "Sergey Beryozkin" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, June 18, 2008 5:03 PM
Subject: Re: REST + JSON + Namespaces
Ok, sure, that can be fixed.
In meantime, the simplest workaround is to copy and paste the existing
JSONProvider, update it to pass the correct properties to the
constructor, or possibly have the factory bean injected through spring, and
then register the custom provider through
jaxrs:providers, and it will be checked first...
JAX-RS ContextResolvers will also be supported soon.
Cheers, Sergey
On Jun 18, 2008, at 11:35 AM, Sergey Beryozkin wrote:
Just would like to clarify :
Do you expect that the bean with id 'jsonOutputFactory' is to be used as a org.codehaus.jettison.mapped.MappedXMLOutputFactory
instance ?
At the moment, no jaxrs:properties are checked. But that can be fixed...
Cheers, Sergey
Yes.. I want my service to do JSON, but it doesn't work unless I can configure jettison first with the namespace prefixes I need,
and I can't figure out how to inject that map via Spring anywhere.
I see a couple examples on the web how to do it programatically, but not how
to do it in my spring container.
--Joe
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
