I am trying to see feasibility of getting rid of the VDB Service,
metadata service and make the logged in user's VDBMetaData available in
all the places that VDBService was used in JCA branch so that it is
inline with other services in JCA branch. For its access I could use
- static access (yuck..)
- bean injection (like parameter passing, like now)
- JNDI lookup
- ThreadLocal (in the DQPWorkContext)
where VDBMetadata will give you all the info needed on the VDB user
logged in. I am leaning toward ThreadLocal, as it is non-intrusive on
the APIs, not sure if increases any memory requirements.
What do you think?
Show replies by thread