Hi Tor,
I already added my vote yesterday. I'll add a comment ASAP.
Regards,
Davide
On Tue, Aug 17, 2010 at 10:52 PM, Torgeir Veimo wrote:
> On 17 August 2010 11:43, Davide Maestroni
> wrote:
>
> > I tried to understand what's happening inside Jackrabbit and I am quite
> > confident now that
On 17 August 2010 11:43, Davide Maestroni wrote:
> I tried to understand what's happening inside Jackrabbit and I am quite
> confident now that the issue is related to the way in which defaults in node
> type definition are handled. [...]
Can you please add your findings to the earlier mentioned
On 17 August 2010 15:39, Alexander Klimetschek wrote:
> On Tue, Aug 17, 2010 at 13:10, Torgeir Veimo wrote:
>> I think the appropriate functionality would be to support 'complex'
>> schema updates through the normal JCR 2.0 mechanism.
>
> Please define "complex". If you think you have cases that
On Tue, Aug 17, 2010 at 13:10, Torgeir Veimo wrote:
> I dont think this is really obvious for anyone except jackrabbit
> developers. I think the code you posted earlier in this thread is the
> first example I've ever seen that enables schema updates.
The point of that code is that it handles CND
On 17 August 2010 12:46, Alexander Klimetschek wrote:
> On Tue, Aug 17, 2010 at 12:04, Torgeir Veimo wrote:
>> On 17 August 2010 11:43, Davide Maestroni wrote:
>>> thanks for the suggestion. That could be a good workaround, though it is
>>> quite annoying that a bug in Jackrabbit code makes the
On Tue, Aug 17, 2010 at 12:04, Torgeir Veimo wrote:
> On 17 August 2010 11:43, Davide Maestroni wrote:
>> thanks for the suggestion. That could be a good workaround, though it is
>> quite annoying that a bug in Jackrabbit code makes the feature of automatic
>> registration of node types in Sling
On Tue, Aug 17, 2010 at 11:43, Davide Maestroni
wrote:
> Hi Alex,
>
> thanks for the suggestion. That could be a good workaround, though it is
> quite annoying that a bug in Jackrabbit code makes the feature of automatic
> registration of node types in Sling unusable.
> I tried to understand what
On 17 August 2010 11:43, Davide Maestroni wrote:
> thanks for the suggestion. That could be a good workaround, though it is
> quite annoying that a bug in Jackrabbit code makes the feature of automatic
> registration of node types in Sling unusable.
Of course fixing this specific problem would b
Hi Alex,
thanks for the suggestion. That could be a good workaround, though it is
quite annoying that a bug in Jackrabbit code makes the feature of automatic
registration of node types in Sling unusable.
I tried to understand what's happening inside Jackrabbit and I am quite
confident now that th
On Mon, Aug 16, 2010 at 19:18, Davide Maestroni
wrote:
> Yes, it could definitely be the same issue, and I see that unfortunately no
> one fixed it...
> Do you happen to know any workaround? I tried to look into Jackrabbit 2.1.0.
> but I could not find any major modifications in the related classe
On 16 August 2010 19:18, Davide Maestroni wrote:
> Yes, it could definitely be the same issue, and I see that unfortunately no
> one fixed it...
> Do you happen to know any workaround? I tried to look into Jackrabbit 2.1.0.
> but I could not find any major modifications in the related classes.
> T
Yes, it could definitely be the same issue, and I see that unfortunately no
one fixed it...
Do you happen to know any workaround? I tried to look into Jackrabbit 2.1.0.
but I could not find any major modifications in the related classes.
This is a real show stopper in case I want to change the node
On 16 August 2010 18:25, Davide Maestroni wrote:
> I have got an issue with the automatic registration of node type definitions
> implemented in Sling. The problem shows up only if I stop and then restart
> the servlet container (I am using Jetty Hightide in this case). After a
> restart cycle, ev
Hi all,
I have got an issue with the automatic registration of node type definitions
implemented in Sling. The problem shows up only if I stop and then restart
the servlet container (I am using Jetty Hightide in this case). After a
restart cycle, every time I re-deploy my node type definitions (al
14 matches
Mail list logo
