WS-SecureConversation / Trust

[Lee Coomber <le...@lshift.net>]

Hi,

Our client has a need for Java WS-SecureConversation and WS-Trust 
implementations to allow interop with .Net clients. We are examining
WSS4J as a potential base to do this from and it would be helpful if we
could have feedback to get approval to move forward.

1) Is anyone out there already working on this and if so, how close is
it to completion (for info, our deadline is about 2 months away)? Are
there chunks of work remaining that you would be willing to hand off to
other people?

2) Is there a roadmap on implementation of these and other WS-*
specifications?

3) Any architectural ideas for these implementations?

4) Any estimates on the work involved? We have guestimated at about 50
man days but would be very interested in some thoughts from anyone who
knows the code thoroughly :-)

5) (for maintainers and other implementors in particular) We have been
working hard to persuade our client (a multinational company) that it is
in their interests to contribute back any implementation we write mainly
on the basis that:-

- it would be impractical to maintain what would effectively be a
branch of the main WSS4J source tree

- the code would be used and maintained by other people increasing the
chances of bugs and reducing the overhead in fixing them

We are winning the argument on a project level but before it goes for
senior approval we need to address their concern that we implement these
specifications and they are not accepted into WSS4J. What is the best
way for us to go about doing this work and ensure that this does not
happen (as far as is possible in an OS project)?

Many thanks for your time and doubly so for any answers,

Lee

-- 

  [][][] Lee Coomber    | Tel: +44 (0)20 7729 7060
    [][] LShift Ltd     | Email: lee@lshift.net
  []  [] www.lshift.net |

Re: WS-SecureConversation / Trust

[Davanum Srinivas <da...@gmail.com>]

Lee,

Yes, it can be done in 2 months :) Check the archives for previous
discussion on these 2 specs, there are a few folks on this list who
are looking into it right now. I can assure you that your contribution
will be more than welcome, and appreciated a lot. There are just a few
simple guidelines (don't break the tests, be careful about backwards
compatibility etc, post the patch to our bug tracker, try and submit a
test case with your patch etc) which are the same in any open source
effort. The archives are at -
http://news.gmane.org/gmane.comp.apache.webservices.fx.devel

thanks,
dims

On Tue, 15 Jun 2004 18:27:27 +0100, Lee Coomber <le...@lshift.net> wrote:
> 
> Hi,
> 
> Our client has a need for Java WS-SecureConversation and WS-Trust
> implementations to allow interop with .Net clients. We are examining
> WSS4J as a potential base to do this from and it would be helpful if we
> could have feedback to get approval to move forward.
> 
> 1) Is anyone out there already working on this and if so, how close is
> it to completion (for info, our deadline is about 2 months away)? Are
> there chunks of work remaining that you would be willing to hand off to
> other people?
> 
> 2) Is there a roadmap on implementation of these and other WS-*
> specifications?
> 
> 3) Any architectural ideas for these implementations?
> 
> 4) Any estimates on the work involved? We have guestimated at about 50
> man days but would be very interested in some thoughts from anyone who
> knows the code thoroughly :-)
> 
> 5) (for maintainers and other implementors in particular) We have been
> working hard to persuade our client (a multinational company) that it is
> in their interests to contribute back any implementation we write mainly
> on the basis that:-
> 
> - it would be impractical to maintain what would effectively be a
> branch of the main WSS4J source tree
> 
> - the code would be used and maintained by other people increasing the
> chances of bugs and reducing the overhead in fixing them
> 
> We are winning the argument on a project level but before it goes for
> senior approval we need to address their concern that we implement these
> specifications and they are not accepted into WSS4J. What is the best
> way for us to go about doing this work and ensure that this does not
> happen (as far as is possible in an OS project)?
> 
> Many thanks for your time and doubly so for any answers,
> 
> Lee
> 
> --
> 
>   [][][] Lee Coomber    | Tel: +44 (0)20 7729 7060
>     [][] LShift Ltd     | Email: lee@lshift.net
>   []  [] www.lshift.net |
> 
> 


-- 
Davanum Srinivas - http://webservices.apache.org/~dims/