Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: EE 3.0.0
-
Fix Version/s: EE-3.0.0.GA_P01, EE-3.2.0.BETA, EE-3.2.0.GA
-
Component/s: None
-
Labels:None
-
Environment:EE
Description
On Servlet context startup, the BPNSNotificationProvider checks for BPNS configuration. If the RIM pusksdk classes are not available, this results in the following message being logged:
INFO: BPNS notification disabled: Could not read BPNS configuration during Registration java.lang.NoClassDefFoundError: net/rim/pushsdk/commons/PushSDKException
Some of our clients have been concerned about logging the NoClassDefFoundError which can trigger extra alerts in their logging audits, so we should avoid this and just print out a "BPNS notification disabled: RIM pushsdk classes not available" message instead.
INFO: BPNS notification disabled: Could not read BPNS configuration during Registration java.lang.NoClassDefFoundError: net/rim/pushsdk/commons/PushSDKException
Some of our clients have been concerned about logging the NoClassDefFoundError which can trigger extra alerts in their logging audits, so we should avoid this and just print out a "BPNS notification disabled: RIM pushsdk classes not available" message instead.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Revision: 31573
Author: philip.breau
Date: June-15-12 10:31:11 AM
Message:
PUSH-175don't print out scary NoClassDefFoundError when checking for RIM pushsdk configModified : /icepush-ee/branches/icepush-ee-3.0.x-maintenance/icepush-ee/core-ee/src/main/java/com/icesoft/icepush/BPNSNotificationProvider.java
Revision: 31572
Author: philip.breau
Date: June-15-12 10:30:56 AM
Message:
PUSH-175don't print out scary NoClassDefFoundError when checking for RIM pushsdk configModified : /icepush-ee/trunk/icepush-ee/core-ee/src/main/java/com/icesoft/icepush/BPNSNotificationProvider.java