We're enhancing a Wicket app which has been running in production for many months. One of the enhancements was adding a panel to a JAR (which we wrote) used by our app. The new panel works fine on the local workstation under Eclipse/Jetty, but fails when we deploy it to our JBOSS server. Cause: Wicket says it can't find the HTML associated with the Java class, even though the HTML & .class file are in the same folder. If finds HTML markup in *other* JARs, but not the JAR with our new panel. (This panel is the first class with markup we've attempted in this JAR.)
Is there some special configuration or initialization that is required to let Wicket find the HTML inside an external JAR? Version info: Our app uses Wicket 1.4.17 & wicket-extensions 1.4.17. The versions are dictated by our corporate framework, so upgrading to newer versions is not an option for now. ** This email and any attachments may contain information that is confidential and/or privileged for the sole use of the intended recipient. Any use, review, disclosure, copying, distribution or reliance by others, and any forwarding of this email or its contents, without the express permission of the sender is strictly prohibited by law. If you are not the intended recipient, please contact the sender immediately, delete the e-mail and destroy all copies. **
