Hi
Has anyone done some? Otherwise i'll look into it once I get time..
Regards Nino
I have finally got a quick start that reproduces the error.
However, I can't seem to test it with a test case.
When I run the quickstart and click the button in the browser, I get the
exception.
Wicket tester generates a different exception.
Is it ok to submit the quick start to jira in this
sure
-igor
On Sat, Dec 12, 2009 at 1:54 AM, Douglas Ferguson
doug...@douglasferguson.us wrote:
I have finally got a quick start that reproduces the error.
However, I can't seem to test it with a test case.
When I run the quickstart and click the button in the browser, I get the
exception.
That would be really cool, Nino!
--
View this message in context:
http://old.nabble.com/JBehave-WicketTester-Steps--tp26756206p26760597.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe,
all,
i just migrated to 1.4.4 from 1.4.3 and looks like enclosure functionality
changed. if enclosure doesn't have child element in it, it throws exception.
for example following code works in 1.4.3
...
wicket:enclosure child=link
div.../div
/wicket:enclosure
a
hrm, already two people stumbled into this. i was of the mind that the
way it works now is the correct behavior, but i am starting to think
maybe i was incorrect...
-igor
On Sat, Dec 12, 2009 at 12:39 PM, Vadim Tesis vad...@hotmail.com wrote:
all,
i just migrated to 1.4.4 from 1.4.3 and
As far as I know, this the way it behaves in 1.4.4 is the correct behavior.
I've used it only when specifying the child of enclosure, not any other
component. Maybe there should be a vote about this.
Alex
igor.vaynberg wrote:
hrm, already two people stumbled into this. i was of the mind
From the description of the tag
http://cwiki.apache.org/WICKET/wickets-xhtml-tags.html I think the 1.4.4
behavior would be correct, and if the example Vadim provided used to
work it would be due to a bug.
The attribute on the tag makes it clear it is a 'child' otherwise it
would have been
Were you able to recreate it?
On Dec 12, 2009, at 12:19 PM, Igor Vaynberg wrote:
sure
-igor
On Sat, Dec 12, 2009 at 1:54 AM, Douglas Ferguson
doug...@douglasferguson.us wrote:
I have finally got a quick start that reproduces the error.
However, I can't seem to test it with a test
I ran into this and now that I know what's happening it doesn't bother me. I
think if anything the messaging is not as helpful as it could be.
1) It was identifying the wrong missing field, which I think is fixed but won't
come until 1.4.5
2) Perhaps the message should indicate that the
i think you guys misunderstand.
i believe what we are talking about here is the requirement for
presence of components *other* then the component specified by
enclosure's child attribute.
essentially if i do this:
add(new webmarkupcontainer(container).setvisible(false));
and have this in my
I did find the behavior handy, but it is easy to work around.
D/
On Dec 12, 2009, at 11:12 PM, Igor Vaynberg wrote:
i think you guys misunderstand.
i believe what we are talking about here is the requirement for
presence of components *other* then the component specified by
enclosure's
12 matches
Mail list logo
