The ejb specs discourage if not prohibit this. Two acceptable ways to access file system objects would be to write a jca connector (no transaction) that handled the access for you, or do the access through an mbean.
You might also be able to use a jndi-filesystem adapter, although I don't know anything about what capabilities that might offer.
Why would you want to access a filesystem from an entity bean?
> Why would you want to access a filesystem from an
> entity bean?
I am attempting to implement the Lucene file-based indexer as a service that can be accessed from any of my client machines. Since the index is file-based, my EJB must be able to access the filesystem for both reads and writes. I am a newbie to EJB and if Entity beans are not the way to go, I could sure use some other suggestions.