Hi,

I saw your todo:

on Application.init()

   - getApplicationSettings().setClassResolver(new PluginClassResolver());


Take a look
at org.apache.wicket.Application#getRootRequestMapperAsCompound. You will
have to do something similar with CompoundClassResolver, as Jesse Long
suggested in your other thread.


On Wed, Nov 14, 2012 at 2:16 PM, Decebal Suiu <decebal.s...@asf.ro> wrote:

> Hi
>
> I implemented a plugin framework for wicket that can be found at
> https://github.com/decebals/wicket-plugin
>
> I have a tiny demo application. The demo application is in demo folder. In
> demo/api folder I declared an extension point (Section) that is a tab in a
> wicket TabbedPanel. Each section has an title, an icon and a content (a
> simple text message in my demo). In demo/plugin* I implemented two plugins:
> plugin1, plugin2 (each plugin adds an extension for Section).
>
> Best regards,
> Decebal
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Announce-wicket-plugin-tp4653875.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
>
>


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

Reply via email to