GenerateHTML not calling SiteController/PageController

We have implemented a sitecontroller which does update the pagescope and that value used in a page-layout.
This is working with .pages

However we have a model, which uses generatedHtmls of these pages(through workflow), for which sitecontroller is not invoked and hence the value is not getting rendered in page-layout.
Even i tried with PageController, but no luck. i.e, not invoked.

GenerateHTML task is mapped with OOTB class com.interwoven.livesite.workflow.web.task.PageConversionWebTask.

Any alternatives to call site-controller, from this GenerateHTML OOTB task?
Or At least, is there a way to get com.interwoven.livesite.runtime.RequestContext object in workflow tasks?

Pls. let me know if need more information.

Find more posts tagged with

Comments

Rick Poulin

It should be getting called but it might be failing to return the results you expect. The RequestContext passed as input will be slightly different, so you should check your server logs for stack traces or add additional debugging into your code.

If you still get nowhere, post your environment details.

Anil Kumar

TS7.3.1 + SitePublisher7.3.1 + WFM7.3.1

SiteController code is attached, which is configured at default.site

Garth McMillan

Yes, the controller should get called when generating .HTML from a .PAGE.

Is debugging set up for your com.livesite.controllers namespace? If you change Log.debug('****') to System.out.println('****') do you get something in iwjboss_server_out.log or content_center.log?

Anil Kumar

Logger is working, when it is a .page and not working for .html

I tried, syso.out, but no luck.

I assume, Generate HTML task, is not reading(in the java code) controllers attached to the site/ page, its just majorly converting XML to HTML as per XSL instructions.

Rick Poulin

I assume, Generate HTML task, is not reading(in the java code) controllers attached to the site/ page, its just majorly converting XML to HTML as per XSL instructions.

But that's not what it should be doing.. I don't exactly have the setup to say for sure, but it looks like my 7.2 server is doing the same but 7.3.2 definitely works, so maybe you might want to upgrade? (definitely not conclusive, but maybe).

Your code could potentially fail on context.getSite() before printing any logging statements.. maybe ad a Log.debug() call as the very first thing in your method and see what happens.