Hi Jan,
I created
https://glassfish.dev.java.net/issues/show_bug.cgi?id=9103
The root of the problem is clearly not caused by something in the webstack. I didn't figure out why the classpath contains a wrong jar file (foo-ejb.jar instead of the directory foo-ejb_jar).
But now, the loading of the web-module logs a non-fatal warning, and the web-module is deployed (but unusable due to non-finished initialization). I see two options:
1. TldScanner.java catches the error about non-existing jar, and continue to do its work
2. If TldScanner can not complete its work, the module should not be loaded.
Let me know if something is unclear.
- Johan
[Message sent by forum member 'johanvos' (johanvos)]
http://forums.java.net/jive/thread.jspa?messageID=360040