I've created SLING-2780 and made an implementation (well I made three
different ones to see how they work).
If no one complains, I'll set this to resolved.
Thanks
Carsten
2013/3/6 Carsten Ziegeler cziege...@apache.org:
I've asked @work, but it seems no one is using ResourceMetadata for
I've asked @work, but it seems no one is using ResourceMetadata for writing.
As no one else complained so far (which is a good sign), I think we
should proceed.
Carsten
2013/3/5 Felix Meschberger fmesc...@adobe.com:
Hi,
As much as I would like to make ResourceMetadata read-only, I am not
Hi,
As much as I would like to make ResourceMetadata read-only, I am not really
comfortable ...
How about running this by our users list and see, whether there is some
feedback ?
Regards
Felix
Am 04.03.2013 um 14:28 schrieb Carsten Ziegeler:
2013/3/4 Felix Meschberger fmesc...@adobe.com:
2013/3/4 Felix Meschberger fmesc...@adobe.com:
Hi,
I have been looking into this some time ago. And I am also somewhat unhappy
with the read/write nature of the ResourceMetadata.
While I think in general we can make the ResourceMetadata read-only, we have
a problem with code like:
On Mon, Mar 4, 2013 at 5:24 AM, Felix Meschberger fmesc...@adobe.com wrote:
...We could see, whether it would be possible to make the ResourceMetadata
read-only after resource
resolution has completed, e.g. ResourceMetadata.lock(). But I am not really
convinced
Maybe wrap it in a
Hi,
while looking into some issues, I realized that ResourceMetadata is
not only extending a HashMap (which makes handling easier), but we
have absolutely no information if this map can be changed by client
code or is a read-only map.
I think we should add this to the documentation and make this
