Wednesday Feb 28, 2007

WSIT at Sun Tech Days 2007 Hyderabad

Kumar and myself had  the opportunity to present on WSIT at Sun Tech Days 2007 Hyderabad. The title of the presentation was "JAX-WS and WSIT : Tangoing with .NET". The talk was well attended and we had to face some interesting questions :). Developers were excited about WSIT and .Net interoperability. The goal of the presentation was to introduce developers to JAXWS , Netbeans and various components of WSIT(Transactions, Optimization, Security,Reliable Messaging , WSIT programming model). Kumar did a demo on JAXWS and RM using Netbeans, this demonstrated how simple it was to write a Web service application and enable WSIT components. 

For those who are still wondering on what WSIT is all about and how it will benefit you or if you have more specific questions or issues, I recommend you to visit us at http://wsit.dev.java.net or post questions on WSIT forum or email us at users@wsit.dev.java.net / dev@wsit.dev.java.net .

WSIT is part of Glassfish v2 builds and can also be downloaded from WSIT .






powered by performancing firefox

Improved XWSS implementation in WSIT Milestone 3

In order to take advantage of new Message design provided in JAXWS 2.1 we revamped XWSS in WSIT milestone 3. XWSS 3.0 now has two implementations of WS Security one is based on DOM/SAAJ api's and other is based on JAXB and StAX api's . We have by default enabled JAXB and StAX based implementation. The performance benefits we get from the default implementation is really exciting. The burden of DOM and SAAJ is no longer needed to support most commonly used security scenarios. I will soon publish the performance improvement we have got over XWSS 2.0. Though the default implementation is efficient it has some limitations in this release of WSIT. We do not support XPATH , i,e we do not support SignedElements and EncryptedElements. We do support this under DOM based implementation.

Ability to switch between these two implementation automatically based on the SecurityPolicy will be supported in future releases of WSIT. In this release we can switch to DOM based WS Security implementation by adding DisableStreamingSecurity policy assertion in wsit-client.xml on client side and wsit.xml/ wsdl on the server side.


Client side assertion :

<sunsp:DisableStreamingSecurity xmlns:sunsp="http://schemas.sun.com/2006/03/wss/client"></sunsp:DisableStreamingSecurity>


Server side assertion :

<sunsp:DisableStreamingSecurity xmlns:sunsp="http://schemas.sun.com/2006/03/wss/server"></sunsp:DisableStreamingSecurity>



powered by performancing firefox

About

venu

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today