[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: VFS and directory handling

[scott.stark@jboss.org]

The only more generic way that would allow for compatibility modes would be to rely on the content-type rather than the url. However, no one uses that. They look at the url scheme or the file suffix and make assumptions about what the url points to, or its InputStream.

There are standard content-type descriptions for a zip input stream, but I don't know about a java.io.File object. Maybe there is an application/x-java-object-java.io.File type defined somewhere.

A nested jar should simply be seen as a JarInputStream. 

"http://java.sun.com/javaee/5/docs/api/javax/persistence/spi/PersistenceUnitInfo.html" wrote : 
  | getJarFileUrls
  | 
  | List getJarFileUrls()
  | 
  |     Returns a list of URLs for the jar files or exploded jar file directories that the persistence provider must examine for managed classes of the persistence unit. Each URL corresponds to a named element in the persistence.xml file. A URL will either be a file: URL referring to a jar file or referring to a directory that contains an exploded jar file, or some other URL from which an InputStream in jar format can be obtained.
  | 
  |     Returns:
  |         a list of URL objects referring to jar files or directories.
  | 


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154262#4154262

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154262