How-To : Silverlight accessing Java SOAP services (Part 2 – No Cross Domain : Tomcat/Eclipse)

The HowTo series demo Silverlight accessing Web Services in various configuration. In this post, we will demonstrate you a SOAP service consumed by a Silverlight client application where the Site of Origin hosts the Web Services. This scenario is categorized as a D2D scenario without cross-domain policy. The SOAP service Eclipse project and the Silverlight…

1

Tip : Cross Domain Policy when Self-Hosting your Services

This tip is about self hosting of services with the .Net WCF or Java Restlet framework. Cross-domain access is mandatory here since the Site of Origin does not host the services. Self hosting a service represents a quick & easy way to expose a Web Service for tests purpose. Yet, customization is extermely limited since self hosting does…

1

How-To : Silverlight accessing Java REST services (Part 2 – No Cross Domain : Tomcat/Eclipse)

The HowTo serie demoes Silverlight accessing Web Services in various configuration. In this post, we will demonstrate a REST service consumed by a Silverlight client application where the Site of Origin hosts the Web Services. This scenario is categorized as a D2D scenario without cross-domain policy. The XAP package, the REST service Eclipse project and…

3

How-To : Silverlight accessing Java SOAP services (Part 1 – Cross Domain : IIS + Tomcat)

The How-To series demo Silverlight accessing Web Services in various configuration. In this post, we will demonstrate a SOAP service consumed by a Silverlight client application. This scenario can be categorized as a D2D scenario with a cross domain policy. Both the Silverlight and SOAP service are available as an attachment to this post. Since…

3

How-To : Silverlight accessing Java REST services (Part 1 - Cross Domain : IIS + Tomcat)

The HowTo serie demoes Silverlight accessing Web Services in various configurations. In this post, we will demonstrate a REST service consumed by HTTP GET and POST requests issued from a Silverlight client application. This scenario can be categorized as a D2D scenario with a cross domain policy. The Silverlight example described below is available as…

1

D2D scenario : Developer Environment

This scenario is typically used in development phase when you are building a Silverlight rich client that connects to new business Logic. It is mandatory that the business logic is new to ensure you have enough control to enforce a configuration where the Site Of Origin and the Services Host reside on the same node….

8

Silverlight scenarios for Rich Internet Applications

From the architecture described in the previous post a cup of Silverlight, a drop of Architecture, you may experience several technical requirements : Infrastructure Security DMZ (if the application is internet facing), Secured transport (HTTPS) if private communication has to be enforced (Mandatory in B2B and B2C environments) Application Security Authentication may be Form, Windows…

6