Hi,
Who wrote http://www.wicket-wiki.org.uk/wiki/index.php/Struts ?
I like it!
Eelco
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
It should be fixed in CVS version. though I have no valid test-case to
test it on, maybe you could give me a case to test the serializable?
Anyway, it will be in our next release which we plan on releasing soon
as our next component will be included and some of the major bugs are fixed.
Marco
All,
There is a short introductory article on Wicket published in the JavaPolis newsletter. You can find the article below.
http://wiki.javapolis.com/confluence/download/attachments/16623/page7.gif
There is also a (4MB) PDF version available, somewhere on the wiki.
See all pages:
The easiest way to test whether you wicket application behaves well
when serialized, turn on the debugging logging for WebSession, like:
log4j.logger.wicket.protocol.http.WebSession=DEBUG
Eelco
On 12/2/05, Marco van de Haar [EMAIL PROTECTED] wrote:
It should be fixed in CVS version. though I
Honestly I think the wicket presentation could be better when it comes
about 1.) true OOP, and 2.) when it comes about tools integration support.
1.) Wicket brings back into it's right the true OOP approaches in the
serverside java programming. I think this is almost all the time
overlooked
Is there any concrete (simple) code example for rerendering a part of a
page? I tried myRequestCycle.request(myComponent), but all I got were
huge errors in my console.
Ari Suutari wrote:
Hi,
Project wicket-stuff contains already some AJAX components
(scriptaculous and dojo based ones).
Yes, with the proxy based solution it is not necessary (transient
fields). I was saying that with the AOP implementation it is
necessary, since there is no proxy working. What the AOP and proxy
solutions have in common is the code to inject the beans.
2005/12/2, Igor Vaynberg [EMAIL PROTECTED]:
that should work, what kind of errors do you getsee the unit test: SimplePageTestand then the rerender(component) calls.johanOn 12/2/05,
Marco van de Haar [EMAIL PROTECTED] wrote:
Is there any concrete (simple) code example for rerendering a part of apage? I tried
you should use requestcycle.setResponseTarget with ComponentRequestTarget
Eelco
On 12/2/05, Marco van de Haar [EMAIL PROTECTED] wrote:
Is there any concrete (simple) code example for rerendering a part of a
page? I tried myRequestCycle.request(myComponent), but all I got were
huge errors in
That selectchoice is a thing you have to add to the collection of choices?then that is not that nice. Because choose one should only be there if no one is selected and null is required (or something like that)Because of that you can't add it easily to the collection because you have to know that
that is what RequestCycle.request(component) does (and how the SimplePageTest works)On 12/2/05, Eelco Hillenius
[EMAIL PROTECTED] wrote:you should use requestcycle.setResponseTarget
with ComponentRequestTargetEelcoOn 12/2/05, Marco van de Haar [EMAIL PROTECTED] wrote: Is there any concrete
dood? That means dead in dutch.. so are you saying you want to kill martijn ;)johanOn 12/2/05, Igor Vaynberg
[EMAIL PROTECTED] wrote:nice glasses dood!-Igor
On 12/2/05, Martijn Dashorst
[EMAIL PROTECTED] wrote:
All,
There is a short introductory article on Wicket published in the JavaPolis
Ok, so form components using a root CompoundPropertyModel are never
versioned, because their data is in the root model. That makes sense.
But what does the form itself do? It doesn't seem to serialize its root
model, and without doing that, it can't live up to its versioning
contract.
I'm
no, SelectChoice is a component that represents a single option element. you add that to the Select component. SelectChoices is a convinience component that draws out a bunch of option tags much like our current components.
-IgorOn 12/2/05, Johan Compagner [EMAIL PROTECTED] wrote:
That
yes then it is exactly what i say.for Choose one.. you shouldn't have to need a SelectChoice == option element in youre collectionBecause Choose one should only be there if nothing is selected and null value isn't allowed...
johanOn 12/2/05, Igor Vaynberg [EMAIL PROTECTED] wrote:
no, SelectChoice
but a SelectOption is not in your collection - its a component. The whole point of the Select component is to have full control over the markup. All our core choice elements limit your access to markup by producing the entire select output for you including all the options. The point of
16 matches
Mail list logo
