'cache some files' sounds like a EJB specification violation.
You should not access from EJB's any file (see http://www.oracle.com/technetwork/java/javaee/tech/index-jsp-142185.html)
If you want to read something like a configuration you should implement a MBean to read the file and provide the information.
And remember that use of a cache should only be implemented if you have detected a bottleneck and measured that it will help.
In my experience caches where implemented without effect (e.g. not often used) or negative effect (e.g. performance reduced or nasty sideeffects)
This is regarding the cache in jboss Application Server...
But the question is still what are the requirements?
What you want to cache? Why you think that a cache should be implemented, performance?
How a jboss cache can be used in standalone,non clustered environments to cache frequently accessed data in memory...
I want to implement the jboss cache in a standalone application,non clustered environments....
i am caching some xml file...
i put that xml file in some jar file and i put that jar file in classpath
but still it is showing the NullPointerException
I am referring to Jboss Cache...
How it makes cache of objects?