Lazy Load Panel at runtime from another jar

[cole]

I have simple plugin frame work for my app. I load plug-in's at startup. What
I would like is to have the plug-in supply a panel for exposing the plugin's
functionality. So a wicket page loads, the app determines if pluginA is
available and calls, pluginA.getPanel(). pluginA is in a separate jar, the
class and html file. When the application runs I get :
(UrlResourceStream.java:108) - cannot convert url:
jar:file://localhostc:/foo/extenders/pluginA.jar!/pluginA.html to file (URI
is not hierarchical), falling back to the inputstream for polling

I'm not sure if the resource loader is finding the html file or it simply
cannot load the html file. Is this a classpath issue or do I need to do
something special to allow loading panels from jar's at runtime.
-- 
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Lazy-Load-Panel-at-runtime-from-another-jar-tp3026325p3026325.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Lazy Load Panel at runtime from another jar

[Jeremy Thomerson]

On Wed, Nov 3, 2010 at 6:22 PM, cole cmilli...@comcast.net wrote:


 I have simple plugin frame work for my app. I load plug-in's at startup.
 What
 I would like is to have the plug-in supply a panel for exposing the
 plugin's
 functionality. So a wicket page loads, the app determines if pluginA is
 available and calls, pluginA.getPanel(). pluginA is in a separate jar, the
 class and html file. When the application runs I get :
 (UrlResourceStream.java:108) - cannot convert url:
 jar:file://localhostc:/foo/extenders/pluginA.jar!/pluginA.html to file (URI
 is not hierarchical), falling back to the inputstream for polling

 I'm not sure if the resource loader is finding the html file or it simply
 cannot load the html file. Is this a classpath issue or do I need to do
 something special to allow loading panels from jar's at runtime.


It must be classpath / classloader related, although I haven't seen that
error and don't know what it means without digging in more.

HTML panels are loaded from jars all the time.  Every time you use a
DataTable or a FeedbackPanel or dozens of other Wicket components, you're
loading HTML from a (wicket) jar.

-- 
Jeremy Thomerson
http://wickettraining.com
*Need a CMS for Wicket?  Use Brix! http://brixcms.org*