Hello [~manovotn],
Yes, you are correct we are running in weblogic. But I do not have any zip file in classpath I just have a jar file. If beans.xml is part of jar file, weblogic classloader scanner returns zip prefix for every classpath resource it find inside the jar file. It's just how weblogic works.
Same issue is documented in spring as well:
https://docs.spring.io/spring/docs/3.0.0.RC2/spring-framework-reference/html/ch04s07.html
section 4.7.2
... the resolver follows a more complex but defined procedure to try to resolve the wildcard. It produces a Resource for the path up to the last non-wildcard segment and obtains a URL from it. * * If this URL is not a "jar:" URL or container-specific variant (e.g. "zip:" in WebLogic, "wsjar" in WebSphere, etc.), * * then a java.io.File is obtained from it and used to resolve the wildcard by traversing the filesystem. In the case of a jar URL, the resolver either gets a java.net.JarURLConnection from it or manually parses the jar URL and then traverses the contents of the jar file to resolve the wildcards.
Since the project code is internal, I can not share it. But let me try to get this reproduce in small poc project and attach to bug.
Thanks,
Latesh |
|
