Just to clarify
Struts can map form to dyanmic object .
It would be cool if it could map to a graph of such objects.
I know the functionality doesn't exist but I think it's a cool idea.
You could have a tag like this on the page.
<html:arbitrary-form class="org.apache.struts.example.House" target="mapper.do">
then an xml file like so
<form type="arbitrary-form" class="org.apache.struts.example.House" >
<attribute name="id" changable="false">
<set name="rooms" class="org.apache.struts.example.Rooms" changeable="true">
<attribute name="id" changable="false"/>
<attribute name="description" changeable="true"/>
</set>
</form>
and then you had a method that you could call
ArbitraryForm arbitraryForm = (ArbitraryForm) form;
House house = arbitraryForm.deserialise(); // or whatever
houseDAO.storeNewHouse(house);
I guess I just am in *love* with hibenate at the moment
--b
On Fri, 6 Aug 2004 21:09:14 +0200, bryan <[EMAIL PROTECTED]> wrote:
> Wouldn't it be so cool if you could take something like a graph of
> hibernate objects and
> have a form dynamically generated for u.
>
> With dhtml or something so that you could populate the whole graph in
> one user form ?
>
> For example a House object that had a set of rooms, each room with
> it's own description.
>
> The dhtm generated by the form could expand out so that the user could add an
> arbitrary number of rooms each with their own description.
>
> The whole thing could get filled out in a single http request.
>
> This would greatly reduce the use case for creating a house.
>
> Has anyone ever developed anything like this ?
>
> --b
>
>
>
>
> On Fri, 06 Aug 2004 11:54:01 -0700, Michael McGrady
> <[EMAIL PROTECTED]> wrote:
> > How do map based forms farm the values from the request?
> >
> > At 09:13 AM 8/6/2004, you wrote:
> > >For me it was very painless and although there aren't lots of big "killer"
> > >features - there are IMO lots of little ones that make this a good upgrade.
> > >
> > >Niall
> > >
> > >----- Original Message -----
> > >From: "Dean A. Hoover" <[EMAIL PROTECTED]>
> > >To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
> > >Sent: Friday, August 06, 2004 4:49 PM
> > >Subject: Re: very dynamic forms
> > >
> > >
> > > > Thanks. I am looking at Niall's Lazy stuff, but I like your idea.
> > > > I will add it to my list o f investigations and experiments. I've
> > > > written quite a bit to struts 1.1. Is there a downside to upgrading?
> > > >
> > > > Thanks.
> > > > Dean
> > > >
> > > > Kevin A. Palfreyman wrote:
> > > >
> > > > >Dean,
> > > > >I do a similar thing with Struts 1.1, and I use an ordinary struts form
> > > > >(a subclass of ValidatorActionForm) that has a DynaBean as one of its
> > > > >fields. To match this, my DTO also has the same field as a DynaBean,
> > > > >and we just have to be a bit more clever when we copy properties between
> > > > >the two. The "schema" of the DynaBeans are configured entirely
> > > > >separately from the rest of the Struts stuff, and should be fairly
> > > > >easily done from a DB. In an upcoming version, the shape of the
> > > > >DynaBeans will be determined from data from a remote corba service.
> > > > >
> > > > >Unfortunately, this is all product specific (closed source), so I can't
> > > > >just pass it on (it wouldn't be useful to you anyway in its current
> > > > >form). But it should encourage you that it can be done.
> > > > >
> > > > >>From a quick read of his web page, Niall's Lazy stuff looks very
> > > > >promising. If I were starting again, I might have a look to see if that
> > > > >would fit.
> > > > >
> > > > >Good luck,
> > > > >
> > > > > Kev
> > > > >
> > > > >
> > > > >
> > > > >>-----Original Message-----
> > > > >>From: Dean A. Hoover [mailto:[EMAIL PROTECTED]
> > > > >>Sent: 06 August 2004 15:47
> > > > >>To: Struts Users Mailing List
> > > > >>Subject: Re: very dynamic forms
> > > > >>
> > > > >>What I need to do is construct a form that has a variety of
> > > > >>text input forms on it that are determined at run-time. I
> > > > >>know how to do this in jsp but I need to provide an
> > > > >>ActionForm that conforms to that form.
> > > > >>I got several useful replies last night and am investigating them.
> > > > >>
> > > > >>Dean
> > > > >>
> > > > >>Michael McGrady wrote:
> > > > >>
> > > > >>
> > > > >>
> > > > >>>That makes sense, but his other comments seem to negate that. He
> > > > >>>says, e.g., that "[w]hat would come out of the query would
> > > > >>>
> > > > >>>
> > > > >>be label,
> > > > >>
> > > > >>
> > > > >>>form position, variable name,etc, etc.". These are things
> > > > >>>
> > > > >>>
> > > > >>that are on
> > > > >>
> > > > >>
> > > > >>>the page form, not on some dynamic class handling the form. He
> > > > >>>specifically rejects dynamic class structures in fact when he says
> > > > >>>that he has worked with DynaActionForm and ActionForm and that they
> > > > >>>don't fit the bill. I think he is focusing on the idea of having
> > > > >>>changing variables on the page form and how to handle this on the
> > > > >>>backend. Is that right, Dean?
> > > > >>>
> > > > >>>Michael
> > > > >>>
> > > > >>>At 01:40 AM 8/6/2004, you wrote:
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>>>I thought that
> > > > >>>>
> > > > >>>>" I want to build one on-the-fly according to
> > > > >>>>
> > > > >>>>
> > > > >>"configuration" stuff
> > > > >>
> > > > >>
> > > > >>>>stored in a database, that can change. "
> > > > >>>>
> > > > >>>>was pretty clear, especially after he pointed out the
> > > > >>>>
> > > > >>>>
> > > > >>DynaActionForms
> > > > >>
> > > > >>
> > > > >>>>weren't what he was looking for because they came from
> > > > >>>>
> > > > >>>>
> > > > >>struts config.
> > > > >>
> > > > >>
> > > > >>>>But maybe it's just me - I'm used to wondering about what (weird
> > > > >>>>stuff) I can do in Struts.
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>>>>>>>At 05:00 PM 8/5/2004, you wrote:
> > > > >>>>>>>>>
> > > > >>>>>>>>>
> > > > >>>>>>>>>
> > > > >>>>>>>>>>Suppose I want to construct a form based on a query to a
> > > > >>>>>>>>>>database. What would come out of the query would
> > > > >>>>>>>>>>
> > > > >>>>>>>>>>
> > > > >>be label,
> > > > >>
> > > > >>
> > > > >>>>>>>>>>form position, variable name, etc, etc. What would be the
> > > > >>>>>>>>>>recommended way of building this under struts/tiles? I've
> > > > >>>>>>>>>>been working with struts/tiles for a while now
> > > > >>>>>>>>>>
> > > > >>>>>>>>>>
> > > > >>and this is
> > > > >>
> > > > >>
> > > > >>>>>>>>>>the first time this sort of requirement has come up. I've
> > > > >>>>>>>>>>used DynaActionForm and ActionForm, but do not
> > > > >>>>>>>>>>
> > > > >>>>>>>>>>
> > > > >>see how this
> > > > >>
> > > > >>
> > > > >>>>>>>>>>sort of thing fits either model.
> > > > >>>>>>>>>>
> > > > >>>>>>>>>>Any ideas?
> > > > >>>>>>>>>>
> > > > >>>>>>>>>>Dean Hoover
> >
> >
> > > > >>>>>>>>>>
> > > > >>>>>>>>>>
> > > > >
> > > > >
> > > > >---------------------------------------------------------------------
> > > > >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]
