Hi,
your thoughts are quite interesting, but unfortunately I don't know
about an official MOF and kind of doubt from my own experiences Struts
development can succesfully be formalized that way. For instance, many
people still think quite differently about the 'M' part; there is no
'official' rule what 'Model' actually means; if Actions (or even Forms!)
may be considered part of the Model an so on; I've seen quite a lot
in this direction. Struts is largely open to architectural decisions
of this kind. Struts provides a standard way for handling web input,
based on the existence of a central 'request processor' servlet that
delegates the information flow to Action implementations that do the
actual work, determine the outcome and return it to the client somehow,
plus the ability to manage the exact details declaratively via
struts-config.xml and web.xml. But it does not enforce a formal coding
or application design paradigm, and that's probably very wise, as Struts
is a protocol-near, 'down-to-earth' framework by nature, originally
aimed at providing a best-practice solution in a spot that had been
left dark by the J2EE specs. In effect, Struts is a different kind
of animal when compared to things like WebObjects, Tapestry or JSF
which were driven by different design goals. Perhaps Craig can shed
some more light on this.
-- Chris.
NB. Still wonder why Compuware uses AndroMDA...glad to be not
having thrown in ArcStyler :-)
Begur, Praveen schrieb:
Thanks to Vance, Christian, Laurie and others who responded to my query.
I understand the Struts cartridge and have limited exposure to it in
AndroMDA. I have seen a few apps developed and I always wonder if they are
100 % Struts compliant.
Thought 1 - It would be nice to have a Struts compatibility verification
Tool Kit which can certify if a particular Web Application is compliant with
Struts and also grade it on some numerical basis.
Thought 2 - I would like to see Enterprise Software mature itself on the
Technology front so that it becomes measurable.
The whole point of the previous two thoughts is
Goal 1: Reduce learning curve, re-learning
Goal 2: Ensure compliance with standards ( in this case it is with Struts
and related specs )
Goal 3: Make Enterprise Software development more easier/faster/better.
I feel the above goal(s) can be met when the meta-model / meta-definition of
the various technical parts / aspects of Struts like the specific mechanisms
for 'M','V' and 'C' are published by the Struts body / community. Once we
have a formal definition ( structured syntax and semantics ) of Struts ( in
addition to the description of the API's, JavaDocs etc ) we can feed that
formal meta-model into any tool and generate real world applications that
are 100% compliant with Struts.
Does anyone know of a MOF Model of Struts anywhere ? I am curious to know if
the Struts body has published it somewhere.
In the case of the present day AndroMDA templates for Struts, how can one be
sure that code generated is 100 % compliant with Struts ? An apache supplied
meta-model would help ensure and check for Struts'ness' of Applications !!
What do you all feel about this ? Your valuable inputs are most welcome.
regards,
Praveen
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
