[jsr361-experts] Re: [jsr361-observers] JIRA Issues
- From: Werner Keil <
- Subject: [jsr361-experts] Re: [jsr361-observers] JIRA Issues
- Date: Tue, 31 Dec 2013 13:58:04 +0100
Thanks for the summary. As I was travelling during the call I appreciate
There is at least one detail I'd like to point out here, before creating a
JIRA ticket. EventManager.getSystemEvents() actually returns a String
array, so something like getSystemEventNames() could be more logical.
The getCurrent() method is a bit short, but for an EventManager it sounds
understandable it'll return events, thus I don't mind the naming here.
Happy New Year,
Am 31.12.2013 10:52 schrieb
> Dear experts,
> as discussed during our last telco, here comes the list of JIRA issues
> that caused changes (or at least consideration of changes, some may
> have fixed with "Won't change", see the respective detailed JIRA
> site)in the spec since beginning of the public review.
> This is for your convenience in able to easier locate chenages that
> have been done.
> Pls. let me know if you face any issues with JIRA access or the content
> of any JIRA issues.
> I will also upload the latest version of the spec to the EG site today.
> I wish you and your families a happy, healthy and successful 2014!
> Best regards -
> MESPEC-2908 Clarification for Suite.setSuiteState method
> MESPEC-2904 It is possible to enable scrolling with
> undefined scrolling interval
> MESPEC-2895 Cellular API: consider getAvailableNetworks
> MESPEC-2871 Clarification required for SWMPermission class
> MESPEC-2852 AccessPoint.getType() and
> CellularNetwork.getNetworkType() are named inconsistently
> MESPEC-2839 CellularNetwork should provide the
> corresponding AccessPoint
> MESPEC-2827 Missing definition of PowerStateEvent event
> MESPEC-2826 Optional event delivery contradicts the purpose
> of power management.
> MESPEC-2825 PowerManager: Behavior missing if
> setPowerState() is invoked with same current state event.
> MESPEC-2824 Unclear how application communicates opposition
> to current state change event.
> MESPEC-2823 POWER_STATE_FULL_POWER description is confusing
> MESPEC-2822 Power Management Sample Code comments need
> MESPEC-2821 Clarify relation between
> PowerManager.getPowerState() and
> MESPEC-2819 PowerManager.getInstance() return value = null
> is unnecessary.
> MESPEC-2817 PowerManager: getBatteryLevel is inconsistent
> with Event.getCurrent(BATTERY_LEVEL).
> MESPEC-2816 PushRegistryPermission: Add
> NullPointerException in the Throws section
> MESPEC-2815 PushRegistryPermission: Clarify if space is
> allowed or not in the list of actions
> MESPEC-2808 PushRegistryPermission constructor: Clarify if
> the input for "actions" param is case sensitive or not.
> MESPEC-2806 Typos in javax.microedition.event.EventManager
> MESPEC-2805 EventPermission: Clarify if space is allowed or
> not in the list of actions
> MESPEC-2803 Root Certificate definition
> MESPEC-2799 EventManager.post(): need to clarify how an
> application registers to be an authorized recipient of an event.
> MESPEC-2791 Event, EventPermission classes: Need to clarify
> the non-acceptable values of "event name".
> MESPEC-2787 media.Controllable.getControls contains invalid
> reference to Player.
> MESPEC-2786 The constructor of class
> javax.microedition.media.Manager must be package visible.
> MESPEC-2785 TimeBase must be interface
> MESPEC-2784 Typos in javax.microedition.event.Event class
> MESPEC-2780 Behavior undefined on opening twice a
> IMCServerConnection using the same uri.
> MESPEC-2772 EventPermission constructor should throw
> IllegalArgumentException for invalid event name
> MESPEC-2771 EventPermission: action = read is also used in
> MESPEC-2770 Subscriber.getBySlotNumber needs clarification