That was my point exactly. :) Especially when you already have the application implemented in Struts, something like my project makes some sense. If you were writing something new, you might want to do things differently.

--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com

[EMAIL PROTECTED] wrote:
Most importantly though is that you can still use what Struts gives you,
things like form validation and internationalization, plus some degree of
the control layer, depending on how your app is designed. I think with

Axis,

you would have to either write some code to duplicate these things, or have
duplicate code in two apps.


Validation is a key point to consider.  Struts gives you a nice
declarative validation system for checking required fields, min/max length
and value, etc.  Many of these common field checks can also be expressed
as part of an XML schema, and therefore by definition could be part of a
WSDL document.  But if you do things the "right" way (Struts actions and
SOAP services both call a common business layer) you don't get a single
point of argument validation easily.

Ideally, between the new versions of JAXB and JAX-RPC, there will be some
way to have metadata for validation constraints attached to individual
bean properties (for example @argument.notNull, @argument.string
maxLength="40") which can be used for both WSDL generation *and* for
Struts form validation--and even Javadocs, potentially.

-- Bill

---------------------------------------------------------------------
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]



Reply via email to