Docs for PostRenderingProcessor

Where can I find documentation on com.interwoven.livesite.model.page.PostRenderingProcessor which I seem to need to use to change how links are generated?

I've searched the support site and these forums without any luck.

I basically want to remove the html/sitename prefix on generated URLs but do NOT want to (completely) change where the generated HTML is placed (via changing the PLC workflow). Ideally, the workflow should store into workarea/html but the links should just begin with / (not /html/sitename)

Find more posts tagged with

Comments

Rick Poulin

Well this is a non-trivial and not entirely supported customization.

The supported (and safest) option is to write a post-processing task in your workflow, that executes right after the generation step.

If you want this integrated directly into the LiveSite engine, your best bet is to extend the RequestContext (whichever implementation of it you're using in your context) and change the definition of getPageLink() and related methods. Non-trivial, and not exactly supported, but it works.

WGM

Does doing this as a "post-processing task" mean that the post processor will need to parse HTML?

I'd rather not go that route.

Rick Poulin

In that case, I'm not sure what you thought the PostRenderingProcessor was going to do for you.. It's basically the same idea (html parsing) but hooked directly into the LiveSite engine.

WGM

Without docs, I wasn't sure at what level the PostRenderingProcessor was manipulating the output (before or after HTML generation). From the name, I assumed that it would be operating on the HTML which I would rather not do as I have always found parsing HTML problematic unless there is some specific token consistently used.

I'll check into the RequestContext suggestion as that seems more specific...

Need to search for documentation on it...

Rick Poulin

WGM wrote:
Need to search for documentation on it...

You won't find any, again because this customization isn't exactly supported.

The approach (for an LSDS runtime, at least) is to extend the RuntimeRequestContext with a custom class that overrides at least the getPageLink() method, and optionally getAjaxURL() and getSubmitURL() as well (because they behave similarly). Then, you tell LiveSite to yours your class by declaring a bean like this:

<bean id="customer.runtime.requestContext" class="com.mycompany.MyCustomRequestContext" scope="prototype" />

By doing this, you're changing both the behaviour of externals that would call context.getPageLink() and also the $PAGE_LINK[] tokens.

Presumably, making this change to the page generation would be fairly similar.