JP5020046B2 - Information processing apparatus, information processing method, and information processing program - Google Patents

Description

  The present invention relates to an information processing device, an information processing method, and an information processing program, and more particularly to an information processing device, an information processing method, and an information processing program that execute communication according to a predetermined communication protocol.

  Conventionally, service is exchanged via a network by SOAP (Simple Object Access Protocol) communication (for example, Patent Document 1). Since SOAP can use HTTP (HyperText Transfer Protocol) in the transport layer, it is possible to implement RPC (Remote Procedure Call) via the Internet.

  In order to realize such RPC by SOAP, a module called a SOAP engine is required on each of the client side and the server side. The SOAP engine performs serialization and deserialization of the SOAP message, and provides a method call method that is transparent to an upper software module using the SOAP communication.

At present, there are various implementations of SOAP engines. Specifically, the specifications of SOAP engines provided by each vendor are not necessarily the same.
JP 2006-330877 A

  However, which implementation to use can be selected according to the user's preference, compatibility with the system execution environment, etc. Switching the SOAP engine also affects software programs that use the SOAP engine. Code modifications and relinks are required.

  Therefore, in a device or information processing apparatus in which an application using SOAP communication or the like is incorporated, there is a problem that a very complicated operation is required when the user requests switching of the SOAP engine.

  The present invention has been made in view of the above points, and is information that can reduce the influence on the upper-level program due to the specification of the lower-level program module used for executing communication by a predetermined communication protocol. An object is to provide a processing device, an information processing method, and an information processing program.

  In order to solve the above-described problem, the present invention includes a communication interface providing unit, a communication plug-in unit, and a communication protocol engine unit, and the communication interface providing unit includes an interface for calling a method related to remote calling. In response to the call of the interface, the method is requested via the predetermined interface to the communication plug-in means dynamically associated with the execution of serialization and deserialization according to a predetermined communication protocol, In response to a request through the predetermined interface, the communication plug-in means requests the communication protocol engine means corresponding to the communication plug-in means to execute the serialization and deserialization, and the communication protocol engine means Said And executes based Realize and deserialization to any of the specifications of a plurality of specifications.

  In such an information processing apparatus, it is possible to reduce the influence on the upper program due to the specification of the lower program module used for executing communication by a predetermined communication protocol.

  According to the present invention, an information processing apparatus, an information processing method, and an information processing program capable of reducing the influence on a higher-order program due to specifications of a lower-order program module used for executing communication using a predetermined communication protocol Can be provided.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing an example of a system configuration in the embodiment of the present invention. In the figure, one or more multifunction peripherals 1 and one or more servers 2 are connected via a network 3 (whether wired or wireless) such as a LAN (Local Area Network). The multifunction device 1 is an image forming apparatus that realizes a copy function, a print function, a scanner function, a FAX function, and the like in a single casing, and is an example of an information processing apparatus in the present embodiment. Communication between each MFP 1 and each server 2 is performed by SOAP (Simple Object Access Protocol). The multi function device 1 calls the function of the Web service in the server 2 by SOAP RPC (Remote Procedure Call). The server 2 executes the called function and returns a response to the multifunction device 1. There may be a multifunction device 1 that functions as the server 2. In this case, a service execution request (SOAP request) and a reply to the response (SOAP response) are performed between the multifunction devices 1.

  FIG. 2 is a diagram illustrating an example of a hardware configuration of the multifunction peripheral according to the embodiment of the present invention. As the hardware of the multifunction device 1, there are a controller 601, an operation panel 602, a facsimile control unit (FCU) 603, an imaging unit 604, and a printing unit 605.

  The controller 601 includes a CPU 611, ASIC 612, NB621, SB622, MEM-P631, MEM-C632, HDD (hard disk drive) 633, memory card slot 634, NIC (network interface controller) 641, USB device 642, IEEE 1394 device 643, Centronics device. 644.

  The CPU 611 is an IC for various information processing. The ASIC 612 is an IC for various image processing. The NB 621 is a north bridge of the controller 601. The SB 622 is a south bridge of the controller 601. The MEM-P 631 is a system memory of the multifunction device 1. The MEM-C 632 is a local memory of the multifunction machine 1. The HDD 633 is storage of the multifunction device 1. The memory card slot 634 is a slot for setting a memory card 635. The NIC 641 is a controller for network communication using a MAC address. The USB device 642 is a device for providing a USB standard connection terminal. The IEEE 1394 device 643 is a device for providing a connection terminal of the IEEE 1394 standard. The Centronics device 644 is a device for providing connection terminals of Centronics specifications. The operation panel 602 is hardware (operation device) for an operator to input to the multifunction device 1 and hardware (display device) for an operator to obtain an output from the multifunction device 1.

  FIG. 3 is a diagram illustrating a software configuration example of the multifunction machine according to the embodiment of the present invention. As shown in the figure, the software of the multifunction device 1 includes a basic platform 10, a system service 20, and one or more applications 30. Each software implements its function by a process executed by the CPU 611 by a program recorded in the HDD 633 or the memory card 635.

  The basic platform 10 includes an OS (Operating System) 11, a JVM (Java (registered trademark) Virtual Machine) 12, an OSGi (Open Services Gateway Initiative) framework 13, and the like, and provides an execution environment for the system service 20 and the application 30. To do.

  The OS 11 is a so-called OS (Operating System). The JVM 12 converts Java (registered trademark) bytecode into native code operable on the OS 11 and executes it. The OSGi framework 13 is a standardized technology by the OSGi Alliance, and is a software platform that provides an execution environment for software components created based on an open software componentization technology based on the Java (registered trademark) language. On the OSGi framework 13, Java (registered trademark) language software is implemented in the form of software components called “bundles”. One bundle is constituted by one JAR (Java (registered trademark) ARchive) file, and can be installed dynamically independently (without restarting the apparatus).

  The system service 20 is a part that provides functions (services) commonly used by various applications 30, and includes a SOAP communication control unit 21, an HTTP (HyperText Transfer Protocol) communication control unit 22, and the like.

  The SOAP communication control unit 21 controls communication using SOAP. The HTTP communication control unit 22 controls HTTP communication for transferring a SOAP message.

  The application 30 is software that provides a function with a higher degree of application using the system service 20. In the present embodiment, it is positioned as a user of the SOAP communication control unit 21.

  The SOAP communication control unit 21 will be described in more detail. FIG. 4 is a diagram illustrating a configuration example of the SOAP communication control unit. 4, the same parts as those in FIG. 3 are denoted by the same reference numerals. In the figure, the SOAP communication control unit 21 includes SOAP engines 211a and 211b (hereinafter, collectively referred to as “SOAP engine 211”) and SOAP communication plug-ins 212a and 212b (hereinafter collectively referred to as “SOAP communication plug”). And a SOAP communication module 213.

  The SOAP engine 211 is an implementation of SOAP for calling a method (method of the Web service 20 in the server 20) defined by WSDL (Web Services Description Language) by RPC (Remote Procedure Call). There is a program module called. Therefore, the SOAP engine 211 is implemented according to the definition of WSDL. The SOAP engine 211 mainly executes serialization and deserialization of a SOAP message. In the present embodiment, the SOAP engine 211a and the SOAP engine 211b have different implementations. Therefore, the interpretable SOAP message format is different. Also, the SOAP engine 211a and the SOAP engine 211b may have different interfaces to the user (software) side. Therefore, different implementations are required on the user side when using the SOAP engine 211a and when using the SOAP engine 211b.

  The SOAP communication plug-in 212 absorbs the specifications specific to each SOAP engine 211, and causes the SOAP engine 211 to execute serialization and deserialization in response to a predetermined interface call with the SOAP communication module 213. It is. The SOAP communication plug-in 212 is implemented for each SOAP engine 211. For example, the SOAP communication plug-in 212a corresponds to the SOAP engine 211a, and the SOAP communication plug-in 212b corresponds to the SOAP engine 212b.

  The SOAP communication module 213 can be used by dynamically switching the SOAP communication plug-in 212 and is a program module that provides the application 30 with a common interface with respect to differences in the SOAP engine 211. Therefore, the application 30 can execute a web service call (remote method call) without being aware of the difference of the SOAP engine 211 by the interface provided by the SOAP communication module 213. However, the SOAP communication module 213 provides a method defined by WSDL to an application. Therefore, the SOAP communication module 213 is mounted according to the definition of WSDL.

  The HTTP client service 221 is a program module included in the HTTP communication control unit 22 and controls transmission of an HTTP request.

  Each SOAP communication plug-in 212 and SOAP communication module 213 are each implemented as a bundle or a JAR file that operates on the OSGi framework 13.

  In the figure, only two SOAP engines 211 are shown, but three or more SOAP engines 211 may exist. However, only one SOAP engine 211 can be used at a certain time. That is, as shown in the figure, in the state where the two SOAP engines 211 and the two SOAP communication plug-ins 212 are installed, only one of the SOAP engine 211 and the SOAP communication plug-in 212 that are actually effective is available. .

  The SOAP communication module 213 and the SOAP communication plug-in 211 will be described in more detail. FIG. 5 is a diagram illustrating a class configuration example of the SOAP communication module and the SOAP communication plug-in.

  In the figure, a SOAP communication module 213 includes an activation class 2131, a SOAP communication plug-in detection class 2132, a SOAP client generation class 2133, a SOAP client service interface class 2134, a SOAP client service class 2135, a SOAP client plug-in interface class 2136, a schema. The generated interface class 2137, the schema 1 interface class 2138-1, the schema n interface class 2138-2, and the like.

  The activation class 2131 is a class that activates initial processing when the SOAP communication module 213 is activated. The activation class 2131 has an activation method. The activation method accepts an activation request for the SOAP communication module 213 from the OSGi framework 13 and activates an initial process at activation.

  The SOAP communication plug-in detection class 2132 is a class for starting processing for making the SOAP communication plug-in 212 available in response to activation of the SOAP communication module 213 or detection of installation of a new SOAP communication plug-in 212. It is.

  The SOAP communication plug-in detection class 2132 includes an activation reception method, a plug-in detection reception method, a plug-in listener registration method, and the like. The activation reception method receives activation notification of the SOAP communication module 213 from the activation class 2131 and activates processing for making the currently valid SOAP communication plug-in 212 available accordingly. The plug-in detection acceptance method accepts the installation notification of the SOAP communication plug-in 212 from the OSGi framework 13 and activates a process for making the newly installed SOAP communication plug-in 212 available in response. The plug-in listener registration method requests the OSGi framework 13 to notify the OSGi framework 13 of the installation of new software (bundle). That is, the installation of the SOAP communication plug-in 212 is notified to the SOAP communication plug-in detection class 2132 through the plug-in detection acceptance method in response to a request to the OSGi framework 13 by the plug-in listener registration method.

  The SOAP client generation class 2133 is a class for generating or deleting the association between the SOAP communication plug-in 212 that is currently valid and the SOAP communication module 213. The SOAP client generation class 2133 has a SOAP client service generation method, a SOAP client service deletion method, and the like. The SOAP client service generation method generates an association with the SOAP communication plug-in 212 by generating an instance of the SOAP client service 2135. The SOAP client service deletion method deletes the association with the SOAP communication plug-in 212 by deleting the instance of the SOAP client service 2135.

  The SOAP client service interface class 2134 is a virtual class in which an interface for calling a method of a Web service defined in WSDL is defined. “SOAP action 1 execution”, “SOAP action 2 execution” and the like illustrated in the SOAP client service interface class 2134 represent methods defined in WSDL. The application 30 can call the function of the Web service transparently by calling the method of the SOAP client service interface class 2134.

  The SOAP client service class 2135 is a class in which the implementation of the interface defined in the SOAP client service interface class 2134 is defined. The SOAP client service class 2135 has a SOAP client attribute. The SOAP client attribute is an attribute according to the SOAP client plug-in interface type, and holds an association with the SOAP communication plug-in 212 that is a usage target. With this association, the SOAP communication plug-in 212 can be used.

  The SOAP client interface class 2136 is a virtual class in which methods to be implemented by the SOAP communication plug-in 212 are defined. The method includes a method for serializing a SOAP message (for example, a SOAP action 1 serialization method and a SOAP action n serialization method) and a method for deserializing a de SOAP message for each method defined in WSDL.

  The schema generation interface 213 is a class that generates a schema entity. In this embodiment, a schema means a data type (including basic data types and structures). That is, the schema generation interface 213 generates entities of various data types used as arguments and return values of Web service methods.

  The schema 1 interface class 2138-1 and the schema n interface class 2138n (hereinafter collectively referred to as “schema interface class 2138”) are virtual classes representing schemas (data types) and are defined for each schema. Therefore, the instance (strictly, an instance of a subclass of the schema interface class 2138) becomes the data of the schema itself. Each schema interface class 2138 has a method for setting and acquiring a value of the schema.

  Among the above, the SOAP client service interface class 2134, the schema generation interface class 2137, and the schema interface class 2138 are directly used (operated) by the application 30.

  On the other hand, the SOAP communication plug-in classes 212a and 212b are composed of a SOAP client class 2121, a schema generation class 2122, a schema 1 class 2123-1, a schema n class 2133-2, and the like. When generically referring to the SOAP communication plug-in classes 212a and 212b, the reference numeral “a” or “b” is omitted in order to distinguish them.

  The SOAP client class 2121 is a subclass of the SOAP client plug-in interface class 2136. In the SOAP client class 2121, processing for executing serialization and deserialization using the corresponding SOAP engine 211 is implemented.

  The schema generation class 2122 is a subclass of the schema generation interface 2137, and a schema entity generation process corresponding to the corresponding SOAP engine 211 is implemented.

  The schema 1 class 2213-1 and the schema class 2133-2 (hereinafter collectively referred to as “schema class 2123”) are subclasses of the schema interface class 2138 related to the respective schemas (data types), and corresponding SOAP engines. A process for operating a schema entity corresponding to 211 is implemented.

  As described above, each SOAP communication plug-in 212 inherits the interfaces defined in the SOAP communication module 213 (SOAP client plug-in interface 2136, schema generation interface 2137, schema interface class 2138, etc.), thereby The communication module 213 can be called by a predetermined interface. In addition, classes constituting the SOAP communication plug-in 212 are implemented by a predetermined class name scheduled by the SOAP communication module 213.

  Hereinafter, a processing procedure related to SOAP communication in the multifunction machine 1 will be described. FIG. 6 is a sequence diagram for explaining a processing procedure when the SOAP communication module is activated. In the sequence diagram, an instance (object) of each class is assigned the same reference number as that class. An instance of “XXX class” is referred to as “XXX object”.

  For example, when the MFP 1 is activated, the OSGi framework 13 requests activation of the SOAP communication module 213 by calling an activation method of the activation object 2131 (S101). The activation object 2131 calls the activation reception method of the SOAP communication plug-in detection object 2132 in response to the activation method call (S102). The SOAP communication plug-in detection object 2132 calls its own plug-in installation listener registration method in response to the call of the activation reception method (S103). Subsequently, the SOAP communication plug-in detection object 2132 requests the OSGi framework 13 to notify when the software is installed in the plug-in installation listener registration method (S104). In the request, identification information (for example, reference) of the SOAP communication plug-in detection object 2132 is passed to the OSGi framework 13.

  Subsequently, the SOAP communication plug-in detection object 2132 requests to make the currently valid SOAP communication plug-in 212 available by calling the SOAP client service generation method of the SOAP client generation object 2133 (S105). The SOAP client generation object 2133 determines the class names of the SOAP client class 2121 and the schema generation class 2122 in the currently valid SOAP communication plug-in 212 in response to the call of the SOAP client service generation method.

  The currently valid SOAP communication plug-in 212 may be determined based on information recorded in a storage device such as the HDD 633. Specifically, if the SOAP communication plug-in 212 is installed in a predetermined location (folder) with a predetermined name (plug-in name), the SOAP communication plug-in 212 is based on a file stored in the folder. It can be discriminated. The class names of the SOAP client class 2121 and the schema generation class 2122 may be determined based on definition information in the package (JAR file) of the SOAP communication plug-in 212. Here, it is assumed that the currently effective SOAP communication plug-in 212 is the SOAP communication plug-in 212a.

  Subsequently, the SOAP client generation object 2133 generates (instantiates) a SOAP client service object 2135 (S106). At this time, for example, the class name of the SOAP client class 2121a in the SOAP communication plug-in 212a is delivered to the SOAP client service object 2135 as an argument of the constructor.

  In response to the generation, the SOAP client service object 2135 generates (instantiates) the SOAP client object 2121a of the SOAP communication plug-in 212a based on the delivered class name (S107). The SOAP client service object 2135 holds the reference of the generated SOAP client object 2121a in the SOAP client attribute.

  Subsequently, the SOAP client generation object 2133 generates (instantiates) the schema generation interface object 2137 (S108). At this time, for example, the class name of the schema generation class 2122a in the SOAP communication plug-in 212a is passed to the schema generation interface object 2137 as an argument of the constructor.

  In response to the generation, the schema generation interface object 2137 generates (instantiates) the schema generation object 2122a of the SOAP communication plug-in 212a based on the delivered class name (S109). The schema generation interface object 2137 holds a reference to the generated schema generation object 2122a.

  As described above, SOAP communication using the SOAP engine 211a can be performed via the SOAP communication plug-in 212. The SOAP engine 11 needs to be installed in advance.

  Next, FIG. 7 is a sequence diagram for explaining a processing procedure when the SOAP communication module is used by an application.

  The application 30 generates a schema 1 object 2123a-1 corresponding to a schema (here, schema 1) used in a method called by SOAP (S201). Strictly speaking, the schema object 2123 is generated via the schema generation object 212a, but is omitted here for convenience.

  Subsequently, the application 30 sets a value for the generated schema 1 object 2133a-1 (S202). Subsequently, the application 30 calls a desired method (for example, “SOAP action 1 execution method”) among Web service methods defined in the SOAP client service interface 2134 with respect to the SOAP client service object 2135. (S203). A schema 1 object 2123a-1 is designated as an argument of the method.

  Subsequently, the SOAP client service object 2135 requests the SOAP client object 2121a of the SOAP communication plug-in 212a whose reference is held in the SOAP client attribute to serialize the request for calling the SOAP action 1 execution method (S204). . The SOAP client object 2121a causes the SOAP engine 211a to perform serialization and returns the result to the SOAP client service object 2135 (S205).

  Subsequently, the SOAP client service 2135 requests the HTTP client service 221 to transmit a SOAP message (SOAP request) including serialized XML (eXtensible Markup Language) data (S206). The HTTP client service 221 transmits a SOAP request to the server 2 and receives a SOAP message (SOAP response) returned as a processing result from the server 2. The HTTP client service 221 returns the received SOAP response to the SOAP client service object 2135 (S207).

  The SOAP client service object 2135 requests the SOAP client object 2121a of the SOAP communication plug-in 212a to deserialize the returned SOAP response (conversion from the XML format to the data format according to the program language) (S208). The SOAP client object 2121a causes the SOAP engine 211a to execute deserialization and returns the result to the SOAP client service object 2135 (S209).

  The SOAP client service object 2135 returns the deserialized data (for example, the return value of the method) to the application 30 (S210). If the argument related to the schema 1 object 2123a-1 is an IN / OUT type, the application 30 acquires a value from the schema 1 object 2123a-1 (S211 and S212). Subsequently, the application 30 deletes the unnecessary schema 1 object 2123a-1 (S213).

  As described above, the application 30 does not need to directly communicate with the SOAP engine 211. Therefore, even if the SOAP engine 211 is replaced, the same method can be called by the same procedure (source code).

  Next, FIG. 8 is a sequence diagram for explaining a processing procedure when a new SOAP communication plug-in is installed. In the figure, a processing procedure when the SOAP communication plug-in 212b is installed in a state where the SOAP communication plug-in 212a is available will be described.

  When new software (bundle) is installed on the OSGi framework 13, the OSGi framework 13 determines the identification name (bundle name or plug-in name, etc.) of the installed software based on the request in step S104 in FIG. ) As an argument, the plug-in detection reception method of the SOAP communication plug-in detection object 2132 is called to notify that the installation has been performed (S301).

  The SOAP communication plug-in detection object 2132 determines whether or not the installed software is the SOAP communication plug-in 212 in response to the call of the plug-in detection reception method (S302). This determination may be made by comparing the identification name specified in the argument with the name scheduled as the SOAP communication plug-in 212.

  If the installed software is not the SOAP communication plug-in 212, the subsequent processing is not executed. When the installed software is the SOAP communication plug-in 212, the SOAP communication plug-in detection object 2132 calls the SOAP client service deletion method of the SOAP client generation object 2133, so that the SOAP communication plug-in 211 a currently used is used. An invalidation is requested (S303).

  The SOAP client generation object 2133 deletes the SOAP client service object 2135 in response to calling the SOAP client service deletion method (S304). In response to the deletion, the SOAP client service object 2135 deletes the SOAP client object 2121a and the schema generation object 2122a of the SOAP communication plug-in 212a (S305, S306).

  Thus, the association between the SOAP communication module 213 and the SOAP communication plug-in 212a is deleted.

  Subsequently, in steps S307 to S311, processing similar to that in steps S105 to S109 in FIG. 6 is executed for the SOAP communication plug-in 212b. As a result, the SOAP communication plug-in 212b can be used.

  Next, FIG. 9 is a sequence diagram for explaining a processing procedure when uninstalling the SOAP communication plug-in. In the figure, a processing procedure when the SOAP communication plug-in 212b is uninstalled in a state where the SOAP communication plug-in 212b is available will be described.

  When the software (bundle) on the OSGi framework 13 is uninstalled, the OSGi framework 13 determines the identification name (bundle name, plug-in name, etc.) of the uninstalled software based on the request in step S104 in FIG. ) As an argument, the plug-in detection reception method of the SOAP communication plug-in detection object 2132 is called to notify that the uninstallation has been performed (S401).

  The SOAP communication plug-in detection object 2132 determines whether or not the uninstalled software is the SOAP communication plug-in 212 in response to the call of the plug-in detection reception method (S402).

  If the uninstalled software is not the SOAP communication plug-in 212, the subsequent processing is not executed. When the uninstalled software is the SOAP communication plug-in 212, in steps S403 to S406, processing similar to that in steps S303 to S306 in FIG. 8 is executed for the SOAP communication plug-in 212b. As a result, the association between the SOAP communication module 213 and the SOAP communication plug-in 212b is deleted, and the SOAP communication plug-in 212b and the SOAP engine 211b are not used.

  As described above, according to the MFP 1 in the present embodiment, the SOAP communication plug-in 212 absorbs the specifications specific to each SOAP engine 211. In addition, the SOAP communication module 213 automatically determines the SOAP communication plug-in 212 to be used. Therefore, the application 30 does not need to be aware of which SOAP engine 211 is used, and only needs to be aware of the interface provided by the SOAP communication module 213. Therefore, it is not necessary to modify the source code of the application 30 according to the SOAP engine 211 used.

  In addition, the SOAP communication module 213 and the SOAP communication plug-in 212 exchange with each other through a predetermined interface. Therefore, the association between the SOAP communication module 213 and the SOAP communication plug-in 212 can be made dynamic, and even when a new SOAP communication plug-in 212 is added, the source code of the SOAP communication module 213 Can be dealt with without correcting.

  Although the present embodiment has been described with SOAP as an example of the communication protocol, the scope of application of the present invention is not limited to SOAP.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

It is a figure which shows the system configuration example in embodiment of this invention. FIG. 2 is a diagram illustrating an example of a hardware configuration of a multifunction machine according to an embodiment of the present invention. FIG. 3 is a diagram illustrating a software configuration example of a multifunction machine according to an embodiment of the present invention. It is a figure which shows the structural example of a SOAP communication control part. It is a figure which shows the class structural example of a SOAP communication module and a SOAP communication plug-in. It is a sequence diagram for demonstrating the process sequence at the time of SOAP communication module starting. It is a sequence diagram for demonstrating the process sequence at the time of the SOAP communication module use by an application. It is a sequence diagram for demonstrating the process sequence at the time of installation of a new SOAP communication plug-in. It is a sequence diagram for demonstrating the process sequence at the time of uninstallation of a SOAP communication plug-in.

Explanation of symbols

1 MFP 2 Server 3 Network 10 Basic platform 11 OS
12 JVM
13 OSGi framework 20 System service 21 SOAP communication control unit 22 HTTP communication control unit 22
30 Application 211a SOAP engine 211b SOAP engine 212a SOAP communication plug-in 212b SOAP communication plug-in 213 SOAP communication module 221 HTTP client service 604 Imaging unit 605 Printing unit 601 Controller 602 Operation panel 603 Facsimile control unit 611 CPU
612 ASIC
621 NB
622 SB
631 MEM-P
632 MEM-C
633 HDD
634 Memory card slot 635 Memory card 641 NIC
642 USB device 643 IEEE 1394 device 644 Centronics device 2131 Startup class 2132 SOAP communication plug-in detection class 2133 SOAP client generation class 2134 SOAP client service interface class 2135 SOAP client service class 2136 SOAP client plug-in interface class 2137 Schema generation interface class 2138-1 Schema 1 interface class 2138-2 Schema n interface class 2121a SOAP client class 2122a Schema generation class 2123a-1 Schema 1 class 2133a-2 Schema n class

Claims (12)

Communication interface providing means, communication plug-in means, and communication protocol engine means,
The communication interface providing means includes a first interface for invoking methods defined as a target for a remote call, in response to a call of the method through the first interface, the predetermined communication protocol for the method Requesting the communication plug-in means that is dynamically associated to execute serialization and deserialization according to the second interface,
The communication plug-in unit, in response to a request through the second interface, to the communication protocol engine means that the communication plug-in unit corresponding, the execution of the serialization and deserialization, any of the plurality of specifications Request via a third interface based on
The communication protocol engine means, in response to a request through the third interface, and run on the basis of the serialization and deserialization any specification of the plurality of specifications,
The information processing apparatus according to claim 1, wherein the first interface is common to the plurality of specifications .   The information processing apparatus according to claim 1, wherein the communication interface providing unit determines the communication plug-in unit effective in the information processing apparatus and associates the communication plug-in unit.   The information processing apparatus according to claim 1, wherein the communication interface providing unit associates the communication plug-in unit related to the program in response to detection of installation of a program that realizes the communication plug-in unit. 4. The communication interface providing unit deletes the association with the communication plug-in unit related to the program in response to detection of uninstallation of the program that realizes the communication plug-in unit. The information processing apparatus according to claim 1. An information processing method executed by an information processing apparatus having communication interface providing means, communication plug-in means, and communication protocol engine means,
The communication interface provides means comprises a first interface for invoking methods defined as an object of remote calls, the in response to the first invocation of the method via the interface, a predetermined communication protocol for the method A step of requesting the communication plug-in means that is dynamically associated with the execution of serialization and deserialization according to a predetermined second interface;
In response to a request through the second interface, the communication plug-in means performs the serialization and deserialization on the communication protocol engine means corresponding to the communication plug-in means , and performs any of the specifications. A request through a third interface based on any specification ,
The communication protocol engine unit, have a the procedure which the response to the third request via an interface, executes the basis the serialization and deserialization any specification of the plurality of specifications,
The information processing method , wherein the first interface is common to the plurality of specifications .   6. The information processing method according to claim 5, further comprising a step of determining the communication plug-in means effective in the information processing apparatus and associating the communication plug-in means.   7. The information according to claim 5, wherein the communication interface providing means includes a procedure for associating the communication plug-in means related to the program in response to detection of installation of a program that realizes the communication plug-in means. Processing method.   6. The interface providing unit includes a procedure of deleting association with the communication plug-in unit related to the program in response to detection of uninstallation of the program that realizes the communication plug-in unit. The information processing method according to claim 7. Computer
Function as communication interface providing means, communication plug-in means, and communication protocol engine means;
The communication interface providing means includes a first interface for invoking methods defined as a target for a remote call, in response to a call of the method through the first interface, the predetermined communication protocol for the method Requesting the communication plug-in means that is dynamically associated to execute serialization and deserialization according to the second interface,
The communication plug-in unit, in response to a request through the second interface, to the communication protocol engine means that the communication plug-in unit corresponding, the execution of the serialization and deserialization, any of the plurality of specifications Request via a third interface based on
The communication protocol engine means, in response to a request through the third interface, and run on the basis of the serialization and deserialization any specification of the plurality of specifications,
The information processing program characterized in that the first interface is common to the plurality of specifications .   The information processing program according to claim 9, wherein the communication interface providing unit determines the communication plug-in unit effective in the information processing apparatus and associates the communication plug-in unit.   The information processing program according to claim 9 or 10, wherein the communication interface providing means associates the communication plug-in means related to the program in response to detection of installation of a program that realizes the communication plug-in means.   12. The interface providing unit, according to detection of uninstallation of a program that realizes the communication plug-in unit, deletes the association with the communication plug-in unit related to the program. An information processing program according to one item.

Images