I have solved the persistence problem.
Change EntityManager.persist(event) to
EntityManager.merge(event)
raxden2 wrote:
HI! i had the same problem, but I have another problem:
When i push the button for save Event... throws this exception:
excepción
How about something like this?
s:form namespace=/customer
s:hidden key=domain.id /
s:textfield key=domain.firstName /
s:textfield key=domain.lastName /
s:textfield key=domain.address1 /
s:textfield key=domain.address2 /
s:textfield key=domain.city /
s:textfield key=domain.state /
s:textfield
Do you need to write the method called super()? I Couldn't resist
S
On Thu, Dec 30, 2010 at 4:29 PM, Dave Newton davelnew...@gmail.com wrote:
So, what might happen if you called it (super()) in validate()?
I mean, I apologize for not just outright telling you, but I really like it
when
Hmm, that looks like it might work ;)
Your technique also avoids having to code the behavior into the action
itself, decoupling things even more cleanly.
(Another foot down the rabbit hole: customer namespace, so bits of CRUD
can be reused across underlying models. I do both, and honestly, I'm
4 matches
Mail list logo