Re: One field enabled in a disabled container

[tho...@jarnot.de]

Before committing to a - as you said wierd requirement - by breaking the form
structure, I'd rather do the setEnabled() - dance but separate it into a
special behavior attached to the form. So you have your requirement
fulfilled while keeping the GUI code clean and readable.


--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/One-field-enabled-in-a-disabled-container-tp4665156p4665158.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: Apache wicket project as osgi compoments

[tho...@jarnot.de]

Although we don't know anything about your application structure, I tend to
answer YES.

Assuming from the subject, that we are talking about OSGi modules (or rather
bundles), making the application capable of that dynamism is surely
possible. It simply depends on your decision of utilizing the OSGi
programming model and execution environment. Do you have your application
modules OSGi ready?

Having a look a the wicket-distribution it seems to be OSGi-ready. You also
may have a look at the Pax Wicket extension.

So you're probably good to go.


--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Apache-wicket-project-as-osgi-compoments-tp4664159p4664164.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