Targeting - Extending Request Context

interDev

Hi,

 

I want to extend the Default Request Context and then want to use the new Request context in my Targeted components. I can create a new wrapper (com.interwoven.livesite.runtime.impl.MyRequestContextWrapper) which will be an implementation of com.interwoven.livesite.runtime.RequestContextWrapper Interface.

 

 

Now two question:

 

1. IN which config file I will have to define the bean for this wrapper class? Will it be in customer-resource-config.xml file?

 

<bean id="runtime.RequestContextWrapper" class="com.interwoven.livesite.runtime.impl.MyRequestContextWrap per" scope="prototype"/>

 

 

2. How do I call this new wrapper context (MyRequestContextWrap

) in my code. OOTB we get RequestContext object in any Livesite code, how do I replace that RequestContext with the MyRequestContextWrapper or will it be replaced automatically due to above bean definition.  

 

TS/LS 7.3.2.

 

TIA

Kalam

Hi,

 

1) Yes, you will need to define the bean in the livesite_customer\resources\customer-resource-config.xml.For example the entry should look like

 
  <bean id="customer.runtime.RequestContextWrapper" class="com.interwoven.livesite.sph.rules.conditions.MyRequestContextWrapperint"/>
</beans>

 

 

2)

i have a class MyRequestContextWrapperint 

package com.interwoven.livesite.sph.rules.conditions;
import javax.servlet.http.HttpServletRequest;
import com.interwoven.livesite.common.web.CookieUtils;
import com.interwoven.livesite.runtime.UserSession;
import com.interwoven.livesite.runtime.impl.BaseRequestContextWrapper;

public class MyRequestContextWrapperint extends BaseRequestContextWrapper {
    public int   getCookieInt(String cookieName) {
        
        UserSession session = mRequest.getSession();
        String amount = (String)session.getAttribute("amount");
        System.out.println("getCookieInt amount value is "+ amount);
        int amount1= Integer.parseInt(amount);
        System.out.println("Amount is "+amount1);
        return amount1;
        
    }
}

 

I have used this in the condition  for which the verbalization file looks like below

 

 

<?xml version="1.0" encoding="UTF-8"?>
<Verbalization Version="1">
  <Bundle>com.interwoven.livesite.rules.values</Bundle>
  <Category i18nKey="category.cookieInt"/>
  <Label i18nKey="value.cookieInt" />
  <RulesXslTemplate File="templates/conditions/session-amount.xsl"/>
  <Constants>
    <UserInput InputId="bean.path" Control="hidden"><Value Type="String">wrapper</Value></UserInput>
    <UserInput InputId="bean.method" Control="hidden"><Value Type="String">getCookieInt</Value></UserInput>
    <UserInput InputId="xml.path" Control="hidden"><Value Type="String">Wrapper/CookieInt</Value></UserInput>
  </Constants>
  <Paragraph Id="paragraph" SentenceSelection="fixed">
    <Sentence Id="sentence">
      <Clause>
        <Structure i18nKey=".cookieInt"/>
        <UserInput InputId="input.cookieIntName" Control="textfield"/>
      </Clause>
      <Clause Include="includes/conditions/generic-number.xml"/>
    </Sentence>
  </Paragraph>
</Verbalization>

 

When you give the wrapper as the beanpath, it will look for a class which extends the RequestContextWrapper.

 

Please let me know if anything i can help.

 

Basically we extend the RequestContextWrapper object when we need the anonymous targeting. For user based targeting we need to extend  the UserProfile object which is little more lengthy process.

 

 

 

Thanks

Kalam