Web Services

TIBCO, WCF e Silverlight

Lorenzo Barbieri — Thu, 01 May 2008 13:09:05 GMT

Due annunci che sembrano scollegati, ma che fanno capire quanto il mercato sia maturo per entrambe le tecnologie (WCF & Silverlight):

At their user conference in San Francisco yesterday, TIBCO announced two integration initiatives to bring the TIBCO and Microsoft platforms closer together.

TIBCO is developing a TIBCO EMS transport channel for WCF. Although Microsoft doesn't have a formal certification process for releasing third-party WCF components, I got to do some code and design reviews over the last few months with the TIBCO developers to understand the work that they are doing. I am very pleased that it was possible to make TIBCO EMS fit naturally into the WCF model. This integration work benefits both Microsoft and TIBCO customers by expanding the reach of applications on each platform. I fully support the partner ecosystem in delivering WCF components and connectivity options that go beyond what Microsoft provides in the framework.
TIBCO is also going to be making use of Silverlight for development and deployment of Internet applications. Silverlight allows developers to reuse much of the tooling and knowledge that they have from desktop development when creating browser-based applications.

Fonte: TIBCO Announces WCF Integration

Un commento su Microsoft e SCA

Lorenzo Barbieri — Sun, 30 Sep 2007 08:17:33 GMT

A volte è interessante non pensare solo a WCF, Biztalk e in genere solo a SOA in "casa Microsoft", ma guardare anche a cosa sta succedendo dall'altra parte serve a capire come ci si sta muovendo.

Will Microsoft support Service Component Architecture (SCA)? It seems unlikely. After all, this new technology is controlled entirely by Microsoft's competitors. Still, even if Microsoft did decide to implement SCA, customers would see almost no benefit. Here's why.
...CUT...
Given the competitive realities, Microsoft supporting SCA today is about as likely as an embrace of EJB would have been a decade ago. Yet even if the company wanted to, there's not much there for Microsoft to embrace. Given SCA's complete focus on portability rather than interoperability, the set of programming languages it supports, and the minimalist nature of SCDL, Microsoft's support of this emerging technology would provide almost no benefit to customers.

Leggete tutto alla Fonte: Why Microsoft Should Not Support SCA

Technorati Tags: Interoperabilita'

Code Coverage di Web Services

Lorenzo Barbieri — Sat, 01 Sep 2007 08:36:22 GMT

Io preferisco sempre inserire la logica dei Web Services in una DLL separata, in modo che sia banale da testare con gli Unit Test, avere le informazioni di Code Coverage, etc...

Ma se proprio dovete avere il Code Coverage direttamente dei Web Services (ad esempio dovete verificare della logica contenuta esclusivamente negli ASMX o simili) allora potete seguire questa strada:

The following is the updated process for doing code coverage on web services.
1. Read our team blog on code coverage here, especially scenario 3. Please note the path to vsinstr and vsperfcmd is %vsinstalldir%\Team Tools\Performance tools
2. Build your product and test binaries.
3. Instrument your product binaries using vsinstr as detailed in the blog
4. Reset iis.
5. Start the code coverage collection using vsperfcmd /start… as detailed in the blog
6. Open a VS commandline and go to your binary drop location, eg. dd\tcm_1\binaries\x86dbg\bin\i386, run tests using mstest:
mstest /testcontainer:ActivitiesTests.dll and mstest /testcontainer:ActivityRuntimeTests.dll
7. Reset iis.
8. Stop the code coverage collection using vsperfcmd /shutdown
9. Open the .coverage file that you get in IDE, check the numbers.

Fonte: MSDN Forums

Technorati Tags: Code Coverage, Developer, Tester

BPEL for Windows Workflow Foundation CTP di Marzo

Lorenzo Barbieri — Sun, 18 Mar 2007 22:13:00 GMT

Inizia a prendere sempre più forma il supporto per BPEL (lo standard per fare workflow di web services) in WF.

BPEL è supportato dai maggiori produttori, ed ora lo è (anche se ancora non ufficialmente) anche in WF.

Attenzione però... BPEL non è uno standard COMPLETO per il Workflow... e questo permette a tutti i produttori di realizzare estensioni che poi non sono facilmente portabili da un ambiente all'altro, rendendolo di fatto molto limitato.

Lo trovate qui: http://www.microsoft.com/downloads/details.aspx?familyid=6d0daf00-f689-4e61-88e6-cbe6f668e6a3&displaylang=en&tm

Dovete interoperare con WSE 3.0/WCF da Java? Potete usare WSO2 Tungsten 1.0

Lorenzo Barbieri — Sun, 28 May 2006 01:02:00 GMT

E' un bel po' che non mi occupo più di Web Services interoperabili, ma preferisco tenermi aggiornato, non si sa mai...
Clicca il titolo per leggere tutto oppure vai alla fonte: WSO2 Tungsten 1.0

Quanto tempo è passato da TIP

Lorenzo Barbieri — Mon, 15 May 2006 20:14:00 GMT

La prima volta che ho sentito parlare di TIP era nel 2000... abituato ai protocolli binari... non ne capivo ancora bene le potenzialità...

Beh... quando vedo queste cose penso che è passato tanto tanto tempo...New WS-AtomicTransaction Configuration tools

Che ne pensate?

Un articolo e due presentazioni molto interessanti... architetture, web2.0, soa, standard, etc...

Lorenzo Barbieri — Tue, 02 May 2006 10:16:00 GMT

Clicca per i link...

Web Service Software Factory Community

Lorenzo Barbieri — Thu, 13 Apr 2006 05:30:00 GMT

Dal gruppo Pattern&Practice una nuova iniziativa:

The Service Factory is a cohesive collection of various forms of guidance that have been build with the primary goal of helping you build high quality connected solutions in a more consistent way with less effort. In addition to the forms of guidance you may have already seen from the patterns & practices team, there is a new form of guidance in here, called a guidance package, that allows guidance to be automated from inside Visual Studio 2005 through the use of a wizard-based dialog than can be modified (by an architect perhaps) to fit the needs of a specific solution.

La trovate qui: http://www.gotdotnet.com/codegallery/codegallery.aspx?id=6fde9247-53a8-4879-853d-500cd2d97a83

Il costo dell'utilizzo dei Sql Endpoints

Lorenzo Barbieri — Mon, 09 Jan 2006 14:04:00 GMT

Post molto interessante sul nuovo support dei webservices di Sql 2005 tramite HTTP.SYS senza passare da IIS.

Leggetelo perchè ne vale la pena. Mi piacciono molto le conclusioni:

[CUT]... But the data led me to the following conclusion: don’t use SQL endpoints unless you need web services without IIS; otherwise, just create a traditional web service using .NET, which calls the stored proc. After all, scaling web/middle tier is easy, scaling SQL is not.

Fonte: SYSK 36: The Cost of SQL EndPoints

Confronto tra WCF (Indigo) e SCA (Java)

Lorenzo Barbieri — Wed, 21 Dec 2005 15:13:00 GMT

SCA non la conoscevo, ma questo articolo di David Chappel mette in evidenza similitudini e differenze tra i due approcci...

Last month's announcement of Service Component Architecture (SCA) suggests that, in the not too distant future, choosing between Microsoft's Windows Communication Foundation (WCF) and SCA will displace significant parts of today's .NET vs. J2EE decision. The latest issue of my Opinari newsletter examines the similarities and differences between these two technologies, then takes a look at some of the challenges facing SCA's creators.

Fonte: Opinari #15 Posted: Comparing WCF and SCA