Yes, it should take precedence over all JSON providers, and I think your code is correct. You could also return providers in the getClasses() method if you don't have any custom initialization code (i.e. use default constructor only).
On Thu, Jun 23, 2011 at 5:17 PM, Paulo Borges <[email protected]> wrote: > > > Bryant: > The extension indeed comes with META-INF/wink-application. When you say: > >>> If you want it to take precedent over any other provider (versus just >>> having it auto-registered), >>> you should return it in your Application sub-class or wink-application >>> file. > > Do you mean, it takes precedence over all (basically default) JSON providers. > If so, would the following method do it in my > Application class > > @Override > public Set<Object> getSingletons() { > Set<Object> s = new HashSet<Object>(); > //The following is the class file in extension.jar > WinkJacksonJaxbJsonProvider jacksonProvider = new > WinkJacksonJaxbJsonProvider(); > s.add(jacksonProvider); > return s; > } > > ---------------------------------------- >> From: [email protected] >> Date: Thu, 23 Jun 2011 16:12:42 -0500 >> Subject: Re: Wink Jackson extension >> To: [email protected] >> >> Hello, >> >> For the Wink Jackson extension JAR, it should have a >> META-INF/wink-application file in it which auto-registers the >> provider. The logs should also indicate that the >> WinkJacksonJaxbJsonProvider if they are turned on to "all". If you >> want it to take precedent over any other provider (versus just having >> it auto-registered), you should return it in your Application >> sub-class or wink-application file. >> >> On Thu, Jun 23, 2011 at 3:34 PM, Paulo Borges <[email protected]> wrote: >> > >> > Hi: >> > >> > I was wondering if dropping Wink Jackson provider extension in WEB-INF/lib >> > is enough to have it registered as a default JSON provider or other >> > configuration is needed. I could not find any info on this one in >> > userguide.pdf doc. >> > >> > regards, >> > >
