How to find current Page Name in generator?

Hi,

I have requirement to find and populate the current page name in a datum.

So can any body please assist, Is it possible through generator property context or is there any other approach available ??

Find more posts tagged with

Comments

sahu

If you are looking for current page url check page token

$PAGE_LINK[page]

smis21

Hi,
Thanks for Reply.

Actually we have requirement that we have to populate datum from result which comes on basis of current page name so I want to get current page name in Generator class itself using PropertyContext or any other mean.

Adam Stoller

Hi,
Thanks for Reply.

Actually we have requirement that we have to populate datum from result which comes on basis of current page name so I want to get current page name in Generator class itself using PropertyContext or any other mean.

Maybe I'm wrong here - as I haven't done any real SP/LS development work - but aren't the datum's specifications for collecting / rendering information in a component? If so - since a component can be associated with multiple pages - I don't think you'd be able to get the "current page" information in the "datum" section of a component - i.e. it sounds a bit like putting the cart before the horse. Or am I missing something here?

smis21

Getting Current Page name means where component is currently added, And We can get it using RequestContext.getPageName(); in externals, I want similar functionality in Generators.

tec_iwov

take a look at com.interwoven.livesite.runtime.RequestContext

smis21

Hi,

Thanks for reply, Problem is RequestContext is not accessible in Generators.
Generator Object takes PropertyContext as a Parameter.
So is there any work around on this.

Kouala

Hi Guys,

Almost 2 years from that original post.
I was wondering if any one found a solution to that PropertyContext missing request context information?

I have same requirement to generate a list of styles, based on an XML configuration file (list of name value pairs options) local to a workarea.

Each component could have it's own config file (or section in the main config file) and therefore can be specific for each workarea/branch.
Component still needs to keep its generic way for re-usability anywhere else if we follow the same principle of having a configuration file to inject style classes in the skin.

So basically I would need to retrieve the component name in the custom generator class so that I can build a path to the configuration file to open(or Xpath if a main configuration file holding all components option lists) .

As the PropertyContext doesn't have much in it about 'context', I wonder if there is a way to pass a param to the Generator, like a Token, available to pass this information to the generator class.

Or maybe you have other suggestions to have these dynamic style lists in the appearance properties?

Thanks in advance for any idea

Garth McMillan

I raised a support ticket with Autonomy in May 2013 about the inability to get context information within a Generator. After 2 months of back-and-forth all I ended up with was "I have checked with internal team and The function your trying is not possible.Please take the help of our professional services team."

I'm pretty certain the PropertyContext is broken but like many other broken things, Autonomy don't want to know about it.