this is a very very interesting approach...
Please tell me how to get the JCR Browser for all repositories. 
Or can u give ma a link for a description.

I remember in 3.0 there was a "magnolia.bootstrap.force" value in
magnolia.properties.
In 3.5.8 i cannot find this anymore - is this attribute still usable in
3.5.8 ???

thx a lot.




Magnolia - User mailing list wrote:
> 
> If you don't mind loosing the running workflows, cleaning the 2  
> workflow workspaces ("Expressions" and "Store") could help; you could  
> do this through the jcr browser, reconfigured to use these workspaces.
> 
> -g
> 
> On Sep 17, 2008, at 10:55 AM, rainer wrote:
> 
>>
>> thx for answering.
>>
>> We made the superuser a member of the publishers group, whoch was not
>> imported by the MagnoliaUpdater - we had to import it manually.
>>
>> Yes, there were running WFs.
>>
>> The definitionID is always the same.
>> (also after after second run of migration - we started again - same  
>> result)
>>
>> We are using the default Magnolia WF "activation".
>>
>> hmmm... does this further information help.
>>
>>
>>
>>
>>
>>
>> Magnolia - User mailing list wrote:
>>>
>>>
>>> On Sep 17, 2008, at 9:09 AM, rainer wrote:
>>>
>>>>
>>>> hi list,
>>>>
>>>> we just migrated from 3.0 to 3.5.8 and now the inbox is always  
>>>> empty.
>>>
>>> Since 3.5, the default workflow definition assigns activation items  
>>> to
>>> the "publishers" group, and also since 3.5, the superuser is a member
>>> of this group by default. This is the most common reason for having  
>>> an
>>> inbox that stays empty. One of the intentions is to avoid the  
>>> tendency
>>> of doing everything as superuser.
>>>
>>>> In the Logs we get the following (at every workflow event):
>>>>
>>>> org.apache.jackrabbit.core.ItemManager 16.09.2008 14:11:40 -- node  
>>>> at
>>>> /owfe/activation/MetaData has invalid definitionId (-349493662)
>>>>
>>>> I dont even know what a "definitionId" is good for.
>>>
>>> Did you have running workflows when you migrated? Did you have a
>>> custom wf definition? Does the "invalid definitionId" always have the
>>> same id in your logs ?
>>>
>>> -g
>>>
>>> ----------------------------------------------------------------
>>> for list details see
>>> http://documentation.magnolia.info/
>>> ----------------------------------------------------------------
>>>
>>>
>>
>> -- 
>> View this message in context:
>> http://www.nabble.com/WF-doesnt-work-after-Migration-to-3.5.8-tp19526513p19527765.html
>> Sent from the Magnolia - User mailing list archive at Nabble.com.
>>
>>
>> ----------------------------------------------------------------
>> for list details see
>> http://documentation.magnolia.info/
>> ----------------------------------------------------------------
> 
> 
> ----------------------------------------------------------------
> for list details see
> http://documentation.magnolia.info/
> ----------------------------------------------------------------
> 
> 

-- 
View this message in context: 
http://www.nabble.com/WF-doesnt-work-after-Migration-to-3.5.8-tp19526513p19532440.html
Sent from the Magnolia - User mailing list archive at Nabble.com.


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

Reply via email to