Davanum Srinivas' weblog

Main web site: http://ca.com/opensource/

Posted by dims at 02:03 AM | Permalink | Comments (0) | TrackBacks (0)

• CA Outlines Strategy To Help Customers Fully Leverage Open Source Technologies


• KGEM Information


• KGEM sf.net project


• CA's Ingres Database To Be Released Into Open Source


• CA and Zope To Bring Open Source Content Management To Mainstream Enterprise Market


• CA and JBoss To Create Advanced Open Source Solution For Java


• Plone Foundation Created to Strengthen Open Source Plone for Community and Business

Posted by dims at 01:54 AM | Permalink | Comments (0) | TrackBacks (0)

Guess what? Computer Associates is now part of the WS-Trust and WS-SecureConversation bandwagon. Grab the latest revisions to WS-Trust and WS-SecureConversation here.

Posted by dims at 01:16 AM | Permalink | Comments (0) | TrackBacks (0)

Wanna see how your favourite web services are performing? - http://wspi.ca.com/

Posted by dims at 01:08 AM | Permalink | Comments (0) | TrackBacks (0)

CA Exorcises Linux' Hooking Demons - http://www.linuxworld.com/story/44941_p.htm

Posted by dims at 02:51 PM | Permalink | Comments (0) | TrackBacks (0)

Excerpt from J2EE 1.4 Specification:

The primary focus of J2EE 1.4 is support for web services. The JAX-RPC and
SAAJ APIs provide the basic web services interoperability support. The Web
Services for J2EE specification describes the packaging and deployment
requirements for J2EE applications that provide and use web services. The EJB
specification was also extended to support implementing web services using
stateless session beans. The JAXR API supports access to registries and
repositories.

Here are list of specifications:

• J2EE.6.12 Web Services for J2EE 1.1 Requirements


• J2EE.6.13 Java™ API for XML-based RPC (JAX-RPC) 1.1
  Requirements


• J2EE.6.14 SOAP with Attachments API for Java™ (SAAJ) 1.2


• J2EE.6.15 Java™ API for XML Registries (JAXR) 1.0
  Requirements

Related projects at Apache Web Services and elsewhere:

• Apache Axis - Implements JAX-RPC and SAAJ


• Apache jUDDI - Working on JAXR


• Enterprise Web Services (at sf.net) - working on JSR 921

Choices for JBoss:

• Contribute significantly to Apache Axis


• Fork Apache Axis


• License RI's from SUN


• License Impl's from another vendor


• Implement everything from scratch

My VOTE would be for #1 ("Contribute significantly to Apache Axis"). But given the bad blood, your guess is as good as mine as to what they will do next. Even now, they claim to make "significant contributions" to Apache Axis and who knows what they will claim if they do contribute to Axis (Hint: See what they say about Apache Tomcat)

-- dims

Posted by dims at 01:44 PM | Permalink | Comments (0) | TrackBacks (8)