>
> Hmm, I guess I should experiment and see if a url like
> jar:jar:http://.../myrar.rar!/path/myjar.jar!/ works to get to the jar
> inside a rar... maybe we don't need to unpack these things.
>
> Scott, does the idea of a mbean providing "where the local filesystem is"
> fit in better to your "securable resource" idea than looking up
> jboss.system.home and accessing the filesystem? Can you be more specific
> about what the interface to this system would look like? Would you get
> files out of it?
>
I'm more inclined to access "jboss/system/home" from JNDI and have this
be setup as a filesystem context using the ExternalContext mbean. The
interface should be a JNDI DirContext that has attributes for the things one
normally obtains from a file. For example, take the
jboss/system/home/db/jbossmq/QUEUE.A.dat29 file as a DirContext and
there could be the following attributes
+ QUEUE.A.dat29
| -- lastModified = Date of last modification
| -- size = size of file in bytes
| -- in = java.io.InputStream for reading the file
| -- out = java.io.OutputStream for writing the file
| etc.
This would require a file system provider implementation for use by JBossNS.
The Sun provider does not provide this File independent view of the
filesystem.
Alternatively, how would the J2EE connector APIs work for exposing a
filesystem?
> I'm going to commit (after a couple more tests) what I have now that uses
> the jboss.system.home directly, so we can play with it, and hopefully a
> better solution will emerge soon.
>
Fine for now. However, everyone needs to be thinking about how to limit
dependency on the filesystem.
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development