from an outsiders point of view.. i think i'd have to admit
that requiring a proper classname everywhere would actually
increase complexity.
but it is nice to be able to think of actions by their name,
it seems a but superfluous when you're constantly changing their
names.. i like thinking of them as entities, jsut like i like to
do in plain java code... an import sets the namespace or whatever.
maybe the examples could use fully blown classnames to help
the newbie. but why couldnt we have something like the prefix action
proxy in ww1 as well?
i like not having to depend on any tools
to help me get the work done, and being to type it all out in plain
text.. and i guess even copy-paste is a tool...
those are my 2 cents..
Ian Pojman
On Mon, Aug 18, 2003 at 08:24:18AM +1000, Mike Cannon-Brookes wrote:
> Anders,
>
> I have to say that this is a _bad_ idea.
>
> You can already test actions to setup xwork.xml - just instantiate the
> object, call your setter methods and run!
>
> People doing J2EE understand XML, they have to. All descriptors are XML.
> Xwork.xml is not _that_ complex for a hello world example, most of the
> elements are optional.
>
> However, there _is_ a problem with WW2 at the moment that if a view is not
> found, no debug page is shown. I think it should be ("action returned
> "input" but not "input" view found).
>
> M
>
>
> On 18/8/03 8:03 AM, "boxed" ([EMAIL PROTECTED]) penned the words:
>
> > I had a discussion on #java with Epesh, and he expressed the sentiment
> > that WW2 might be turning into a too complex system which will alienate
> > new users and be "popular with the gearheads and such when it leaves
> > nerd-domain". After reading the responses to the "Simplicity in WW2"
> > email I must agree that it looks like this.
> >
> > Now, to make me sound less like a whiner and more like someone with good
> > ideas, here is a practical proposal:
> >
> > The way you have to declare each action in a rather complex XML config
> > file before even rudimentary testing increases the learning-curve
> > needlessly. I propose a few simple features that will help the average
> > users:
> >
> > Actions can be run with the fully qualified class name.
> > Actions map by default to
> > 1. a view document with the name of the action.
> > 2. if 1 fails, a debug document that displays a list of the exposed
> > properties and their current value.
> >
> > This will cut the amount of explaining needed for a hello world type app
> > down by an entire step. Anyone else got ideas like this that will cut
> > down on the learning curve for newbies?
> >
> > Anders Hovmöller
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> > Data Reports, E-commerce, Portals, and Forums are available now.
> > Download today and enter to win an XBOX or Visual Studio .NET.
> > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> > _______________________________________________
> > Opensymphony-webwork mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Opensymphony-webwork mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
