+1 to report them as warnings. I added some checks before, for example, a
@Reference on a private field or non-setter method. We could add a few
negative itests for these checks.
Thanks,
Raymond
--------------------------------------------------
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
Sent: Thursday, March 27, 2008 10:41 AM
To: <[email protected]>
Subject: Re: Reporting errors for illegal SCA annotations (TUSCANY-2140)
Simon Nash wrote:
TUSCANY-2140 raises a more general question about whether we should
report errors for all SCA annotations that are used in illegal positions.
I suspect it would be impractical to do this in every possible case.
For error cases that we consider "common" or "harmful", adding a
diagnostic is worthwhile. TUSCANY-2140 would fall into this category.
I'd be interested in other views about this.
Simon
+1 to report a misplaced annotation as a warning.
Throwing an exception that'll prevent my application to run just because a
harmless annotation was present (and not considered) somewhere in part of
my code seems too aggressive to me.
--
Jean-Sebastien
---------------------------------------------------------------------
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]
