When searching for a good web framework I looked
for simplicity first and power second. The thing which stood out about WW1
was that it seemed easier to get new actions up and running quickly. Being
able to define a default package made the config very simple. I think that
some of this has been lost in WW2.
I would like to suggest the ability to have
"default" mappings between action aliases, action classes and views so that if
I enter the URL "/action/search" or "search.action" the framework will look
for a class named SearchAction and a view of "/search.jsp" (success
result).
This must be able to be configured so that instead
of jsp some other view technology could be used as the default. The
directory in which the default jsp view should be searched for should also be able to be specified ("/" as
default)
The action search path should be able to be
specified. If an action with a namespace is used ("/products/search") then
the action class should be searched for in the sub package "products"
of every package in the search path.
Of course this would only work for actions that
only need one specific result (may use global results)
To my mind, this kind of shortcut makes a framework
appear easy to use. In reality it is easy to configure every action in
your xml file but it is an obvious way to show "look how easy it is to use
Webwork". The fine grained control would remain for more complicated
actions.
John.
|
- RE: [OS-webwork] Simplicity of WW2 John Patterson
- RE: [OS-webwork] Simplicity of WW2 Jason Carreira
- Re: [OS-webwork] Simplicity of WW2 John Patterson
- RE: [OS-webwork] Simplicity of WW2 Jason Carreira
- RE: [OS-webwork] Simplicity of WW2 Cameron Braid
- RE: [OS-webwork] Simplicity of WW2 Lars Fischer
- RE: [OS-webwork] Simplicity of WW2 Jason Carreira
- Re: [OS-webwork] Simplicity of WW2 John Patterson
- RE: [OS-webwork] Simplicity of WW2 Jason Carreira
- Re: [OS-webwork] Simplicity of WW2 boxed
- Re: [OS-webwork] Simplicity of WW2 Rene Gielen