Hi Folks,
+1 for warnings when the application is developed. +1 for Errors when
you put the application into production. The trick is to know the
difference
between deployment for UT vs. deployment for real.
:-)
Dave
----- Original Message -----
From: "Simon Nash" <[EMAIL PROTECTED]>
To: <tuscany-dev@ws.apache.org>
Sent: Monday, March 31, 2008 11:56 AM
Subject: Re: Reporting errors for illegal SCA annotations (TUSCANY-2140)
Jean-Sebastien Delfino wrote:
Mike Edwards wrote:
ant elder wrote:
I agree with that and having recently spent time helping people new to
Tuscany and seen the problems they've had I think it would be much more
helpful to fail. Could we have a "lenient" mode which can be used when
debugging in eclipse? But I think the default should be strict so when
you
deploy a Tuscany webapp it fails if there are issues.
...ant
Wouldn't it be better to output warnings rather than simply stop?
In the cases your talking about, were there any warning messages?
Wouldn't such messages have helped?
Yours, Mike.
+1, it looks like you and I are on the same page but in minority.
Also, annotations are just one way of configuring things. XML is another
one, should we really prevent an application to start if an XML element
is misplaced?
I think that all the people who want to throw an exception and stop when
an annotation is misplaced or misconfigured should be given a little
exercise, just for the fun of it:
Try to develop a real application, go yourself through the steps of
writing it, debugging, fixing, rebuilding, deploying etc. Then come back
and tell everybody again what you'd prefer, warning messages, error
messages, or exceptions that prevent the application to start.
Good luck in advance :)
>
I prefer to be given error diagnostics as early in the development
cycle as possible. IMO, compile-time errors are better than runtime
errors, and deployment-time or configuration-time errors (where
these can be detected) are better than runtime errors.
The above is my view, but it seems from this discussion that this
is one of those "religious" issues where personal preference is a
big factor. Unfortunately, supporting both approaches takes more
work as Tuscany would need to have code to detect errors early for
the "strict" folls as well as code to detect the same errors later
for the "relaxed" folks. And the documentation would need to
explain both approaches with examples of how each error shows up in
both "strict" and "relaxed" modes. This would increase complexity
as well as cost.
So on balance I'd say pick one approach based on the majority view,
and make sure the real users get to vote as well as the Tuscany
developers :-)
Simon
---------------------------------------------------------------------
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]
