This content has been marked as final. Show 3 replies
using JNDI only global scope component can be resolved,
for resolving session components you need to use DynamoRequest.resolveName
you cannot resolve request scope component either with JNDI lookup or NucleusResolverUtil
If I use same code in application 1 (which have ATG servlet pipelint) it works,
Only thing is this is not working in application which don't have ATG servlet pipeline in the web.xml
It seems the scheduler global component is resolving the request scope component internally.
For request scope components there should be DynamoHttpServletRequest object in context to resolve.
DynamoHttpServletRequest object is created as part of servlet pipeline.
As you request is not going thru servlet pipeline, there is no DynamoHttpServletRequest and hence the request scope components cannot be resolved.
So check in the scheduler why do you need to resolve the request scope component. Its not good practice to resolve them in schedulers.