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 :)
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
