HI,
on http://wicket.sourceforge.net/source-repository.html it points to:
Web Access
The following is a link to the online source repository.
http://svn.apache.org/viewvc/incubator/wicket/branches/wicket
however, the this is wrong, correct should be:
It is not only the header component, it is any auto component such as
wicket:link, wicket:message etc. If anything is different in the other
markup file ...
Juergen
On 11/3/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
the markup gets loaded. Two possible solutions: a) stay with adding
auto
Please see src/test/java. It contains all the junit tests.
Juergen
On 11/3/06, craigdd [EMAIL PROTECTED] wrote:
I though I remember seeing on the WIKI a section on how to unittest
components and pages in wicket. Since the move to the apache WIKI I don't
see that anymore, unless I am totally
Not sure I understand it. Can a bit more specific. How markups (input
and expected output) look like?
Juergen
On 11/3/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
Sorry to hijack the thread, but I think this might be related:
I have an idea for a component that is added to an event handler
Ok, but those don't look like the examples that I'm thinking about, I'm
looking for documentation on how to unittest your own pages, forms, etc.
Juergen Donnerstag wrote:
Please see src/test/java. It contains all the junit tests.
Juergen
On 11/3/06, craigdd [EMAIL PROTECTED] wrote:
Search for WicketTester and TagTester and WicketTestCase
Juergen
On 11/3/06, craigdd [EMAIL PROTECTED] wrote:
Ok, but those don't look like the examples that I'm thinking about, I'm
looking for documentation on how to unittest your own pages, forms, etc.
Juergen Donnerstag wrote:
Please
Question / Idea:
If I undestand it correctly, currently component hierarchy is build based
on markup. How about to do it other way round ? For component hierarchy
created in your java code lookup the markup ?
saki
that wont work, some components such as wicket:link and wicket:message
only exist in markup
-igor
On 11/3/06, Petr Sakar [EMAIL PROTECTED] wrote:
Question / Idea:
If I undestand it correctly, currently component hierarchy is build based
on markup. How about to do it other way round ? For
Thanks Gwyn, this was the page that I was looking for.
One more question. I have a couple form object in my application that
aren't inner classes to a page object. Is there a good way to test the
separate form object. It looks like the only was to test a form is to get a
FormTester from the
You need to re-create them based on the new markup loaded. In case of
the form example e.g. when you hit the save button (same page), or
when you change the locale (again same page). And for the 2nd render
there is no component constructur called any more. Which means markup
gets loaded during
that wont work, some components such as wicket:link and wicket:message
only exist in markup
Igor,
thank you for your answer.
From api doc:
wicket:message=value=key would replace or add the attribute value with
the message associated with key.
I would expect it is implemented using
11 matches
Mail list logo
