Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

DSDP/MTJ/Discussion/Refactoring/EP

< DSDP‎ | MTJ‎ | Discussion‎ | Refactoring
Revision as of 09:56, 29 January 2009 by Wds057.motorola.com (Talk | contribs) (Current Extension Point List)

Current Extension Point List

We currently have the following list of Extension points:

  • org.eclipse.mtj.core.api
    • Representation of an Java ME application programming interface (API).
  • org.eclipse.mtj.core.configurations
    • Provides a listing of supported Java ME Configurations.
  • org.eclipse.mtj.core.deviceImporter
    • Provides a means for registering new types of device importers
  • org.eclipse.mtj.core.profiles
    • Provides a listof supported Java ME Profiles.
  • org.eclipse.mtj.core.library.MIDletLibrary
    • Define the concept of MIDlet suite library. An external library (not JSR from SDK) that may be used in a midlet. For example a Database Access support library.
  • org.eclipse.me.ui.deviceEditor
    • Registering an editor for use in editing a device from the device management user interface.
  • org.eclipse.mtj.ui.venderSpecJADAttributes
    • Add the some JAD attributes to a specific JAD editor page
  • org.eclipse.mtj.ui.jadEditorPages
    • Add the some JAD editor pages to the JAD editor.

Refactory Suggestions

   org.eclipse.mtj.core.api 
    * Are we the only ones that implements this E.P?
    * Is it really necessary? since the UEI standard provides a way to gather the APIs from a SDK's device
    * The skeletonFile element is not used anymore

Back to the top