OK, I've got it figured out. The packaging question is a red herring. A.jar depends on MANY Class files in B.jar, but it turns out that only one Class was causing a problem. This particular Class in B.jar is a public static inner interface, a rather unusual and rare programming choice. While this is legit and should work, it's not surprising that no one else has seen this.
I just broke out the inner interface into it's own proper .java file and everything deploys correctly. Sincere thanks to all for reading and responding. -Eric View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3853199#3853199 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3853199 ------------------------------------------------------- This Newsletter Sponsored by: Macrovision For reliable Linux application installations, use the industry's leading setup authoring tool, InstallShield X. Learn more and evaluate today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
