[Spring-beandoc-user] Bug with classpath: access; Suggestion: WARs, EARs

[Hans-Peter S. <Han...@t-...>]

Hi!

Thanks for the development of spring-beandoc! This is a very valuable 
tool for the spring developer.

Just two suggestions. First, accessing spring configurations via the 
classpath: does not seem to work, since spring-beandoc often tries to 
use the File for the Resources - which does not exist, of course. 
Exceptions like

java.io.FileNotFoundException: class path resource [meldung.xml] cannot 
be resolved to absolute file path because it does not reside in the file 
system: 
jar:file:/D:/WITA/source/eai/blw/wita-eai-blw-meldung/target/wita-eai-blw-meldung-1.100.5.0.jar!/meldung.xml

do result. It works in the junit-tests, since the classpath: resources 
are included as class folder, but it does not work when the resources 
are included as a jar.

Second, it would be nice to extract the spring-configuration from a WAR 
/ EAR-File. This would require accessing the jar files within the WAR / 
EAR. This is rather low priority, though, since it is not too difficult 
to unpack it by hand. Currently with the classpath: bug you have to 
unpack the war *and* then unpack the individual jars... Ouch!

Thank you!

Best regards,

Hans-Peter Störr