Implementation of custom Page Token

I am using TeamSite/LiveSite (7.1) and wish to implement a custom Page Token.
I see from the docs on autonomy that this is something that's available OOTB.
I've looked at FAQ (https://customers.autonomy.com/support/secure/docs/FAQ/Interwoven/64899.html)

So I created my own PageTokenVariableCustom.java file and placed it in:
\local\config\lib\content_center\livesite_customer_src\src

I also edited the file customer-resource-config.xml that lives under:
\local\config\lib\content_center\livesite_customer_src\etc\conf\livesite_customer\resources

But I am having trouble getting the bean registered, the example given in the FAQ looks incomplete. I am looking for an example of how that bean definition should look for a custom class of your own.
Thanks.

Find more posts tagged with

Comments

Rick Poulin

Unfortunately, they implemented this as a constructor argument to a parent factory object, instead of making it a normal property. That means you can't just extend the object and merge your new options into the existing ones. You have to 'override' the entire bean. Copy the sample from ApplicationContainer/default/deploy/iw-preview.war/WEB-INF/conf/livesite/resources/rendering-resource-config.xml into your customer-resource-config.xml, and change the bean id to "customer.livesite.PageTokenFactory". That file should contain a commented-out sample of how to add your extra tokens.

tbkeith

Unfortunately, they implemented this as a constructor argument to a parent factory object, instead of making it a normal property. That means you can't just extend the object and merge your new options into the existing ones. You have to 'override' the entire bean. Copy the sample from ApplicationContainer/default/deploy/iw-preview.war/WEB-INF/conf/livesite/resources/rendering-resource-config.xml into your customer-resource-config.xml, and change the bean id to "customer.livesite.PageTokenFactory". That file should contain a commented-out sample of how to add your extra tokens.

Hi Rick, thanks for quick reply.
I copied that over and renamed the id but that didnt work, so I just left it as it was "livesite.PageTokenFactory" and then added the custom for my Custom token and that seemed to work for me, hopefully I've not stopped anything else working?

Do you know where tokens can be used? Is it only in components? I tried adding to the page title (from Page Settings dialog) but that didn;t work.

Rick Poulin

Do you know where tokens can be used? Is it only in components?

Components (either in the data or in the XSL) and page-level XSL (e.g. fixed-layout.page.xsl).

The title and page injection and a few other things are tokens themselves, and tokens are not recursively evaluated, which is why it didn't work for you.

mailing_labels.rptdesign

tbkeith

Thanks, yes that makes sense.
I'm thinking that the way forward for that would be to create an external Java class to execute during workflow that will look for tokens in metadata and replace them.

Rick Poulin

If you do it in workflow, you'll only do the substitution once and it'll stick forever (because the token will no longer be there), so that may not be what you're looking for.

Instead, if you're using the LiveSite runtime, you can write a page controller to do this substitution at runtime, thereby ensuring that the substitution is always current.

tbkeith

Thanks for your help Rick, I will take a look at Page controllers.