Apache releases AXIS 1.3?

According to SpikeSource news AXIS 1.3 has been released but there is no evidence of this event any where on the Apache site. Currently the only way to get to the release page is to click on this link.

Presumably this is a release that many have been waiting for so avoid the rush and download early.

The anouncement is here: http://www.apachenews.org/

Where do I get the feature list that are included in AXIS 1.3
-Sourav

I was just posting the link to the announcement I had found. There clearly has been some sort of mess up at Apache. But as you ask, the points noted in the download are:


This release is intended to be 100% compliant with the JAX-RPC and SAAJ specifications from Sun. The Axis code has successfully passed the all of the JAX-RPC and SAAJ TCK (Technology Compatibility Kit) tests.


and

Changes from 1.2.1 final

Support Axis inside Applets
Upgrade versions of dependency jars
Updated xmlbeans serializer/deserializer
Fixes for SAAJ
Fixes for Code Generation
Fixes for tools
Fixes for Runtime
Fixes for Performance
Fixes for various attachments problems
Fixes for Memory Leaks
Cleanup support for JavaBeans with array-type properties
Extract attachment streams directly from http request (w/o intermediate files)
GC Fixes for long standing servers (Geronimo)
Preliminary support for MTOM

Thanks. I updated this:
http://www.apachenews.org/archives/000755.html

FWIW

Announcements - translated:

Chinese: http://news.csdn.net/news/newstopic/27/27538.shtml
Japanese: http://pcweb.mycom.co.jp/news/2005/10/12/013.html

I found the file "axis-1_3\docs\index.html" claims the documentation is for axis version 1.2 and not for 1.3.Any comments ?

Hello folks,
    Why do we need to go for Axis when we have entire JAXP package.
I believe that JAXP provide all the services that are required for Development of WebServices.

Please Provide your comments??


Yours
NavIndian.
Future is Open.

Hello folks,    Why do we need to go for Axis when we have entire JAXP package.I believe that JAXP provide all the services that are required for Development of WebServices.

Hey, if you are happy with JAXP, stick with it.

If, on the other hand, you want one of the the most broadly used SOAP toolkits in the java world, and the one that probably has the most tweaks to interop with the .NET platform (it supports DIME, SwA and MTOM attachments), and which comes with all the source, then you need Axis.

It is freely redistributable, and installs and runs in any popular app server, though those that include their own version can sometimes cause classpath grief if you don't pull the older one.

Its like why we go for log4J when we have logging utils by JDK itself ?

Its like why we go for log4J when we have logging utils by JDK itself ?

Why not? Using the classes provided with the JDK is NOT mandatory. It's just a matter of choice. IF the JDK was a step beyond every other product out there, THEN it would be an option. I personally found out JDK 1.4 had logging way after using Log4J. Shame on me? Perhaps...

Read about commons-logging, clogging and slf4j if you want to know more about what is being done with logging these days.

Hello folks,    Why do we need to go for Axis when we have entire JAXP package.I believe that JAXP provide all the services that are required for Development of WebServices.Please Provide your comments??YoursNavIndian.Future is Open.

I think you want to inquire about JAX-PRC or JAX-WS but not JAXP. JAXP is just the parser? Its not analogous to Axis.

Hello folks,    Why do we need to go for Axis when we have entire JAXP package.I believe that JAXP provide all the services that are required for Development of WebServices.Please Provide your comments??YoursNavIndian.Future is Open.

I think you want to inquire about JAX-PRC or JAX-WS but not JAXP. JAXP is just the parser? Its not analogous to Axis.

whoops, s/PRC/RPC

Hello folks,    Why do we need to go for Axis when we have entire JAXP package.I believe that JAXP provide all the services that are required for Development of WebServices.Please Provide your comments??YoursNavIndian.Future is Open.

Typically Sun puts out a reference implementation of a specification with the full intent that others will come out with implementations as well.

JAXB and JAIN SIP are examples of this (though the latter was implemented by NIST, as opposed to Sun employees).

I just downloaded it and all the docs refer to 1.2 - are there any plans to update the docs (or at least sync the version numbers) as I always get a bit edgy when I see things out of sync like that . . .

Yes, me too noticed and started a thread "https://www.theserverside.com/news/thread.tss?thread_id=37071#187740"