Hi Carsten,
thanks for your quick feedback - yes it works without functional
degradations but it actually spams the error.log with INFO messages which
is not acceptable in productive Code. Do you see a way to workaround this
issue and/or give an estimation when this issue could be fixed? I'd help
Am 29.10.14 um 11:13 schrieb Dominik Süß:
Hi Carsten,
thanks for your quick feedback - yes it works without functional
degradations but it actually spams the error.log with INFO messages which
is not acceptable in productive Code. Do you see a way to workaround this
issue and/or give an
On Wed, Oct 29, 2014 at 5:24 PM, Carsten Ziegeler cziege...@apache.org wrote:
Am 29.10.14 um 11:13 schrieb Dominik Süß:
Hi Carsten,
thanks for your quick feedback - yes it works without functional
degradations but it actually spams the error.log with INFO messages which
is not acceptable in
Hi everybody,
I might have found a bug related to the changes of SLING-3848.
Due to some requirements some properties of a resource had to be moved to a
third location for the resources of one very specific contentbranch. Now I
do have a ResourceProvider that does nothing more then creating a
This is the ugly code trying to get the content length for a resource. I
think this code is unchanged, it's now just invoked different and maybe
the reporting of the exception is new. However, the exception is
swalled, so your provider should still work.
But maybe we have to revisit the code in
