Hi,
i'm also interested in making a modular, during runtime extensible wicket
appliaction.
Meaning a Wicketapplication which can be extended by plugins during runtime.
Can OSGi accomplish this?
Could you please explain the wstarter a little bit more in detail.
I only developed normal wicket web
Hi Chris,
Comments inlined.
2009/10/31 Giambalvo, Christian christian.giamba...@excelsisnet.com
Hi,
i'm also interested in making a modular, during runtime extensible wicket
appliaction.
Meaning a Wicketapplication which can be extended by plugins during
runtime.
Can OSGi accomplish
it is easy to create a pluggable application in wicket. all you need
is a registry of component providers, whether it be something like
spring [1], a custom registry like brix uses [2] or something more
advanced like osgi. the choice should be based on the featureset you
need. eg, if you need hot
Alex,
My apologies, but I cannot reproduce this issue again. Even if I mount a
page and then land on that page, I now get the correct behaviour with the
default URL encoding strategy. I am wondering if I called the correct
urlFor()? No good speculating on this though
If I see this again, I
takes values for alt attribute . Like the sortable columns , If I
can set
value for alt attribute that would be really nice.
how about:
div.add( new AttributeModifier( alt, true, new ModelString( what
it should say... ))
Hi,
I was trying to figure out how to display wicketmodal once a page is
created-- this has been a popular issue
http://issues.apache.org/jira/browse/WICKET-12
It seems just a week ago it has been marked resolved in wicket 1.4.4,
can someone tell me what the fix is or what I need to do
If you do go with OSGi, you will have problems with classloaders and
deserialization.
To my knowledge, nobody has yet solved this (i.e. implemented a good
solution) in a decent way. The Eclipse buddy system is not proper
OSGi, IMO.
pax-wicket does solve this problem (using proper
I do agree Eclipse buddy system in not proper OSGi, but it makes a lot
easier to develop applications because
1- Your application, components, etc, will be same as in any normal Wicket
application (no changes to are needed)
2- If you find out OSGi is not suitable at the end, you can always build
