I've been beating my head on this for a day now and searched through many
of the docs for the most elegant way to solve a problem I'm having.
I have a Customer object, which has many other objects tied to it. I want
to allow the screen to capture as much of the data as possible on the
initial insert screen before pushing the user to "Next screen"...
I was successful in doing New Customer, add customer object to the
context, return step 2 of adding new customer etc, but I would rather get
the bare necessities all on the first screen, allow the user to come back
and update the object as needed later on.
I read on one thread a suggestion to use castor to create a map but this
seems like double work.. I could just as easily extract each and every
form element from the RunData parameters and create the objects manually
myself, but this seems like a lot of redundant coding.
I love the simplicity of the action call
public void doInsert(RunData data, Context context)
throws Exception
{
Product entry = new Product();
data.getParameters().setProperties(entry);
entry.setNew(true);
entry.save();
}
but when Product needs to map additional data, like a color and size
matrix that I'm trying to do, this simple method doesn't seem possible to
gather on one screen.
I've been using turbine for several months now and love it but would like
any help in pointing me in the right direction to do this.
I have not tried using Intake for form validation at this point.. the app
is still in development and fields are still volital.. I don't think it
would help in this case anyway.
Kind regards,
Jeff Painter
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
