As it turns out, rewriting the code was a better option than manually exploding the .sar file each time, so that is what we did. The underlying code was using classLoader.getResource(filename) which we were able to change to classLoader.getResourceAsStream(filename) The first call gets a URL, and the second an Input Stream. When the first bit of code is called with "bar.xml", it fails while looking for: C:\jboss-4.0.1sp1\server\default\tmp\deploy\tmp20951foo.sar-contents\bar.xml It can't find the file, because it is not unpacked into the temp directory..
The second one finds the file, without looking in the temporary directory, by getting it directly from foo.sar. I still don't know why the .ear file is fully exploded into it's temporary directory, and the .sar file is only partially exploded (only .jar files.) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883738#3883738 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883738 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
