Abstract: A method of generating stereoscopic display contents includes obtaining, from a Red, Green, Blue plus Distance (RGB-D) image using a processor, a first Red, Green, and Blue (RGB) image and a depth image; determining, based on depth values in the depth image, a first disparity map in accordance with the RGB-D image; determining a second disparity map and a third disparity map by transforming the first disparity map using a disparity distribution ratio; and generating, by the processor, the pair of stereoscopic images comprising a second RGB image and a third RGB image, wherein the second RGB image is generated by shifting a first set of pixels in the first RGB image based on the second disparity map, and the third RGB image is generated by shifting a second set of pixels in the first RGB image based on the third disparity map.

Abstract: An optical multiplexer having two or more optic elements with optic coating or layers that act as optic filters. The optic elements are configured to receive optic signals and the coating on the optic elements allow certain wavelengths to pass therethrough while other frequencies are reflected. One configuration includes a first, second, third and fourth optic elements or substrates which are configured to combine four optic signals into a reduced number, such as a single combined signal. Coatings are placed between the optic elements such that each coating is a type of filter that reflects or allows passage of certain frequencies. At least one coating is selected to reflect an optic signal while the other coatings are selected to selectively reflect or pass optic signals (beams) based on the wavelength of the optic signal and the coating.

Abstract: A framework (referred to herein as Application Integration Architecture, or AIA) that formalizes and orchestrates activities in an SOA development lifecycle. In one set of embodiments, AIA can capture development-related information in a shared data store and cause the information to flow in an automated or semi-automated manner from one lifecycle phase to the next as the lifecycle progresses. This information flow can, in turn, facilitate automations at each lifecycle phase for the responsible stakeholders (e.g., solution architects, developers, installation developers, etc.), thereby enforcing SOA best practices, enhancing development productivity, and ensuring the quality of the final SOA deliverables.

Abstract: A framework (referred to herein as Application Integration Architecture, or AIA) that formalizes and orchestrates activities in an SOA development lifecycle. In one set of embodiments, AIA can capture development-related information in a shared data store and cause the information to flow in an automated or semi-automated manner from one lifecycle phase to the next as the lifecycle progresses. This information flow can, in turn, facilitate automations at each lifecycle phase for the responsible stakeholders (e.g., solution architects, developers, installation developers, etc.), thereby enforcing SOA best practices, enhancing development productivity, and ensuring the quality of the final SOA deliverables.

Abstract: A framework (referred to herein as Application Integration Architecture, or AIA) that formalizes and orchestrates activities in an SOA development lifecycle. In one set of embodiments, AIA can capture development-related information in a shared data store and cause the information to flow in an automated or semi-automated manner from one lifecycle phase to the next as the lifecycle progresses. This information flow can, in turn, facilitate automations at each lifecycle phase for the responsible stakeholders (e.g., solution architects, developers, installation developers, etc.), thereby enforcing SOA best practices, enhancing development productivity, and ensuring the quality of the final SOA deliverables.

Abstract: Techniques for conditionally deploying artifacts of a software application (e.g., a SOA application). In one set of embodiments, a deployment plan can be generated that specifies a list of artifacts to be deployed for the application. At a time of deployment, the deployment plan can be retrieved and processed by an installation module to carry out the deployment process. As part of this processing, the installation module can determine, for each artifact in the deployment plan, whether the artifact is associated with a user-defined condition. If such an association is found, the installation module can evaluate the user-defined condition and execute conditional deployment logic for the artifact based on the outcome of the evaluation. In this manner, the deployment activities to be carried out for the application can be dynamically modified at the time of deployment.

Abstract: A framework (referred to herein as Application Integration Architecture, or AIA) that formalizes and orchestrates activities in an SOA development lifecycle. In one set of embodiments, AIA can capture development-related information in a shared data store and cause the information to flow in an automated or semi-automated manner from one lifecycle phase to the next as the lifecycle progresses. This information flow can, in turn, facilitate automations at each lifecycle phase for the responsible stakeholders (e.g., solution architects, developers, installation developers, etc.), thereby enforcing SOA best practices, enhancing development productivity, and ensuring the quality of the final SOA deliverables.

Abstract: A framework (referred to herein as Application Integration Architecture, or AIA) that formalizes and orchestrates activities in an SOA development lifecycle. In one set of embodiments, AIA can capture development-related information in a shared data store and cause the information to flow in an automated or semi-automated manner from one lifecycle phase to the next as the lifecycle progresses. This information flow can, in turn, facilitate automations at each lifecycle phase for the responsible stakeholders (e.g., solution architects, developers, installation developers, etc.), thereby enforcing SOA best practices, enhancing development productivity, and ensuring the quality of the final SOA deliverables.

Abstract: A framework (referred to herein as Application Integration Architecture, or AIA) that formalizes and orchestrates activities in an SOA development lifecycle. In one set of embodiments, AIA can capture development-related information in a shared data store and cause the information to flow in an automated or semi-automated manner from one lifecycle phase to the next as the lifecycle progresses. This information flow can, in turn, facilitate automations at each lifecycle phase for the responsible stakeholders (e.g., solution architects, developers, installation developers, etc.), thereby enforcing SOA best practices, enhancing development productivity, and ensuring the quality of the final SOA deliverables.

Abstract: Inbound processing of web service request messages at runtime is enhanced by providing validation of the message structure against corresponding schema, at an intermediary web service server rather than at the web service level (e.g., entirely by a web service application). Hence, there is minimal delay in responding to the client upon determining an invalid message structure, and unnecessary processing of invalid messages by the web service application is avoided.

Abstract: A web services system provides web services interfaces to applications having native interfaces with different types of synchrony. The web services interfaces can have the same or different type of synchrony than the underlying application. The web services layer translates a web services request from a client to corresponding function calls to applications. Upon receiving a response from an application, the web services layer translates the response back to a web services format and forwards it to the client. A naming convention is used to define the names of the data types and operations in the web services interface corresponding with data types and functions of the application. A function prefix can be used to specify a namespace in the web services interface unique to the application. A web services namespace is assigned to tokens so that requests for asynchronous web services are diverted to a general web services routine.

Abstract: Techniques for conditionally deploying artifacts of a software application (e.g., a SOA application). In one set of embodiments, a deployment plan can be generated that specifies a list of artifacts to be deployed for the application. At a time of deployment, the deployment plan can be retrieved and processed by an installation module to carry out the deployment process. As part of this processing, the installation module can determine, for each artifact in the deployment plan, whether the artifact is associated with a user-defined condition. If such an association is found, the installation module can evaluate the user-defined condition and execute conditional deployment logic for the artifact based on the outcome of the evaluation. In this manner, the deployment activities to be carried out for the application can be dynamically modified at the time of deployment.

Abstract: A web services system provides web services interfaces to applications having native interfaces with different types of synchrony. The web services interfaces can have the same or different type of synchrony than the underlying application. The web services layer translates a web services request from a client to corresponding function calls to applications. Upon receiving a response from an application, the web services layer translates the response back to a web services format and forwards it to the client. A naming convention is used to define the names of the data types and operations in the web services interface corresponding with data types and functions of the application. A function prefix can be used to specify a namespace in the web services interface unique to the application. A web services namespace is assigned to tokens so that requests for asynchronous web services are diverted to a general web services routine.

Abstract: A framework (referred to herein as Application Integration Architecture, or AIA) that formalizes and orchestrates activities in an SOA development lifecycle. In one set of embodiments, AIA can capture development-related information in a shared data store and cause the information to flow in an automated or semi-automated manner from one lifecycle phase to the next as the lifecycle progresses. This information flow can, in turn, facilitate automations at each lifecycle phase for the responsible stakeholders (e.g., solution architects, developers, installation developers, etc.), thereby enforcing SOA best practices, enhancing development productivity, and ensuring the quality of the final SOA deliverables.

Abstract: A framework (referred to herein as Application Integration Architecture, or AIA) that formalizes and orchestrates activities in an SOA development lifecycle. In one set of embodiments, AIA can capture development-related information in a shared data store and cause the information to flow in an automated or semi-automated manner from one lifecycle phase to the next as the lifecycle progresses. This information flow can, in turn, facilitate automations at each lifecycle phase for the responsible stakeholders (e.g., solution architects, developers, installation developers, etc.), thereby enforcing SOA best practices, enhancing development productivity, and ensuring the quality of the final SOA deliverables.

Abstract: A framework (referred to herein as Application Integration Architecture, or AIA) that formalizes and orchestrates activities in an SOA development lifecycle. In one set of embodiments, AIA can capture development-related information in a shared data store and cause the information to flow in an automated or semi-automated manner from one lifecycle phase to the next as the lifecycle progresses. This information flow can, in turn, facilitate automations at each lifecycle phase for the responsible stakeholders (e.g., solution architects, developers, installation developers, etc.), thereby enforcing SOA best practices, enhancing development productivity, and ensuring the quality of the final SOA deliverables.

Abstract: A framework (referred to herein as Application Integration Architecture, or AIA) that formalizes and orchestrates activities in an SOA development lifecycle. In one set of embodiments, AIA can capture development-related information in a shared data store and cause the information to flow in an automated or semi-automated manner from one lifecycle phase to the next as the lifecycle progresses. This information flow can, in turn, facilitate automations at each lifecycle phase for the responsible stakeholders (e.g., solution architects, developers, installation developers, etc.), thereby enforcing SOA best practices, enhancing development productivity, and ensuring the quality of the final SOA deliverables.

Abstract: A web services system provides web services interfaces to applications having native interfaces with different types of synchrony. The web services interfaces can have the same or different type of synchrony than the underlying application. The web services layer translates a web services request from a client to corresponding function calls to applications. Upon receiving a response from an application, the web services layer translates the response back to a web services format and forwards it to the client. A naming convention is used to define the names of the data types and operations in the web services interface corresponding with data types and functions of the application. A function prefix can be used to specify a namespace in the web services interface unique to the application. A web services namespace is assigned to tokens so that requests for asynchronous web services are diverted to a general web services routine.

Abstract: A computer-implemented method of testing interoperability of a web service against a plurality of web services tools may include steps of providing a web services description language file (WSDL) that describes the web service to be tested; selecting at least one of the plurality of web services tools; generating and compiling sets of proxy files for each selected web service tool based upon the provided WSDL file and loading the generated and compiled proxy files into memory; generating an XML test case for each of the generated and compiled sets of proxy files, the XML test case including dummy variables for each operation of the provided WSDL file; populating the generated XML test case with values for at least some of the dummy variables, and invoking a targeted web service from a selected client platform using the populated XML test case and providing results for each invocation.

Abstract: A web service broker transforms, at runtime, output data from client applications to the input data form required by various web services. Such transformations are based on data and/or parameter mappings that are accessible to the broker. Further, the broker accesses and invokes particular web services in the manner required by the web services. Such invocations are based on information regarding the access style, such as RPC style of communication, and encoding, such as SOAP, associated with respective web services. The broker provides a generic framework in that it is capable of supporting transformation of different data and data forms from many different applications to respective data that many different respective web services can use.