Eeek, that's a bug in the spec. Thanks!
It should read:
"If an enterprise Web Bean defined using annotations does not
explicitly declare a Web Bean remove method using @Destructor, and
exactly one remove method that accepts no parameters exists, then that remove
method is the Web Bean remove method. Otherwise, if no remove method
that accepts no parameters exists, or more than one remove method
that accepts no parameters exists, the enterprise Web Bean has no Web
Bean remove method."
Damn copy/paste!
On Wed, Nov 12, 2008 at 1:56 AM, Nicklas Karlsson <nickarls(a)gmail.com> wrote:
Hi
Section "3.3.5.1. Declaring a Web Bean remove method using annotations." says
"If an enterprise Web Bean defined using annotations does not
explicitly declare a Web Bean remove method using @Destructor, and a
remove method that accepts no parameters exists, then that remove
method is the Web Bean remove method. Otherwise, if no remove method
that accepts no parameters exists, the enterprise Web Bean has no Web
Bean remove method."
What should be done if there are multiple remove methods that accept
no parameters? Throw a DefinitionException?
---
Nik
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org