-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
"Daniel F. Savarese" <[EMAIL PROTECTED]> writes:
<snip/>
> The problem with the JCP is not merely the licensing. It is also the basic
> JSR procedures. The objective of a new API is to meet some set of developer
> requirements in a particular application domain. If you don't consult with
> your users, the target developer group, you probably won't develop a useful
> result.
<snip/>
Preach on brother!
The other issue is the way packaging is done! They really need to drop this
"shove everything in the JDK mentality".
There is no reason JAXM needs to be within your JDK. Just choose a decent
license and ship a .jar.
There are tons of classloader issues with Tomcat 4.x and JDK 1.4 because JAXP is
within the JDK.
You have versioning issues - can't ship a new library because you can't ship a
new JDK for 18 months. Competition issues - can't use your JCP library within
another VM (GCJ), etc, etc, etc.
So... screw JAXM. I would much rather link to Axis directly and bypass their
API.
Things need to change, drastically and soon...
Kevin
- --
Kevin A. Burton ( [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] )
Location - San Francisco, CA, Cell - 415.595.9965
Jabber - [EMAIL PROTECTED], Web - http://relativity.yi.org/
Linux. The *only* Operating System you will ever need.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt
iD8DBQE8msTRAwM6xb2dfE0RAkjRAJ9BJDOdrNug6GFIvS8umWccvGNo2QCgnLcR
satnVJFx5p6DqJjSlAdewo4=
=E349
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
