See intermixed. On Mon, 28 Jan 2002, GOMEZ Henri wrote:
> Date: Mon, 28 Jan 2002 16:00:14 +0100 > From: GOMEZ Henri <[EMAIL PROTECTED]> > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]> > To: Tomcat Developers List <[EMAIL PROTECTED]> > Subject: RE: Tools for Building Web Services > > >If your interest in Tomcat is for developing Web Services, you will be > >interested in the Java Web Services Developer Pack (version > >1.0ea1) that > >was just released by Sun: > > > > http://java.sun.com/webservices > > > >The Java WSDP includes early releases of base XML technology: JAXP 1.2 > >(with schema support), SOAP-based RPC (JAX-RPC), SOAP-based messaging > >(JAXM), and registry client support (JAXR). Although this is an EA1 > >release of the product we are targeting for this summer, we > >also include a > >tutorial as well as a number of development features to help you get up > >and running quickly, including building tools (Apache's Ant), > >a UDDI based > >registry server for testing, some management tools (more in later EAs). > >We also include a version of Apache Tomcat so develoeprs can > >start using > >the JWSDP right away. All of these technologies depend on > >J2EE 1.3 APIs. > > These technologies couldn't be used under Linux if you have IBM SDK 1.3. > The Sun JDK 1.3.1 is mandatory. Why couldn't we use the IBM SDK ? > > Also how many of the technologies reviewed are OpenSource ? > > * JavaTM XML Pack Release which includes the following: > > *JavaTM API for XML Messaging ("JAXM") 1.0 EA 1 > > => Apache xml-common ? > No. It's the reference implementation for JSR-67: http://www.jcp.org/jsr/detail/67.jsp > * JavaTM API for XML Processing ("JAXP") 1.2 EA 1 (with XML Schema > support) > > => Apache Crimson/Xerces > It's based on Xerces2 and Xalan2 (and therefore uses xml-common). > * JavaTM API for XML Registries ("JAXR") 1.0 EA 1 > > => is there OSS alternatives ? > I don't know. This is the RI for http://www.jcp.org/jsr/detail/93.jsp > * JavaTM API for XML-based RPC ("JAX-RPC") 1.0 EA 1 > > => xml-axis ? > Axis is in the same general area of endeavor, and my understanding is that they are working towards compliance with the same spec: http://www.jcp.org/jsr/detail/101.jsp > * JavaServer PagesTM Standard Tag Library ("JSTL") 1.0 EA 3 > > => ??? > The RI for this is actually being created at Apache, in the Taglibs project. http://www.jcp.org/jsr/detail/52.jsp > Ant Build Tool 1.4.1 > > = Ok, it's jakarta > Yep. Nearly all the internal components are built with Ant as well (so backwards compatibility of Ant scripts is important to me :-). > Java WSDP Registry Server 1.0 EA 1 > > => ??? > Implements a UDDI-based registry server. JAXR is the client API to talk to it, but can also talk to any other UDDI registry. > Tomcat JavaTM Servlet & JavaServer PagesTM container 4.1-dev > > => jakarta-tomcat-4 > Yep, from the HEAD branch. > > Thanks to correct me if I made mistake and clarify if Sun plan > to give back some APIs to Apache as they do for crimson and servlets ? > At the present time, the RIs for JAXM, JAXR, JAXRPC, and the registry server are not open source. Craig -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
