|<< Back to previous view|
[GLASSFISH-19104] NullPointerException was thrown out when delete a nonexistent lifecycle module Created: 25/Sep/12 Updated: 25/Sep/12 Resolved: 25/Sep/12
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
Windows XP, Windows 7
|Participants:||Hong Zhang, Tim Quinn and zhouronghui|
STEP2. Execute the delete-lifecycle-module to delete a lifecycle-module that does not exist.
asadmin> delete-lifecycle-module not_exist
|Comment by zhouronghui [ 25/Sep/12 10:59 AM ]|
The patch of
|Comment by zhouronghui [ 25/Sep/12 11:07 AM ]|
I think it's caused by the NULL check was omitted
|Comment by Hong Zhang [ 25/Sep/12 03:01 PM ]|
As Tim helped make this part of the security changes, I will let Tim take a look to see if the attached patch is the best place to fix (or should the NPE check made in CommandSecurityChecker.resourceURIFromAccessCheck so other similar code paths are covered as well).
|Comment by Tim Quinn [ 25/Sep/12 03:56 PM ]|
Fix checked in.
The code which prepares the access check did not adequately protect against a null resource name being used (which happens if the specified life cycle module does not exist).