6816 2009-04-16 10:14:22 +0000 Resources loading: slight inconsistency in the code 2009-04-20 11:36:02 +0000 1 1 1 Unclassified mobileOK Basic checker Java Library unspecified Other All RESOLVED FIXED P2 enhancement --- 6815 1 fd abel.rionda oldest_to_newest 24759 0 fd 2009-04-16 10:14:22 +0000 Not a bug per se, but the library uses two different ways to load resources: 1. through a call to getClass().getResourceAsStream() in MobileOKCatalog and XhtmlContent to resolve entities. 2. through a call to getClassLoader().getResourceAsStream() in DOMUtils to resolved XSLT stylesheets. That is almost the same thing, but there is a slight difference on the way paths are handled (absolute vs. relative). Sticking to one convention seems a good idea. For an explanation of the difference, see, e.g.: http://www.javaworld.com/javaworld/javaqa/2003-08/01-qa-0808-property.html?page=2 The convention to use depends on how we resolve bug 6815 to allow for more flexibility in XSLT paths. First one is probably better 24849 1 fd 2009-04-20 11:36:02 +0000 Resolution of bug 6815 de facto fixed the inconsistency: getClass().getResourceAsStream() is used throughout the mobileOK Checker.