I would love to take a look at that. thanks robert.

yan

Robert wrote:

> I do know that Hallmark Stories uses Struts (www.hallmarkstories.com you
> will notice the *.do URLs). Sprint happens to be evaluating it for
> internal use as well. The biggest problem is as you mention, in a large
> app having lots of coding to do, i.e. the FormBeans and Action classes.
> We (Browsersoft) have written some adapters for our eQ! components that
> eliminates the need to have one FormBean per HTML form and same with
> Actions (we are developing a script engine using XML). While not _quite_
> ready for prime time, it does work, and we have demoed the script engine
> and eQ! stuff to Sprint. They have more web developers than Java
> developers, and using our stuff they don't have to write Action classes
> and FormBeans for most of their apps; i.e. the non Java programmers can
> build the app without having a Java programmer on call all the time.
>
> If you (or anyone else) are interested, let me know. We hope to be
> providing a sample download soon, but I do have a demo that I can show.
>
> Robert McIntosh
> [EMAIL PROTECTED]
> Browsersoft
>
> -----Original Message-----
> From: Yan Zhu [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 14, 2002 4:10 PM
> To: Struts Users Mailing List
> Subject: struts' approaches
>
>     I been looking at the struts' stuff for two days now, and
> been a newbie don't really have any real experiences with it.
> However, I do have some experiences with developing j2ee
> applications with jsp, ejbs etc. I feel that there are a lot of good
> things in struts, such as implementation of the MVC and some
> of the tags, but I feel in certain situations what struts provide will
> not be good enough for large, complex, dynamic applications. For
> example, mapping form fields to form beans will be a pain in
> the butt in certain situations. Has anyone used Struts for anything
> of a medium to large size projects with considerable complexity?
>
>     thanks
>
> yan
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to