Lance just incase your email client is stripping out the html.
On Mon, Nov 25, 2013 at 9:24 AM, George Christman
wrote:
>
>
>
> On Sun, Nov 24, 2013 at 7:37 AM, Lance Java wrote:
>
>> > I used very similar code in 5.3.7 without issue which is why I believe
>> this
>> is a bug.
>>
>> Ah, ok... I
On Sun, Nov 24, 2013 at 7:37 AM, Lance Java wrote:
> > I used very similar code in 5.3.7 without issue which is why I believe
> this
> is a bug.
>
> Ah, ok... I agree that this does point in the direction of a 5.4 bug.
>
>
> > I was hoping to manage the formloop through the use of my person
> obje
> I used very similar code in 5.3.7 without issue which is why I believe
this
is a bug.
Ah, ok... I agree that this does point in the direction of a 5.4 bug.
> I was hoping to manage the formloop through the use of my person
object rather than having to manage the form loop through the phone obj
On Sat, Nov 23, 2013 at 4:48 AM, Lance Java wrote:
> I'm still not convinced this is a bug in tapestry... it might be but
> there's still some suspect areas in your code.
>
I used very similar code in 5.3.7 without issue which is why I believe this
is a bug. I was hoping to manage the formloop th
I'm still not convinced this is a bug in tapestry... it might be but
there's still some suspect areas in your code.
1. In hibernate, Phone has-a Person (@ManyToOne) and Person has Phones(s)
(@OneToMany) but you seem to be manipulating both:
@CommitAfter
void onRemoveRow(Phone phone) {
Your on :) you can just paypal me haha.
Well the value encoder doesn't appear to be the issue. :( I can completely
remove the encoder parameter from the component and refresh the page and it
will still hold on to the wrong result despite the correct select option
being selected in the select menu.
As I said... I haven't taken the time to fully understand the code.
That being said, I'd be willing to bet you a fiver that it's causing the
issue
:)
Yes I'm aware and I'm also aware the encoder is fired twice while adding a
row, once for the row and a second time for the remove action. The
ajaxformloop has never seemed to be straight forward, I'm always interested
in a simpler approach. Do you believe this may be the cause of the issue?
On Fr
I'm assuming you know that the encoder is fired every time a conversion
between clientside id and serverside object is done. This includes your
delete action etc.
I didn't take the time to fully understand your code but a ValueEncoder's
role is solely to serialize between clientside string and serverside
object. Nothing more.
Without that line the phone object never gets added to the person object
prior to commit. Do you know of a better approach?
On Fri, Nov 22, 2013 at 2:20 PM, Lance Java wrote:
> Why is your encoder calling
> person.getPhones().add(phone)???
>
> That looks totally dodgy!
>
--
George Christman
Why is your encoder calling
person.getPhones().add(phone)???
That looks totally dodgy!
I would like to share some additional details related to this issue. I'm
finding after removing a row and refreshing the page the selected option is
marked selected in the html correctly, however the option displayed in the
select menu is the former select option from the previously deleted row.
I'
Probably best to see some code before calling it a bug. Perhaps you are
initializing a variable in its declaration (instead of @SetupRender) or
possibly a @Persist issue?
Hello, I have an ajaxformloop with a nested select menu loaded from the
database.
Lets say we have two rows in the list and both select menus have selected
values. When I remove the first row everything works as desired. If I
refresh the page I'm finding my now single row ajaxformloop select menu
15 matches
Mail list logo
