Is it too easy to write your own soap stack?
I don't know. I was reading this Survey from XMLBeans folks. Reading about SAAJ there triggered other memories, sent an email to Steve asking him about Alpine. Thinking about Alpine reminded me of Steve's post on Jboss's initiative to replace Axis. That triggered me to do a google search on how others are faring, Here's the user mailing lists of a few other stacks (check the activity).
- ActiveSOAP
- XFire
- JWSDP
- Systinet
Then i started thinking about Axis2, on how to provide an upgrade path to the existing Axis 1.X users.
One thing keeps popping up. Is it too easy to write a soap stack? The more we do this, it seems more difficult to get it right without repeating the same mistakes we've done before. Before Axis2 there was Axis1 and before that there was Apache SOAP. Is everyone writing their own soap stacks know what they really signed up for? Or is WS-* too complicated for its own good? May be it's time to sleep...zzzzz
Comments
I would say that critical part is how well SOAP stacks implement their target use cases *and* how well they tested and can interoperate - and the last thing is the most important - after all isnt it promise of WS to not care in what language, what OS, or in general how things are internally implemented?
From mainframe to mobile phone: (X)HTML, HTTP, WS?
Posted by: Aleksander Slominski | July 7, 2005 05:46 AM
Why that should be a problem?
I would say that critical part is how well SOAP stacks implement their target use cases *and* how well they tested and can interoperate - and the last thing is the most important - after all isnt it promise of WS to not care in what language, what OS, or in general how things are internally implemented?
From mainframe to mobile phone: (X)HTML, HTTP, WS?
Posted by: Aleksander Slominski | July 7, 2005 05:54 AM