On 11/12/05, Ted Husted <[EMAIL PROTECTED]> wrote:
>
> The website seems to be in pretty good shape now. I just ran build-all
> on the applications subproject, and that's looking pretty good too. I
> think that just leaves
>
> * Reviewing the applications
> * Adding the Actions package to PlugIns and renaming it Extra
>
> If this all goes well, then I'm thinking we can roll 1.3.0 sometime next
> week.
>
> Now about the whole "what to call it" thing :)
>
> I was about to suggest "Struts Smurf", but, hey, why not go for the
> next best thing?


Nah, I like Struts Gromit much better. ;-) Shale could then be renamed to
Struts Wallace.

We've called everything else "Action", why not call the framework that too?
> :)
>
> OK, let's try it on for size:
>
> Today, the Apache Struts project is comprised of two distinct
> frameworks and several subprojects. The two frameworks are *Struts
> Action* and *Struts Shale*. Struts Action is the original action/page
> framework. Struts Shale is an event/component framework based on
> JavaServer Faces.


I like the term "Struts Action Framework", but just "Struts Action" feels a
little stilted. Not that I have any better ideas.

Also, I prefer "action-oriented" and "component-oriented" over "action/page"
and "event/component".

--
Martin Cooper


...
>
> Struts Action is a flexible control layer based on standard
> technologies like Java Servlets, JavaBeans, ResourceBundles, and XML,
> as well as various Jakarta Commons packages, like BeanUtils and Chain
> of Responsibility. Action helps you create an extensible development
> environment for your application, based on published standards and
> proven design patterns.
> ....
>
> Struts Action in a Nutshell
>
> The framework's controller class, also called "Action", acts as a
> bridge between the application's Model and the web View. When a
> request is received, the Request Processor invokes an Action class.
> The Action class consults with the Model (or, preferably, a Facade
> representing your Model) to examine or update the application's state.
> The framework provides an ActionForm class to help transfer data
> between Model and View.
> ....
>
> We could then call the bundle the "Struts Action Library".
>
> Thoughts on calling the core of the original framework "Action"? Last
> call!
>
> -Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to