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 output for you including all the options. The point of Select/SelectOpti
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, SelectC
no, SelectChoice is a component that represents a single element. you add that to the Select component. SelectChoices is a convinience component that draws out a bunch of tags much like our current components.
-IgorOn 12/2/05, Johan Compagner <[EMAIL PROTECTED]> wrote:
That selectchoice is a thin
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 n
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 n
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 (
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 yo
because of this i like to have a some kind of preference.I do want versioning of all my state changes of component (remove/add or visiblitiy that kind of stuff)But i am mostly not interested in versioning model data. Because that is mostly database data anyway (So it is "versionend" in the database
Yeah. I'm just saying that you /should/ work with request targets
instead of trying to render the component directly.
Eelco
On 12/2/05, Johan Compagner <[EMAIL PROTECTED]> wrote:
> that is what RequestCycle.request(component) does (and how the
> SimplePageTest works)
>
>
> On 12/2/05, Eelco Hille
that depends on the component and what it does. if you are using a pull model then there is no point of versioning it because the model is always recalculated even if the user presses the back button. this is also the case with some formcomponents, since their model is always current after request.
Yeah but most models do change, right? The thing is, nothing is calling
modelChanging(), neither the Form process() nor the form component's
updateModel().
So versioning, even if it's on, is not activated. Why is this?
Nathan
Igor Vaynberg wrote:
when a component is versioned and its model is
If you want to see the impact of serialization, turn on some debugging info:
log4j.logger.wicket.protocol.http.WebSession=DEBUG
serializes state and dumps results of that just like it would do in a
clustered (with the heaviest variant, HTTP session replication)
environment.
log4j.logger.wicket.v
Sounds like a bug to me. Could you please file one?
Thanks,
Eelco
On 12/2/05, Dipu <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> When we add ajax handler to a component with open and close tag , for
> example a drop down choice id="parentAgent">
> wicket will try to add the hanfder twice, first duri
nice glasses dood!-IgorOn 12/2/05, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
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 (4
when a component is versioned and its model is changed it makes a backup of the previous model value by serializing it.in case of the dataview when you change the sort that change is recorded inside the SortableDataProvider which is the model of the dataview. this causes the dataview to make a clon
just checked in a fix. also the Select element does not add a "choose one" choice for you, you have to do it yourself by adding a SelectChoice that represents that element.-Igor
On 12/2/05, Davide Savazzi <[EMAIL PROTECTED]> wrote:
On 11/30/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote:> any feedback
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
This came up before when I was trying to track down why reversing the
sort order of a DataView was bringing down my test application.
(http://thread.gmane.org/gmane.comp.java.wicket.user/4309) It turned out
that the page versioning code was serializing the entire view hierarchy,
recursively, be
Or use the tomcat plugin and close tomcat the NICE way.. (so use the icons)I always do that and because of that i already fixed a lot of serializeable problems.When you do that then on shutdown you see exceptions in the log.
johanOn 12/2/05, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
and watch your
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 myRequestCycle.request(myCompon
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]>:
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). Wi
and watch your log of course.
On 12/2/05, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> 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
>
>
> O
On 11/30/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> any feedback on this yet? if not, i guess i will polish it with its current
> feature set and that will be that.
I have a Map that contains List of choices, my code is:
Map choicesMap = getChoicesMap();
Select select = new Select("mySelect",
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 ev
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
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:
http://wiki.ja
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
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
searchi
