I would prefer to not see a mandatory dependency but don't have a big problem with optional dependency. Still, my gut feeling is that adding a jsonToMap() function is something that the developer should be doing themselves for now rather than being provided.
Perhaps in the future, when JSF-353 is final, passThroughAttributes could be changed to support JSON Strings directly?
Phil.
----- Original Message -----
> From: "Andy Schwartz" <andy.schwartz_at_oracle.com>
> To: jsr344-experts_at_javaserverfaces-spec-public.java.net
> Cc: "Edward Burns" <edward.burns_at_oracle.com>
> Sent: Thursday, June 28, 2012 6:58:50 AM
> Subject: [jsr344-experts] Re: [1089-PassThroughAttributes] JSON dependency: OK?
>
> On 6/28/12 9:29 AM, Kito Mann wrote:
> > I think this is probably worth it, since there are so few
> > dependencies
> > already. One of my clients does some custom JSON parsing; they were
> > using the libraries that ship with WAS, but now they use the ones
> > included with PrimeFaces. However, I've worked with several clients
> > that wouldn't go down that path.
>
> Fortunately, jsr-353 is addressing exactly this use case. Not sure
> whether JSF should itself force this dependency now, or hold off a
> bit
> until jsr-353 is integrated into the Java EE platform. Of course, if
> jsr-353 isn't going to make it for Java EE7, I would be more tempted
> to
> force the dependency.
>
> Andy
>
>