244

General Considerations

JAR file

Client class files

JAR file

Service endpoint interface and dependent classes

Generated classes

JAR file

JAX RPC runtime

Figure 5.10

Packaging a J2SE Client with Web Service Library

Figure 5.10 shows how to package a J2SE client in a modular manner. The

classes specific for Web service access are kept in a separate JAR file referenced

via a class path dependency. Packaged this way, a client can swap out the service

endpoint access without having to change the core client code. The service access

classes may also be shared by different application clients accessing the same ser 

vice. A developer utilizing a prepackaged service interface may also be able to

develop a Web service client with less knowledge of a service.

5.4.4.3

J2ME Clients

Two optional packages, both of which are extensions of the J2ME platform, enable

Web services in the J2ME platform by providing runtime support for XML process 

ing and JAX RPC communication. (Note that although XML processing capabili 

ties are not provided in the J2ME platform, they are required for JAX RPC

communication.)

A J2ME client application developer must package certain resources with a

J2ME application. First, J2ME applications are packaged in a MIDlet format. A

MIDlet is a Java Archive (JAR) file that contains class files, application resources,

and a manifest file (

manifest.mf

), which contains application attributes.