I've been trawling the archive again on ways to manipulate the page
activation context and break up the parameters.
The specific scenario I'm working on is that of 'hijacking' part of the
activation context by a transformation worker or similar.
For example, I'd like to be able to define a page class like:
@ContentDrivenPage
public class ArticlePage {
@PageActivationContext
private String myParam;
}
For pages with this annotation, I'd like the first part of the page
activation context to be intercepted by another component, and maybe put
into the Environment stack/service after some specific processing.
An example url might be:
/mycontext/mypage/document_id/myparamstring
(where document_id would be the intercepted value that the page never
sees)
Does this make sense, and is it achievable? One potential problem is
that the hijacked activation component would still need to end up back
in the url in onPassivate().
Another way to think of this is potentially as a hierarchy of page
classes each of which is interested in progressively more detail on the
url...
public class ArticlePage extends CmsDrivenPage {
@PageActivationContext
private String myParam;
}
public class CmsDrivenPage {
@PageActivationContext
private String documentId;
}
Thanks, Alfie.
