[GLASSFISH-3625] Report non-portable annotation use in code Created: 19/Sep/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: verifier
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Blocker
Reporter: Sanjeeb Sahoo Assignee: Sanjeeb Sahoo
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: All

Attachments: Text File Bug3625.zip     Text File Bug3625.zip    
Issuezilla Id: 3,625


Verifier currently does not report about non-portable annotation usage in the
code. The API scanning facility needs to be improved to scan class data section
that contains annotations. An example of where current verifier does not report
a failure is given below:

public class MyServletEndpoint {
@javax.ejb.TransactionAttribute(REQUIRES_NEW) // incorrect use
public void registerUser(String username, String encodedPW)

{ // ... }


I think, we need to switch to ASM based API scanning implementation to address
this issue.


Comment by Sanjeeb Sahoo [ 26/May/08 ]

Confirming the issue.

Comment by seemarich [ 05/Jun/08 ]

Created an attachment (id=1537)
New files, old files, patch and a readme

Comment by seemarich [ 14/Jun/08 ]

Created an attachment (id=1558)
Updated patch is attached

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Generated at Tue Dec 06 16:49:25 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.