Dear Sven,
I have done some investigation on this topic. Due to the fact that one shouldn't access the HttpRequest in a webdynpro application, consquently one shouldn't access the underlying Servletcontext as well.
In order to store data in memory for usage as e.g. valuehelp content like in a project i am working on there are 2 possibilities:
1) implement a portal service that holds the cache in a private member variable, but provides accessor methods for it.
public class ContextService implements IContextService{
private IServiceContext mm_serviceContext;
private Properties mm_applicationCache;
/**
*/
public void init(IServiceContext serviceContext){
mm_serviceContext = serviceContext;
CrtClassLoaderRegistry.addClassLoader(this.getKey(), this.getClass().getClassLoader());
}
public Properties getCache(){
return mm_applicationCache;
}
tro call the Service in WD.
====================
IContextService portalservice=(IContextService)WDPortalUtils.getServiceRefrence(IContextService.KEY);
portalservice.getCache();
2) the second solution (which i am not going to implement) is using Entity Beans, that hold the Applicationcontext Information. you would access these with SessionBeans (preferrably stateless) that in turns are used as Webdynpromodells (Command bean approach).
best regards,
Juergen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.