I think I'm just going to save the values to the db, however for future
knowledge how do i use a value encoder with a form?
On Oct 24, 2014 3:15 PM, "Thiago H de Paula Figueiredo"
wrote:
> Implementing your own ValueEncoder and contribute it to ValueEncoderSource
> should be enough to get this wo
Implementing your own ValueEncoder and contribute it to ValueEncoderSource
should be enough to get this working.
On Fri, 24 Oct 2014 16:33:52 -0200, Lance Java
wrote:
I'm not sure I fully understand the problem. I thought the form contained
all the data so all you needed was a new object
I'm not sure I fully understand the problem. I thought the form contained
all the data so all you needed was a new object to populate.
If not, Kalle's suggestion of saving temp state to the db sounds OK to me.
Perhaps with a scheduled task to clear out incomplete wizards after some
period of inact
I agree with Lance, but I just want to comment on the overall problem.
Unless the per-step lifetime in your wizard is in the order of a few
seconds, you are, in my opinion, unnecessarily optimizing to reduce
database operations (and if it was in the order a few seconds, a wizard
might not be the ri
Lance, even if I were to give the object a temp id or put it in a wrapper
object, wouldn't that value be lost as soon as the zone finishes rendering?
It seems to me as if I have three choices, session, commit, or copy form
data from form a to b. Your thoughts?
On Fri, Oct 24, 2014 at 12:02 PM, Lan
urces than @SessionState.
> Date: Fri, 24 Oct 2014 11:50:04 -0400
> Subject: Re: Could not find a coercion from type java.lang.String to type
> org.tapdemo.demo.entity.TimeSheet
> From: gchrist...@cardaddy.com
> To: users@tapestry.apache.org
>
> I'm facing a problem w
Instead of null ids, you could give your unsaved entities unique ids that
are negative. This would require a smart enough ValueEncoder that would NOT
attempt to lookup negative ids from the database.
It's all sounding a bit hack so you might prefer to pass around a wrapper
object which knows if th
I'm facing a problem where the object hasn't yet been committed to the db
and there for the object has no id. This is probably the root of this
exception.
I'm trying to build an ajax wizard where each step has it's own ajax form
and the db commit will be handled at the end. I was hoping to just p
Pass the object key as a simple type (string/long) and setup the object in
the PREPARE_FOR_SUBMIT handler.
On Fri, Oct 24, 2014 at 5:22 PM, George Christman
wrote:
> Unfortunately the valueencoder is not an option for the form component.
>
> On Fri, Oct 24, 2014 at 11:09 AM, Name Surname >
>
Unfortunately the valueencoder is not an option for the form component.
On Fri, Oct 24, 2014 at 11:09 AM, Name Surname
wrote:
> Hey George. I had a very similar situation. What you can do here is to
> make a new Encoder and put it into appropriate field. Take a look at my
> example.
>
>priva
Hey George. I had a very similar situation. What you can do here is to make a
new Encoder and put it into appropriate field. Take a look at my example.
private class DateEncoder implements ValueEncoder {
@Override
public String toClient(Date date) {
long timeMillis
11 matches
Mail list logo
