JSR 124: J2EE Client Provisioning Specification goes Final

Discussions

News: JSR 124: J2EE Client Provisioning Specification goes Final

  1. The Expert Group for JSR-124: J2EE Client Provisioning Specification has published the Final Release of its specification. This JSR defines the Java standard for server applications that provision client applications in such a way that the details of any one client provisioning model are abstracted and standardized.

    This JSR will define deployment conventions and possibly deployment packaging formats for client application code and associated descriptive configuration data to enable storage and management of client applications for provisioning to target client platforms. It will define a Java framework and APIs that can be used to interact? with existing and emerging provisioning protocols and conventions in a standardized way. It will provide a portable way to negotiate a list of suitable client applications available for delivery and monitoring the activity of delivering a client application.

    This JSR will aim for a design of the provisioning framework so that it can be layered on top of existing J2EE APIs in such a way that provisioning adapters may also be written portably on the platform.

    View the JSR 124 Details

    Download the JSR-124 J2EE Client Provisioning Specification (Final Release)

    Threaded Messages (4)

  2. Whoa[ Go to top ]

    Holy marketing-speak batman! Can anyone tell what this means, in english please?
  3. Provisioning[ Go to top ]

    From the spec:

    {{
    For the purposes of this specification, the term provisioning refers to the
    activities of advertising client services to a client device, and to the process of
    delivering the service to the device. The physical form of a client service that is
    delivered to a client device is referred to throughout this document as a client
    bundle, or sometimes just a bundle. A bundle may take the form of an archive file
    containing Java byte code and the resources it uses, a file containing a screen
    saver, other media or other executable.
    }}

    Mobile network operators _provision_ applications and services to mobile devices.

    4thPass (in Seattle) has been doing this for quite a while. 4thPass was acquired by Motorola: http://www.4thpass.com/

    Another company in this space, Pixo ( http://www.pixo.com/ ), was acquired by Sun in July 2003.

    http://www.sun.com/smi/Press/sunflash/2003-07/sunflash.20030717.1.html
  4. Whoa[ Go to top ]

    Holy marketing-speak batman! Can anyone tell what this means, in english please?

    That it's dedicated to "client application code" shines a ray of hope into TheServerSide's jaded audience of HTML spinners. WebStart and Swing kick hiney together! Now even the JCP knows it.
  5. Yet another example of the slowliness of the JCP.
    When this JSR started, there were 15+ provisioning platform vendors. Now this number has been reduced to 4 or 5. Among them maybe 3 main vendors: Mobilitec, 4th Pass and Pixo (now being handled by SUN).
    Do we need a JSR for 3 vendors ?? These vendors, especially Mobilitec have huge contracts with the biggest wireless operators in the world. The decision of using these platforms are not based on the compliancy with this JSR.
    Each wireless operator has different requirements in term of features, this features largely encompass what is defined in this JSR.
    The only used feature from this JSR in all above listed platforms is the provisioning interface (usually web service based). A big issue with the PAR lies in the pricing, drm, ... features which are not defined by the JSR and usually differently described by each implementor.