[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Remaing classLoader changes

[adrian@jboss.org]

"alesj" wrote : "scott.stark at jboss.org" wrote : One difference in behavior I'm seeing that we don't appear to have control over is duplicate resource ordering.
  |   | 
  | OK, I must admit I'm not entirely following the discussion. :-)
  | But has this got to do something with this:
  | 
  |   | 2008-01-22 17:37:32,796 TRACE [org.jboss.seam.as5.vfs.VFSScanner] Root url: vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta4/server/default/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/jboss-seam-debug.jar/seam.properties
  |   | 2008-01-22 17:37:32,796 TRACE [org.jboss.seam.as5.vfs.VFSScanner] File: C:\projects\jboss5\trunk\build\output\jboss-5.0.0.Beta4\server\default\deploy\jboss-seam-booking.ear\jboss-seam-booking.war\WEB-INF\lib\jboss-seam-debug.jar\seam.properties
  |   | 2008-01-22 17:37:32,796 TRACE [org.jboss.seam.as5.vfs.VFSScanner] URL: file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta4/server/default/deploy/jboss-seam-booking.ear, relative: jboss-seam-booking.war/WEB-INF/lib/jboss-seam-debug.jar/seam.properties
  |   | 
  |   | 2008-01-22 17:37:33,687 TRACE [org.jboss.seam.as5.vfs.VFSScanner] Root url: jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta4/server/default/tmp/deploy/jboss-seam-booking19541-exp.war/WEB-INF/lib/jboss-seam-debug.jar!/seam.properties
  |   | 2008-01-22 17:37:33,687 TRACE [org.jboss.seam.as5.vfs.VFSScanner] File: file:\C:\projects\jboss5\trunk\build\output\jboss-5.0.0.Beta4\server\default\tmp\deploy\jboss-seam-booking19541-exp.war\WEB-INF\lib\jboss-seam-debug.jar!\seam.properties
  |   | 2008-01-22 17:37:33,687 TRACE [org.jboss.seam.as5.vfs.VFSScanner] URL: null, relative: file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta4/server/default/tmp/deploy/jboss-seam-booking19541-exp.war/WEB-INF/lib/jboss-seam-debug.jar!/seam.properties
  |   | 
  | I do a ClassLoader.getResources("seam.properties") inside Seam app, and I'm not expecting any non vfs URLs.
  | Where does that 'jar:file' come from?

No. As I told you last week, this is showing that both the original and the tmp jar are being added
to the list of VFS files/urls in the classpath. You need to determine what is doing this.

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

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