[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2475) @Remove method called instead of @Destroy.
[
https://jira.jboss.org/jira/browse/JBSEAM-2475?page=com.atlassian.jira.pl...
]
Pete Muir closed JBSEAM-2475.
-----------------------------
Resolution: Rejected
I never said anything of the kind.
The logic is correct, and I made a mistake in the forum post, we don't assign the last
parameterless @Remove method to be the default, we throw an exception if there are more
than 1
@Remove method called instead of @Destroy.
------------------------------------------
Key: JBSEAM-2475
URL: https://jira.jboss.org/jira/browse/JBSEAM-2475
Project: Seam
Issue Type: Bug
Components: Core
Environment: N/A
Reporter: Sanne Grinovero
Assignee: Pete Muir
Priority: Critical
Fix For: 2.1.0.BETA1
After some discussions at
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=127257
Pete Muir gets interested and discovers that, in lack of a @Destroy method, a @Remove
could be called.
That looks terribly wrong.
Also, the JBoss Tools shows an error at the presence of multiple methods annotated as
@Remove; that's another problem but it could depend on this one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira