You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@lenya.apache.org by simon litwan <si...@wyona.com> on 2005/06/16 14:58:44 UTC
bugfix or enhancement? losing scheduler jobs after paste, rename
url
hi list
i'm working on a customers request about losing jobs after paste/rename
url. they wish the scheduled jobs should move with document. but they
also would be satisfied with a warning on the paste/rename screen that
the jobs will get lost.
for now the jobs get deleted with the anttask while renameurl or move. i
looked/asked around how to move the jobs with the document instead of
just deleting it. but it seems to be a big thing.
now i'm not sure is it worth to do this effort.
WDYT?
on the other hand its quite easy to show a warning. i'm just not sure
how to find out the document AND its children has some jobs. i will look
on it, but maybe someone has a hint.
i just want to know what the community think about the approach with the
warning. is it good enough for lenya?
cheers
simon
--
simon litwan
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
simon.litwan@wyona.com
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: bugfix or enhancement? losing scheduler jobs after paste, rename
url
Posted by Doug Chestnut <dh...@virginia.edu>.
simon litwan wrote:
> Am Donnerstag, den 16.06.2005, 09:43 -0400 schrieb Doug Chestnut:
>
>>I don't know how it works now, but it would also be nice to delete the
>>scheduled job.
>>
>
> i'm not sure i understand your answer.
> the problem is lenya deletes the scheduled jobs. but IMO it should not.
> i think the best would be to move the jobs with the document.
> but for the moment a warning would comply.
> simon
Right, a warning and delete the scheduled job. Sorry, didn't see the
original mail.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: bugfix or enhancement? losing scheduler jobs after paste,
rename url
Posted by simon litwan <si...@wyona.com>.
Am Donnerstag, den 16.06.2005, 09:43 -0400 schrieb Doug Chestnut:
> I don't know how it works now, but it would also be nice to delete the
> scheduled job.
>
i'm not sure i understand your answer.
the problem is lenya deletes the scheduled jobs. but IMO it should not.
i think the best would be to move the jobs with the document.
but for the moment a warning would comply.
simon
> --Doug
>
> Michael Wechner wrote:
> > simon litwan wrote:
> >
> >>
> >> i just want to know what the community think about the approach with the
> >> warning. is it good enough for lenya?
> >>
> >>
> >
> > I think at least a warning would be good if a page is actually scheduled.
> >
> > Michi
> >
> >> cheers
> >> simon
> >>
> >>
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: bugfix or enhancement? losing scheduler jobs after paste, rename
url
Posted by Doug Chestnut <dh...@virginia.edu>.
I don't know how it works now, but it would also be nice to delete the
scheduled job.
--Doug
Michael Wechner wrote:
> simon litwan wrote:
>
>>
>> i just want to know what the community think about the approach with the
>> warning. is it good enough for lenya?
>>
>>
>
> I think at least a warning would be good if a page is actually scheduled.
>
> Michi
>
>> cheers
>> simon
>>
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: bugfix or enhancement? losing scheduler jobs after paste, rename
url
Posted by Michael Wechner <mi...@wyona.com>.
simon litwan wrote:
>
>i just want to know what the community think about the approach with the
>warning. is it good enough for lenya?
>
>
I think at least a warning would be good if a page is actually scheduled.
Michi
>cheers
>simon
>
>
>
>
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: bugfix or enhancement? losing scheduler jobs after paste, rename
url
Posted by Andreas Hartmann <an...@apache.org>.
Thorsten Scherler wrote:
> On Thu, 2005-06-16 at 16:05 +0200, Andreas Hartmann wrote:
>
>>simon litwan wrote:
>>
>>>hi list
>>>
>>>i'm working on a customers request about losing jobs after paste/rename
>>>url. they wish the scheduled jobs should move with document. but they
>>>also would be satisfied with a warning on the paste/rename screen that
>>>the jobs will get lost.
>>
>>[...]
>>
>>That's a good example for a problem caused by mixing concerns -
>>document storage and site structure. If they were separated, the
>>problem would not occur. I suggest that we reconsider storing documents
>>in a non-structured way and implement site structures as views on the
>>document repository.
>>
>
>
> Like I understand the problem: simon wants to move the documents and it
> would be best that the associated jobs as well would be moved, right?
>
> http://marc.theaimsgroup.com/?t=103992708800001&r=1&w=2
>
> When linking the docs in jobs.xml with input modules then that is
> possible.
The key is - as Michi pointed out - a facility to map unique, constant
IDs to documents. Unless we have that, we'd have to add a job-moving
functionality to the scheduler, which is IMO overkill. Re-writing the
URLs in jobs.xml directly violates the job store encapsulation.
I'm -1 to change the current behaviour in 1.2 (unless someone wants to
extend the scheduler), maybe we can add a message like
"Please check the subtree for scheduled jobs as they will get
lost after moving."
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: bugfix or enhancement? losing scheduler jobs after paste,
rename url
Posted by Thorsten Scherler <th...@apache.org>.
On Thu, 2005-06-16 at 16:05 +0200, Andreas Hartmann wrote:
> simon litwan wrote:
> > hi list
> >
> > i'm working on a customers request about losing jobs after paste/rename
> > url. they wish the scheduled jobs should move with document. but they
> > also would be satisfied with a warning on the paste/rename screen that
> > the jobs will get lost.
>
> [...]
>
> That's a good example for a problem caused by mixing concerns -
> document storage and site structure. If they were separated, the
> problem would not occur. I suggest that we reconsider storing documents
> in a non-structured way and implement site structures as views on the
> document repository.
>
Like I understand the problem: simon wants to move the documents and it
would be best that the associated jobs as well would be moved, right?
http://marc.theaimsgroup.com/?t=103992708800001&r=1&w=2
When linking the docs in jobs.xml with input modules then that is
possible.
I agree with Andreas that we should implement site structures as views
on the document repository.
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Unique IDs [WAS:Re: bugfix or enhancement? losing scheduler jobs
after paste, rename url]
Posted by Michael Wechner <mi...@wyona.com>.
Andreas Hartmann wrote:
> simon litwan wrote:
>
>> hi list
>>
>> i'm working on a customers request about losing jobs after paste/rename
>> url. they wish the scheduled jobs should move with document. but they
>> also would be satisfied with a warning on the paste/rename screen that
>> the jobs will get lost.
>
>
> [...]
>
> That's a good example for a problem caused by mixing concerns -
> document storage and site structure. If they were separated, the
> problem would not occur. I suggest that we reconsider storing documents
> in a non-structured way and implement site structures as views on the
> document repository.
I think you can still store the documents in a structured way, but each
document
has a unique ID which is mapped onto the path within the
hierarchy/structure, e.g. by
hashmap. This unique ID (uid) is then being used within the Scheduler or
for references
for instance and not the path itself.
We have built this for a customer of ours and it seems to work pretty well.
I hope that we can contribute the lessons we learned in the near future.
Btw, it seems to me that Jackrabbit is doing pretty much the same thing,
whereas
Jackrabbit is managing this "hashmap", whereas I am not sure if I might
have misunderstood something. For instance I am not sure if one can
access/use the unique
IDs from Jackrabbit and use them within the application. On the other
hand AFAIK
the persistence manager only receices the UIDs.
Anyway, I am pretty conviced that we will be able to solve this problem
within Lenya in the very near future.
Michi
>
> -- Andreas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: bugfix or enhancement? losing scheduler jobs after paste,
rename url
Posted by Thorsten Scherler <th...@apache.org>.
On Thu, 2005-06-16 at 16:05 +0200, Andreas Hartmann wrote:
> simon litwan wrote:
> > hi list
> >
> > i'm working on a customers request about losing jobs after paste/rename
> > url. they wish the scheduled jobs should move with document. but they
> > also would be satisfied with a warning on the paste/rename screen that
> > the jobs will get lost.
>
> [...]
>
> That's a good example for a problem caused by mixing concerns -
> document storage and site structure. If they were separated, the
> problem would not occur. I suggest that we reconsider storing documents
> in a non-structured way and implement site structures as views on the
> document repository.
>
Like I understand the problem: simon wants to move the documents and it
would be best that the associated jobs as well would be moved, right?
http://marc.theaimsgroup.com/?t=103992708800001&r=1&w=2
When linking the docs in jobs.xml with input modules then that is
possible.
I agree with Andreas that we should implement site structures as views
on the document repository.
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Unique IDs [WAS:Re: bugfix or enhancement? losing scheduler jobs
after paste, rename url]
Posted by Michael Wechner <mi...@wyona.com>.
Andreas Hartmann wrote:
> simon litwan wrote:
>
>> hi list
>>
>> i'm working on a customers request about losing jobs after paste/rename
>> url. they wish the scheduled jobs should move with document. but they
>> also would be satisfied with a warning on the paste/rename screen that
>> the jobs will get lost.
>
>
> [...]
>
> That's a good example for a problem caused by mixing concerns -
> document storage and site structure. If they were separated, the
> problem would not occur. I suggest that we reconsider storing documents
> in a non-structured way and implement site structures as views on the
> document repository.
I think you can still store the documents in a structured way, but each
document
has a unique ID which is mapped onto the path within the
hierarchy/structure, e.g. by
hashmap. This unique ID (uid) is then being used within the Scheduler or
for references
for instance and not the path itself.
We have built this for a customer of ours and it seems to work pretty well.
I hope that we can contribute the lessons we learned in the near future.
Btw, it seems to me that Jackrabbit is doing pretty much the same thing,
whereas
Jackrabbit is managing this "hashmap", whereas I am not sure if I might
have misunderstood something. For instance I am not sure if one can
access/use the unique
IDs from Jackrabbit and use them within the application. On the other
hand AFAIK
the persistence manager only receices the UIDs.
Anyway, I am pretty conviced that we will be able to solve this problem
within Lenya in the very near future.
Michi
>
> -- Andreas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: Unique IDs [WAS:Re: bugfix or enhancement? losing scheduler jobs
after paste, rename url]
Posted by Michael Wechner <mi...@wyona.com>.
Andreas Hartmann wrote:
>
> IMO the unique ID should be opaque to the user.
> It can be auto generated on document creation and doesn't have to be
> human-readable.
right, whereas we used the timestamp which gives it a certain meaning.
Michi
>
> -- Andreas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
>
>
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Unique IDs [WAS:Re: bugfix or enhancement? losing scheduler jobs
after paste, rename url]
Posted by Andreas Hartmann <an...@apache.org>.
J. Wolfgang Kaltz wrote:
> Andreas Hartmann schrieb:
>
>> Michael Wechner wrote:
>>
>> [...]
>>
>>> I think you can still store the documents in a structured way, but
>>> each document
>>> has a unique ID which is mapped onto the path within the
>>> hierarchy/structure, e.g. by
>>> hashmap. This unique ID (uid) is then being used within the Scheduler
>>> or for references
>>> for instance and not the path itself.
>
>
> IMO this is mostly a usability problem at document creation time. Right
> now when the user creates a new document in the default publication, she
> has to guess a document id which does not exist in this branch. This is
> not ideal but still acceptable, as typically there will only be a few
> documents within that branch. But if we want the user to provide a
> publication-wide unique id at creation, Lenya will need to propose such
> an id in the creation mask (a sort of auto-increment).
IMO the unique ID should be opaque to the user.
It can be auto generated on document creation and doesn't have to be
human-readable.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Unique IDs [WAS:Re: bugfix or enhancement? losing scheduler jobs
after paste, rename url]
Posted by Michael Wechner <mi...@wyona.com>.
J. Wolfgang Kaltz wrote:
> Andreas Hartmann schrieb:
>
>> Michael Wechner wrote:
>>
>> [...]
>>
>>> I think you can still store the documents in a structured way, but
>>> each document
>>> has a unique ID which is mapped onto the path within the
>>> hierarchy/structure, e.g. by
>>> hashmap. This unique ID (uid) is then being used within the
>>> Scheduler or for references
>>> for instance and not the path itself.
>>
>
> IMO this is mostly a usability problem at document creation time.
> Right now when the user creates a new document in the default
> publication, she has to guess a document id which does not exist in
> this branch. This is not ideal but still acceptable, as typically
> there will only be a few documents within that branch. But if we want
> the user to provide a publication-wide unique id at creation, Lenya
> will need to propose such an id in the creation mask (a sort of
> auto-increment).
The UID is given automatically by the repository layer, whereas the user
can still choose the name or path arbitrarily.
>
> So IMO we need something like Publication.getNewUniqueDocumentId()
> before changing the current id structure, otherwise we will have a big
> usability issue.
>
> But I am not sure where the last used id would be stored ...
the repository layer does all this handling and Lenya would have nothing
to do with it.
The user normally won't see any UIDs
> it would clearly be too inefficient to look at the current documents
> and their ids. Maybe we need to store some new structure, like a
> "publication state node" ? The sitetree doesn't feel right for this.
the sitetree is just a "view" of the various documents.
Michi
>
>
> --
> Wolfgang
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
>
>
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Unique IDs [WAS:Re: bugfix or enhancement? losing scheduler jobs
after paste, rename url]
Posted by "J. Wolfgang Kaltz" <ka...@interactivesystems.info>.
Andreas Hartmann schrieb:
> Michael Wechner wrote:
>
> [...]
>
>> I think you can still store the documents in a structured way, but
>> each document
>> has a unique ID which is mapped onto the path within the
>> hierarchy/structure, e.g. by
>> hashmap. This unique ID (uid) is then being used within the Scheduler
>> or for references
>> for instance and not the path itself.
IMO this is mostly a usability problem at document creation time. Right
now when the user creates a new document in the default publication, she
has to guess a document id which does not exist in this branch. This is
not ideal but still acceptable, as typically there will only be a few
documents within that branch. But if we want the user to provide a
publication-wide unique id at creation, Lenya will need to propose such
an id in the creation mask (a sort of auto-increment).
So IMO we need something like Publication.getNewUniqueDocumentId()
before changing the current id structure, otherwise we will have a big
usability issue.
But I am not sure where the last used id would be stored ... it would
clearly be too inefficient to look at the current documents and their
ids. Maybe we need to store some new structure, like a "publication
state node" ? The sitetree doesn't feel right for this.
--
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Unique IDs [WAS:Re: bugfix or enhancement? losing scheduler jobs
after paste, rename url]
Posted by Andreas Hartmann <an...@apache.org>.
Michael Wechner wrote:
[...]
> I think you can still store the documents in a structured way, but each
> document
> has a unique ID which is mapped onto the path within the
> hierarchy/structure, e.g. by
> hashmap. This unique ID (uid) is then being used within the Scheduler or
> for references
> for instance and not the path itself.
Yes, that is a more precise description. The problem is not that we
store the documents in a structured way, but that we use the structure
information to reference documents.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: bugfix or enhancement? losing scheduler jobs after paste, rename
url
Posted by Andreas Hartmann <an...@apache.org>.
simon litwan wrote:
> hi list
>
> i'm working on a customers request about losing jobs after paste/rename
> url. they wish the scheduled jobs should move with document. but they
> also would be satisfied with a warning on the paste/rename screen that
> the jobs will get lost.
[...]
That's a good example for a problem caused by mixing concerns -
document storage and site structure. If they were separated, the
problem would not occur. I suggest that we reconsider storing documents
in a non-structured way and implement site structures as views on the
document repository.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org