Hi Wouter,
It could be that you are better of writing an (postcontent) event
trigger than an extractor. Extractors have a very spefic purpose, ie
they get the content of a document and return a list of extracted
properties. Extractors don't have repository 'access'.
Regards,
Bart
Wouter Zelle wrote:
Hi Ard,
Let me answer your questions:
> your extracted values depend on another resource: what if this
> resource changes?
Translation changes will have to be managed carefully, since this may
require a update xslt for the content. The extracted and translated
properties can fairly easily be updated by touching every file in the
repository (during off hours). So I don't see a problem here assuming
every change to the translations is done carefully.
> Secondly, how can you be certain the current user actually has
> read rights on another resource from within an extractor.
The translation document is also used to set the original values for the
content. So editing the document will fail before the extractor comes
into play, if the editor cannot access the translation document.
We have considered the various options carefully and they all have their
problems. I think that the extractor solution is reasonable, assuming we
can retrieve the translation document properly.
Regards,
Wouter
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Ard Schrijvers
Sent: Wed 4/16/2008 12:18 PM
To: Hippo CMS development public mailinglist
Subject: RE: [HippoCMS-dev] Repository access from extractor
Hello Wouter,
I suppose you are implementing this in the repository, isn't? I have
never fetched another repository resource from within an extractor, and
IMHO, this is a bad idea. First of all, your extracted values depend on
another resource: what if this resource changes? Secondly, how can you
be certain the current user actually has read rights on another resource
from within an extractor. I strongly advice you to reconsider your way
to implement this feature (or explain what you would like to achieve).
Regards Ard
> Hi everyone,
>
> I'm trying to create an extractor that will get a value from
> the XML and then do a translation before putting the value in
> a property. The challenging part is that the translation
> document is stored in the repository and will need to be
> retrieved. I think I need a ServiceManager so I can get a
> SourceResolver from it (which I can use to retrieve the
> translation document). I've implemented the Serviceable interface:
>
> public void service(ServiceManager serviceManager) throws
> ServiceException;
>
> I don't know how/where to configure the repository so the
> ServiceManager will actually be injected into the extractor.
>
> Can anyone help me with this?
>
> Wouter Zelle
> ********************************************
> Hippocms-dev: Hippo CMS development public mailinglist
>
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
--
Hippo B.V. - Amsterdam
Oosteinde 11, 1017 WT, Amsterdam, +31(0)20-5224466
Hippo USA Inc. - San Francisco
101 H Street, Suite Q, Petaluma CA, 94952-3329, +1 (707) 773-4646
-----------------------------------------------------------------
http://www.onehippo.com - [EMAIL PROTECTED]
-----------------------------------------------------------------
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
