Académique Documents
Professionnel Documents
Culture Documents
Topics
What is WSIT? WSIT features
> > > > >
End-to-end reliability Secure communication Atomic transaction Optimized communication Bootstrapping communication
Summary
What is WSIT?
What is WSIT?
Web Services Interoperability Technologies
(WSIT)
Goal > Interoperability with Microsoft Windows Communication Foundation (WCF, a.k.a. Indigo) > Implementation of WS-* specifications
End-to-End Reliability
RMD are responsible for message exchange on behalf of Source and Dest.
Rebuild the Hello World Web service using Reliable Messaging (Demo Scenario Next Slide)
http://www.javapassion.com/handsonlabs/wswsit/#Exercise_1
Demo:
Demo Scenario
Configure the Hello World Web service with
> No code change
Test the Web service > Should work the same Display the newly generated WSDL document > It should contain Reliable messaging policy elements Rebuild the client application > Refresh the client to get new WSDL Show the message exchanges using WS-Monitor > There are two message exchanges
8
Secure Communication
WS-SecurityPolicy
WS-SecurityPolicy defines assertions that can
be used to describe the security capabilities and requirement of the WebService. The capabilities and requirements can be published as part of the WSDL.
> A security requirement specified in the WSDL of a
service forces a communicating party trying to access the service in a certain way.
WS-SecurityPolicy
Examples of security requirement specified
through WS-SecurityPolicy
Username/Password in order to authenticate to the service etc. > The type of Key and Key Sizes and Algorithms that need to be used etc.
11
Rebuild the Hello World Web service using Security (Demo Scenario Next Slide)
http://www.javapassion.com/handsonlabs/wswsit/#Exercise_2
Demo:
12
Demo Scenario
Configure the Hello World Web service with
Display the newly generated WSDL document > It should contain security policy elements Rebuild the client application > Refresh the client to get new WSDL Show the message exchanges using WS-
13
14
or are all rolled back Same as in Enterprise JavaBeans (EJB) architecture/Java RMI-IIOP Technology New to web services
> The transaction context is carried over SOAP
(instead of RMI-IIOP)
15
Annotations
16
[1] stateless EJB default, annotation added to be explicit [2] Implementation restriction: transaction not propagated with a one way message
17
18
time a transacted Web service operation is invoked within a JTA transaction scope - line 05 below > 01 @Resource > 02 javax.transaction.UserTransaction ut; > 03 > 04 ut.begin(); > 05 bankWebService.makeWithdrawl(); > 06 ... > 07 ut.commit();.
19
Demo:
20
Demo Scenario
Create EJB based Web service > One of the operation is annotated with
@javax.ejb.TransactionAttribute
based Web service is invoked as as part of a business process Create a composite application which contains the above BPEL module Create a Web client application which starts the business process Show the message exchanges using WSMonitor or GlassFish log
21
Thank You!