Argh really bad example, heres a better one:
tester.getComponent("basepath").getIframe().addvisitor or something?
And then visitor would have to sort out if the component probed were a
form etc?
Nino Saturnino Martinez Vazquez Wael wrote:
So in pseudo code you would:
tester.getForm.add(IVisitorImplementation) ???
Timo Rantalaiho wrote:
On Fri, 31 Oct 2008, Bert van Heukelom wrote:
I want to test an ajax upload component that uses an IFrame. I have
difficulties when trying to access Components via their path that are
contained in the IFrame. I manage to a reference of the Iframe but
can not
find a path-string that accesses a component (namly a form) within the
Iframe.
Try doing wicketTester.debugComponentTrees() (or debugging the exact
hierarchy by yourself).
FormTester f =
wicketTester.newFormTester("path:to:my:iframe:and:to:its:inner:form");
Long component paths like this are a bit problematic anyway.
You could try digging your Form up with a visitor to make it
less dependent on the path.
Best wishes,
Timo
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
