Carsten Ziegeler wrote
> It seems option 2 is our favorite here:
>> 2) Release the new api as 2.0 under a different symbolic name allowing
>> our users to have new and old side by side. In that case we would need
>> to deprecate 1.x and users should upgrade over time.
>>
>
> Now, I personally still think we should not add a new JSONUtil as it's
> usage is questionable.
>
> Second comment, if we increase the version to 2.0, are we happy with the
> current API or is there something we could improve/change there?
> Users have to adjust their code anyway (or at least recompile/rebuild),
> so if there is anything we should improve, now is a good time. (I'm not
> implying there is, just bringing up the opportunity)
>
Just had a look at the API and I think we should remove these methods
from XSSAPI:
XSSAPI getRequestSpecificAPI(SlingHttpServletRequest request);
XSSAPI getResourceResolverSpecificAPI(ResourceResolver
resourceResolver);
Neither the request nor the resource resolver are used, the
implementation just returns "this". And by removing these methods we
remove a unnecessary dependency to the Sling API
Regards
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
