built-in types updated

HI all,

The built-in types where updated.
You need to force reloading types into jackrabbit

You can do this by adding the attribute
forceReloadTypes="true"
inside
<repository name="demo" 
factory="org.nuxeo.ecm.core.jcr.JCRRepositoryFactory&qu
ot; 
securityManager="org.nuxeo.ecm.core.jcr.JCRSecurityMana
ger">

in the file

nuxeo.ear/demo-ds-bundle.xml

Bogdan
_______________________________________________
ECM mailing list
ECMlists.nuxeo.com
http://li
sts.nuxeo.com/mailman/listinfo/ecm

Bogdan Stefanescu wrote:
> The built-in types where updated.
> You need to force reloading types into jackrabbit
> 
> You can do this by adding the attribute
forceReloadTypes="true"
> inside
> <repository name="demo"
>
factory="org.nuxeo.ecm.core.jcr.JCRRepositoryFactory&qu
ot;
>
securityManager="org.nuxeo.ecm.core.jcr.JCRSecurityMana
ger">
> 
> in the file
> 
> nuxeo.ear/demo-ds-bundle.xml

Do we have any idea to ensure compat at 5.1 release time ?

Is adding the forceReloadTypes="true" a viable
option by default or is
it too costly ?

	J.

-- 
Julien Anguenot | Nuxeo R&D (Paris, France)
Open Source ECM - http://www.nuxeo.com
Nuxeo 5 : http://www.nuxeo.org
Mobile: +33 (0) 6 72 57 57 66


_______________________________________________
ECM mailing list
ECMlists.nuxeo.com
http://li
sts.nuxeo.com/mailman/listinfo/ecm

Julien Anguenot wrote:
> Bogdan Stefanescu wrote:
>   
>> The built-in types where updated.
>> You need to force reloading types into jackrabbit
>>
>> You can do this by adding the attribute
forceReloadTypes="true"
>> inside
>> <repository name="demo"
>>
factory="org.nuxeo.ecm.core.jcr.JCRRepositoryFactory&qu
ot;
>>
securityManager="org.nuxeo.ecm.core.jcr.JCRSecurityMana
ger">
>>
>> in the file
>>
>> nuxeo.ear/demo-ds-bundle.xml
>>     
>
> Do we have any idea to ensure compat at 5.1 release
time ?
>
> Is adding the forceReloadTypes="true" a
viable option by default or is
> it too costly ?
>
> 	J.
>
>   
When updating the nuxeo schemas the only way we synchronize
with 
jackrabbit is to use this flag for now.
It's not so costly to add it by default - it is done only
once at 
deploying time. But this can be dangerous because it
recreate from zero the jackrabbit node types without
checking if 
existing data is compatible with the new types.
And  if it is not this can lead  to broken repositories.

Bogdan


_______________________________________________
ECM mailing list
ECMlists.nuxeo.com
http://li
sts.nuxeo.com/mailman/listinfo/ecm

Bogdan Stefanescu wrote:
> Julien Anguenot wrote:
>> Bogdan Stefanescu wrote:
>>  
>>> The built-in types where updated.
>>> You need to force reloading types into
jackrabbit
>>>
>>> You can do this by adding the attribute
forceReloadTypes="true"
>>> inside
>>> <repository name="demo"
>>>
factory="org.nuxeo.ecm.core.jcr.JCRRepositoryFactory&qu
ot;
>>>
securityManager="org.nuxeo.ecm.core.jcr.JCRSecurityMana
ger">
>>>
>>> in the file
>>>
>>> nuxeo.ear/demo-ds-bundle.xml
>>>     
>>
>> Do we have any idea to ensure compat at 5.1 release
time ?
>>
>> Is adding the forceReloadTypes="true" a
viable option by default or is
>> it too costly ?
>>
>>     J.
>>
>>   
> When updating the nuxeo schemas the only way we
synchronize with
> jackrabbit is to use this flag for now.
> It's not so costly to add it by default - it is done
only once at
> deploying time. But this can be dangerous because it
> recreate from zero the jackrabbit node types without
checking if
> existing data is compatible with the new types.
> And  if it is not this can lead  to broken
repositories.

ok. Thanks for the information.

Did you add a Jira entry so that we can have a trace about
that for the
next release while generating the history ?

	J.

-- 
Julien Anguenot | Nuxeo R&D (Paris, France)
Open Source ECM - http://www.nuxeo.com
Nuxeo 5 : http://www.nuxeo.org
Mobile: +33 (0) 6 72 57 57 66


_______________________________________________
ECM mailing list
ECMlists.nuxeo.com
http://li
sts.nuxeo.com/mailman/listinfo/ecm