Silverlight and Java Interoperability

Summary

This article provides some introductory guidance for Java Community developers who want to integrate Silverlight into the solution. Microsoft Silverlight is a cross-browser, Cross-platform, and Cross-platform Browser plug-in designed to design, develop, and publish the next-generation multimedia experience and rich-interface application network applications. This paper also introduces some background knowledge of Silverlight, its basic function and development idea, and describes how to locate Silverlight reasonably when developing rich client applications that support multiple media, and describes the architecture, advantages and limitations of Silverlight, and so on.

This article explores three different scenarios for Silverlight and Java interactions: SOAP Web Services, REST Web services, and aggregation (RSS) services. SOAP Web Services and Rest Web services are implemented through the tools in NetBeans. This article provides demo code for each interaction, and discusses the most appropriate scenario for applying the interaction. Silverlight can also interact directly with sockets, but is relatively complex and uncommon, and will be discussed later. This article focuses on the Silverlight-java interactive discussion and some architectural guidance for Silverlight 2 Beta 2.

Range

This article will focus on Silverlight-java interoperability. Create a Silverlight application from Visual Studio to help developers understand the following interoperability approaches:

Interoperability with SOAP Web services

Interoperability with REST services

Interoperability with aggregate (RSS) services

Silverlight can also interact with sockets, but is relatively complex, and this article will not be discussed.

Ultimate goal

Provides several alternatives for the Java community to implement basic Silverlight-java service interoperability.

Goal

The reader has an accurate understanding of what Silverlight is and what it uses.

The reader has a basic understanding of the architecture of Silverlight, its pros and cons.

By describing the three basic interop instances mentioned in the "Scope" section above, the issue of how Silverlight clients interact with Java Services provides a useful guide to readers.

Silverlight Introduction

Microsoft Silverlight is a cross-browser, Cross-platform, Cross-platform Browser plug-in designed to design, develop, and publish the next-generation multimedia experience and rich-interface application network applications. Silverlight is positioned to apply to rich Internet applications that can be quickly deployed to browsers. Silverlight is designed for Web page content connected to a host, and is characterized by a user's deep involvement in the interaction, and the application can run in any browser. "Use the Silverlight scenario.

Separating the user interface design from the underlying logic can significantly increase the productivity of the application Development Lifecycle (ADLC). With Microsoft expression and Microsoft Visual Studio, user interface designers and developers can play their respective roles and improve their cooperation with each other.

Extensible Application Markup Language (XAML) is an xml-based, descriptive language that supports process control and is designed specifically for user interface design. The. NET language is used to write background logic for the user interface, such as vb.net, C #, IronRuby, and IronPython. Both Windows presentation Foundation (WPF) and Silverlight use XAML.

The run-time environment of Silverlight is the foundation of its architecture. Silverlight 2 Beta 2 has a one-time download size of 4.6MB plug-ins that can be deployed to IE, Firefox, opera, or Safari browsers. A zip-formatted ". xap" file is a development package for Silverlight applications. This ". Xap" package contains the application and its interfaces for Silverlight plug-in control to run. This ". xap" file is in Visual Studio. NET, the client's ". xap" file will be updated every time it compiles. The Silverlight application (". XAP" package) can be deployed by any Web server.

Figure 1:web Silverlight in the browser sandbox

The Silverlight controller is embedded in an HTML Web page and is naturally contained in a Web browser's sandbox. MSDN has a technical article on the Silverlight Architecture overview that describes the Silverlight architecture in general, illustrating the status of Silverlight in the Microsoft User Experience (UX) program. It is very important that the client machine running in Silverlight does not need to install. NET. The necessary resources required to run Silverlight are all included in the Silverlight browser plug-in. All interoperation scenarios are based on Silverlight 2 Beta 2. The new features of Silverlight 2 Beta 2 are:

Framework language (Visual Basic.NET, C #, IronPython, IronRuby)

Storage separation

JSON, REST, Soap/ws-i, pox, and RSS Web Services (also support sockets)

Support WCF

Ado. NET Data Services

LINQ to Objects and LINQ to XML

DEEP Zoom Technology

XML programmable

Media Content Protection

Rich manageable control framework here is an example of a simple crossdomain.xml file: "