Hi Natalie,
I'm finally coming up on upgrading from 1.4.19 to 1.5. To manage my projects
better, could anybody comment on how long it took them to upgrade? I know it
depends on how complicated your application is, but as a general
guideline, does it take minutes, days, months?
It took me
Hi,
There is nothing specific for Wizard components in WicketTester.
WicketTester is in -core, Wizard is in -extensions. -core doesn't know
about -extensions.
Can't you test it like any other Panel ?
On Sat, Mar 10, 2012 at 12:13 AM, Dan Alvizu dalv...@pingidentity.com wrote:
Hi again,
Sorry
On Fri, Mar 9, 2012 at 4:03 PM, grazia grazia.russolass...@gmail.com wrote:
Still not clear what I did wrong.
With wicket 1.4 my code was:
public final class PageHeaderComponent extends WebComponent {
public PageHeaderComponent(final String id, final String
changeDestination) {
Hi,
I'm pretty new to Wicket but I had a similar problem and did the following:
In your Application subclass
@Override
public void init() {
...
getSharedResources().add(cssheader, new
ContextRelativeResource(/css/header.css));
...
}
then in your component // behavior or whatever use
Hi Chris,
GAE initializer is part of WicketStuff which is hosted at github.com:
https://github.com/wicketstuff/core/
See http://help.github.com/send-pull-requests/
On Thu, Mar 8, 2012 at 7:53 PM, Chris Merrill ch...@webperformance.com wrote:
On 3/8/2012 11:55 AM, Martin Grigorov wrote:
I'm
Hi,
Thanks for the reply. When I try to test it like other Panel classes
through WicketTester.startComponentInPage(), I get the NPE in the first
post, as WizardStep.onInitialize() expects the WizardStep to be within a
wizard providing a Form. The lack of a Form in the parent causes the NPE.
Is
