I double checked, & the html & class files are indeed in the folder (see 
image below):



Heres the error message:

2012-11-14 09:50:31,875 [ajp-10002-3] ERROR - Markup of type 'html' for 
component 
'com.uprr.ecm.wicket.components.panels.location.PointLocationPanel' not 
found. Enable debug messages for org.apache.wicket.util.resource to get a 
list of all filenames tried.: [MarkupContainer [Component id = 
switch-location]]
org.apache.wicket.markup.MarkupNotFoundException: Markup of type 'html' 
for component 
'com.uprr.ecm.wicket.components.panels.location.PointLocationPanel' not 
found. Enable debug messages for org.apache.wicket.util.resource to get a 
list of all filenames tried.: [MarkupContainer [Component id = 
switch-location]]
                 at 
org.apache.wicket.markup.MarkupCache.getMarkupStream(MarkupCache.java:227)
                 at 
org.apache.wicket.MarkupContainer.getAssociatedMarkupStream(MarkupContainer.java:351)
                 at 
org.apache.wicket.MarkupContainer.renderAssociatedMarkup(MarkupContainer.java:654)
                 at 
org.apache.wicket.markup.html.form.FormComponentPanel.onComponentTagBody(FormComponentPanel.java:223)
                 at 
org.apache.wicket.Component.renderComponent(Component.java:2690)
                 at 
org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1539)
                 at 
org.apache.wicket.Component.render(Component.java:2521)

Though I don't think it's significant, but our main app does have some 
code (below) that tells Wicket to look in an additional location for HTML 
files. But I don't that's causing the problem, because Wicket is finding 
HTML files in *other* JARs. This is a puzzler.

final IResourceSettings resourceSettings = getResourceSettings();
        resourceSettings.addResourceFolder("WEB-INF/html");
        resourceSettings.setResourceStreamLocator(new PathLocator());



From:   Martin Grigorov <mgrigo...@apache.org>
To:     users@wicket.apache.org
Date:   11/14/2012 09:29 AM
Subject:        Re: Finding HTML Markup in External JARs



Hi,

I'm 99% certain that the .html files are not in the .jar.
Double check that they are actually packed with the .class files.


On Wed, Nov 14, 2012 at 5:26 PM, Richard W. Adams <rwada...@up.com> wrote:

> 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.
> **
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com <http://jweekend.com/>



**

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.
**

Reply via email to