I want to implement a caching mechanism on the business tier, perhaps with a Value List Handler.
Couple of questions:
1) I've got my class diagram, more or less, at the 'specification level' (Fowler's UML Distilled). I'm doing my best to keep it technology independent. But, leaving out certain information, such as what type of caching i'm implementing seems to add confusion to the diagram rather than make it simpler to read. How are people handling this? Are you specifying stateless and stateful components, facades, caching, etc in the class diagram? Or is it more 'conceptual'?
2) The
J2EE blueprints docs on VLH do not seem to handle multiple threads accessing the cache simultaneously, which would be the case for a common cache. I can think of several good solutions, but i'm not sure of the detail in which i need to address this.
Any help is appreciated. Thanks.