Sorry for this, I did not create our domain classes. However I did not
say that you had to do this, I thought it was a wicket problem. So of
course I got to the wicket list with it, as I've done with other things.
Some times it turnes out to be a wicket bug sometimes not. I am very
aware that this is a opensource community. I try to give back where I
can, by finding bugs and creating components.
Actually I was in the process of cutting out excess code, next I'll do
that before drawing anybody else(external) into potential bugs.
regards Nino
Igor Vaynberg wrote:
nino, you know how to use a debugger dont you? for future reference here is
what i did:
set a breakpoint in formcomponent.updatemodel to see if the object inside
the model is being updated, walk that to component.setmodelobject() call, go
inside and you will see that the model object is not being updated because
your implementation of Phone.equals() returns true for any selected phone -
thus wicket does not push it into the model because it thinks the old value
is the same as the new value. we are not payed to debug your code, so please
next time cut out as much fat out of your example as possible so i do not
have to spend my personal time solving your business bugs.
-igor
On 8/26/07, Nino Saturnino Martinez Vazquez Wael <[EMAIL PROTECTED]>
wrote:
Igor did you ever get the chance to check this out?
regards Nino
Nino Saturnino Martinez Vazquez Wael wrote:
Now available from badongo to avoid cheesy IE problems
http://www.badongo.com/file/4142529
Nino Saturnino Martinez Vazquez Wael wrote:
Argh had made an error in the previous quickstart that made the
dropdown to be broken..
This version however displays the problem as it are.
http://fileho.com/download/ff12cb141317/wicket-quickstart.zip.html
Small guide on howto see the problem:
First select an option from the dropdown, after it have been selected
you cannot change it again. Very strange...
PS I am aware that using hashcode from a string is not a proper or
safe way to generate and id, we will change it later.
Regards Nino
Nino Saturnino Martinez Vazquez Wael wrote:
Hmm, I've now managed to reproduce the problem in a wicket quickstart.
It's great news on one side, this means that it has nothing todo
with wicket-spring thing or hibernate. On the other side im a bit
puzzled by what could be causing the problem.
If someone would take a look, I've uploaded the source to here:
http://fileho.com/download/ff12cb886730/wicket-quickstart.zip.html
I think it may be an odd combination of things, that however does
not bring me closer to a solution:(
regards Nino
Nino Saturnino Martinez Vazquez Wael wrote:
I've now created a quickstart project. This does however not show
this behavior. Im also using spring injection, not doing so in the
quickstart. I'll dig deeper into this.
regards Nino
Nino Saturnino Martinez Vazquez Wael wrote:
Ok, i've removed all other stuff from the page, error are still
there, wierd thing is that the dropdowns are working on the other
pages.
I guess next step are to create a quickstart and see if it works
there..
Should I try with beta 3 or?
regards Nino
Nino Saturnino Martinez Vazquez Wael wrote:
Thats wierd.
I've now changed it to not use ajax and are using
wantonselectionchangednotifications..
This yields the same result, not working. This is really wierd
cant belive that it should not work, some of the processing must
be broken by some of the other components I add, are there any
way to get some more describtive informations from wicket?
http://papernapkin.org/pastebin/view/1389
Nino Saturnino Martinez Vazquez Wael wrote:
Hmm, im not using the dataview or iDataprovider, although I have
a listview in one of the singlephonecomparepanels. However it
seems as theres something about these two issues that match.
But the wierd thing are that it never ever picks up the change
in the dropdownchoice. I'll try going back and doing this
without ajax and see if that works any better.
I've tried your suggestion about declaring phone as a private on
the page it did not fix the problem..
Wierd stuff are that I used the same approach in wicket 1.2.6
and it was working there(although not with the same combination
of models)..
regards Nino
Oleg Taranenko wrote:
Hello Nino,
It seems to be the same issue as i've encountered a week ago.
see thread "Order-Items master detail page" started at 16 august
Possible Solution in you case:
declare anywhere posible in page
private Phone selectedItem;
in function
protected void onUpdate(AjaxRequestTarget target) {
...
selectedItem = (Phone) phoneA.getObject();
...
}
And than everythingService.findAllStandardFeatures() (or other
function) shoud get access to the
field selectedItem.
Possible you need to create your own new IDataProvider.
Cheers,
Oleg.
am 23 August 2007 um 09:08 schrieben Sie:
Hi
I have a page where theres two dropdownchoices and two panels
acordingly. when you click dropdown a and select a new item
panel a should be updated to the new item, I've used
ajaxformComponentupdatingbehavior( have also tried
ajaxformsubmittingbehavior).
However it seems as the model of the dropdown are never
updated, im using compoundpropertymodel (have also tried
reverting and just using a
simple model).
I just cant figure out whats wrong. Please take a look any
hints will be
appreciated
http://papernapkin.org/pastebin/view/1386
Havent had the chance yet to tryout beta 3, not sure if its
gone there.
regards Nino
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
