> > > Stefano Mazzocchi writes:
> > > > > Apache SOAP is destined to become the "old version" and Axis to be
> > > > > the new and on-going version.
> > > > >
> > > > I now understand this, but this is *NOT* clear from the outside.
> > > > We must fix this in some way.
> > > >
> > > Do you have any suggestions? We (Apache SOAP developers) have repeated
> > > this a hundred times on the soap-user list for example.
> > >
> > > Maybe what we should do is do one last release and then put flashing
> > > lights on xml.apache.org/soap saying this is it and that the next
> > > soap impl will be from axis.
> >
> > I love this! Yes, IMHO, no matter how many times you tell this to users,
> > this is not going to be evident from those lurkers (me included!) who
> > aren't subscribed to that list.
it would be wonderfully useful for newcomers to have some sort of
diagram or chart of all the xml.apache projects showing PROJECT
HISTORY/ANCESTORY/INHERITANCE, in case they have used one of the
previous incarnations.
eg.
IBM SOAP4J ---> Apache Soap 1.0 -------> Apache Axis 1.0
(?) \ |
\? |
\ v
> Wasp Lite ----> Apache Axis 2.0
or perhaps a tree list...
Apache Axis 2.0
+ Apache Axis 1.0
+ Apache Soap 1.0
+ IBM SOAP4J (?)
+ Wasp
+ Apache Soap 1.0 (?)
Some "used by" tables might also be useful to show how projects relate
to one another.
eg.
Xerces
+ Xalan (i'm guessing, its not obvious on the site, but it seems like
Xerces would need to parse XML to work)
Cocoon
+ Xalan
+ Xerces
+ Xalan
+ Batik
actually, i'd be happy to do it if i knew more about what the content
was - a useful reason to download batik and play with it.
---------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
