In his blog Patt Helland talks about Why I hate the phrase “Long Running Transactions”.
I think this is a good example why we have to reconsider a lot of software engineering concepts when we want to develop Service Oriented Applications. SOA has more implications than we might see today.
A friend of mine Antoine Doubacis who works at the olympic games in Athens took this picture in the olympic village.
It somehow reminds me to SOA. Looks complicated but has well defined interfaces. Quite impressive.
BEA Weblogic Platform now supports the OASIS Web Services Security Specification.
Quote:
Implementation of the Final 1.0 OASIS Web Services Security Specification
WebLogic Web Services now implement the following OASIS Standard 1.0 Web Services Security specifications, dated April 6, 2004:
Web Services Security: SOAP Message Security
Web Services Security: Username Token Profile
Web Services Security: X.509 Token Profile
Although it’s great that Web Service Security ist standarized within a platform, the interesting question is whether it’s possible to connect distinct platforms in a secure manner.
Currently I’m setting up a new study in order to show whether WS-Security is mature enough to connect for instance BEA Weblogic Server 8.1 SP3 and Microsoft WSE2.0. If you would like to get involved in the study please let me know. I’ll keep you informed.
On 6.April 2004 the WS-Security specification was ratified by OASIS
Currently this specification is supported only by Microsoft WSE2.0.
Sun announced WS-Security support in JWSDP 1.4 and BEA in Weblogic Server 8.1 SP3.
I’m curious how this products will affect the adoption of Web Service technology.
On April 6th 2004 OASIS ratified the WS-Security specifications. This is an important step for the adoption of Web Service technology as it is one of the building blocks of Service Oriented Architectures (SOA).
It seems that Gartner shares this opinion: Gartner Advise Enterprises to Adopt Web Services Security (WS-Security).
I think in the near future all leading application servers / frameworks will support these specifications and thus make it possible to write secure and interoperable Web Services.
That’s great.
In it’s current issue the DOTNETPRO magazine published my recent article about developing interoperable Web Services with J2EE and .NET.
It’s worth a look. What else should I say?
The following document gives a good overview about the different encoding styles, and it’s strenghts and weaknesses:
http://www-106.ibm.com/developerworks/webservices/library/ws-whichwsdl/
Wouldn’t it be nice to have an editor other than notepad.exe to write WSDL files from scratch ?
Have a look at:
http://www.capescience.com/downloads/wsdleditor/
It’s free !
When you read different forums there is a lot of talk about serialisation of plattform dependent types.
Pepole are asking how to get a .NET Type (e.g. DataSet) from Java or vice versa (e.g. Resultset).
If you are developing end to end .NET or J2EE applications you don’t have to worry about that. The runtime does most of the work for you and if you ask for a DataSet you will get one.
But when it comes to cross plattform what will you get when you ask for a DataSet from an J2EE application ?
To answer this Question we have ask another one.
What makes up an object ? Answer: It’s state and behaviour.
When you request a DataSet you will only get the state and type information. But what makes a DataSet so powerful ? It’s the behaviour.
If you don’t have the concept of a DataSet on the J2EE platform you can get only the half of the object representation. It’s a cripple object.
The same it true when you request a Java Resultset from .NET.
In order to develop interoperable Web Services you have to rely on XML Schema types only. First define the schema and wsdl contract and then generate the service from it.
It’s the same as you might know from CORBA or COM Interface Definition Language (IDL).
Tool support is available:
.NET -> wsdl.exe /server …
JWSDP -> wscompile -gen:server …
This article on MSDN gives a good overview over the most important upcoming Web Service standards. It’s worth a look.