Struts has a mapped property attribute in the nightly build.
This lends it self to the Expresso DBObject way of
reading field by attribute name. If you had a database
object with field called "ProductId" you could retrieve
the column simply with code like:
dvdProduct.getField("ProductId");
More importantly you could retrieve the property from a
struts html tag with this pseudo code.
<html:hidden property="businessobject.field(ProductId)" />
<%-- getBusinessObject().getField( "ProductId" ) --%>
<bean:write name="orderForm" property="businessobject.field(ProductName)" />
<%-- orderForm.getBusinessObject().getField( "ProductId" ) --%>
So I am looking forward to next release, of course!
--
Peter Pilgrim ++44 (0)207-545-9923
............................................ Swamped under electionic mails
---------------------------------------- Message History
----------------------------------------
From: "Stephen Owens" <[EMAIL PROTECTED]> on 09/01/2002 11:11 EST
Please respond to "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
cc:
Subject: RE: Advice needed on Stuts versus Struts/Expresso
Bill,
--<CUT>--
Expresso has an advantage over many other frameworks that it is open
source so if you really get stuck you can modify the framework to fit
you. Of course then you have to worry about stepping off the upgrade
path when the next revision comes out.
My experience with Expresso has been pretty positive so far. It handles
a particular set of problems pretty well. With webAppWriter in front of
it it is VERY fast to get up and running for a new application. The code
doesn't look too bad, the documentation is a bit weak in areas and
missing completely in others, but there is quite a bit of it, which
often isn't true for home grown code. The mailing list is not as
amazingly helpful as the Struts mailing list, but it is pretty good and
will hopefully keep getting better.
Which brings up another point, will Expresso upgrade in step with
Struts? If the next revision to Struts has wonderful workflow management
will your Expresso code be able to take advantage of it? At that point I
think we're probably just trying to read tea leaves, you always have to
plant a stake in the ground and start coding with what exists.
regards,
Stephen Owens
Corner Software
--<CUT>--
--
This e-mail may contain confidential and/or privileged information. If you are not the
intended recipient (or have received this e-mail in error) please notify the sender
immediately and destroy this e-mail. Any unauthorized copying, disclosure or
distribution of the material in this e-mail is strictly forbidden.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
