This seems a good clarification to make, the intent is clear, the language isn't.
On 3 Aug 2011, at 02:47, Marina Vatkina wrote:
> Experts,
>
> It seems to me that the spec text uses here and in several other places, 'may be defined' in the content of 'it can be defined on any of the interfaces in the list'... Do we want to change the text everywhere to say 'is/are to be defined on ... either of ...' or should it be left as-is?
>
> thanks,
> -marina
>
> -------- Original Message --------
> Subject: [ejb-spec issues] [JIRA] Updated: (EJB_SPEC-20) Application Exceptions as part of a throws clause
> Date: Fri, 15 Jul 2011 11:22:38 +0000 (GMT+00:00)
> From: Carlo de Wolf (JIRA) <jira-no-reply_at_java.net>
> Reply-To: issues_at_ejb-spec.java.net
> To: issues_at_ejb-spec.java.net
>
>
>
> [ http://java.net/jira/browse/EJB_SPEC-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Carlo de Wolf updated EJB_SPEC-20:
> ----------------------------------
>
> Description: The current definition of a throws clause leaves the actual definition of an application exception optional. This should be made more strict by mandating that a throws clause of a checked exception implies that the exception is an application exception.
>
> EJB 3.1 FR 14.2.1
> {quote}
> The Bean Provider defines application exceptions. Application exceptions that are checked exceptions
> may be defined as such by being listed in the throws clauses of the methods of the bean's business
> interface, no-interface view, home interface, component interface, and web service endpoint.
> {quote}
>
> Should become:
> {quote}
> The Bean Provider defines application exceptions. Application exceptions that are checked exceptions
> *are* defined as such by being listed in the throws clauses of the methods of the bean's business
> interface, no-interface view, home interface, component interface, and web service endpoint.
> {quote}
>
> Note that there are other spots which state the effect of a throws clause.
>
> was:
> The current definition of a throws clause leaves the actual definition of an application exception optional. This should be made more strict by mandating that a throws clause of a checked exception implies that the exception is an application exception.
>
> EJB 3.1 FR 14.2.1
> {quote}
> The Bean Provider defines application exceptions. Application exceptions that are checked exceptions
> may be defined as such by being listed in the throws clauses of the methods of the bean's business
> interface, no-interface view, home interface, component interface, and web service endpoint.
> {quote}
>
> {quote}
> The Bean Provider defines application exceptions. Application exceptions that are checked exceptions
> *are* defined as such by being listed in the throws clauses of the methods of the bean's business
> interface, no-interface view, home interface, component interface, and web service endpoint.
> {quote}
>
> Note that there are other spots which state the effect of a throws clause.
>
>
>> Application Exceptions as part of a throws clause
>> -------------------------------------------------
>>
>> Key: EJB_SPEC-20
>> URL: http://java.net/jira/browse/EJB_SPEC-20
>> Project: ejb-spec
>> Issue Type: Improvement
>> Reporter: Carlo de Wolf
>>
>> The current definition of a throws clause leaves the actual definition of an application exception optional. This should be made more strict by mandating that a throws clause of a checked exception implies that the exception is an application exception.
>> EJB 3.1 FR 14.2.1
>> {quote}
>> The Bean Provider defines application exceptions. Application exceptions that are checked exceptions
>> may be defined as such by being listed in the throws clauses of the methods of the bean's business
>> interface, no-interface view, home interface, component interface, and web service endpoint.
>> {quote}
>> Should become:
>> {quote}
>> The Bean Provider defines application exceptions. Application exceptions that are checked exceptions
>> *are* defined as such by being listed in the throws clauses of the methods of the bean's business
>> interface, no-interface view, home interface, component interface, and web service endpoint.
>> {quote}
>> Note that there are other spots which state the effect of a throws clause.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators: http://java.net/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>