ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ias" <>
Subject RE: WS Commons again
Date Tue, 20 Jan 2004 09:33:09 GMT
> I am not a big fan a lots of little jar files.
So am I. we already have lots of jars in various projects.
> What is the driving motivation for this?  Does it solve a 
> problem users are having?

Apparently, the motivation is from Sun's JWSDP (1.3). When I first saw
their (too) fine-grained jar files, I couldn't understand what they meant.
As I worked with Sun's JAXB, I gradually got to know why they were so
I'm not sure whether it's a significant problem or not, but guess that
Sun's jax-qname.jar containing only one class, QName is invented for
avoiding duplication. For example, if you use Axis, jUDDI and even JaxMe
toghether, you have three QName classes in your classpath. It may be OK,
however, is not a recommended situation.

I'd like to tell you all that we are now in a transition period of XML and
Web Services development. If we have JAXB 2.0 and JAX-RPC 2.0 requiring
JAXP 1.3, all these problems will disappear. Until that time (I guess
around one year later), I think we should make a good compromise for not
only ourselves but also users of Apache WS. There's a way to remove the
conflict and not to cope with Sun's jars even though we have the same ones,
I believe.

> --
> Tom Jordahl
> -----Original Message-----
> From: Ias []
> Sent: Saturday, January 17, 2004 9:55 AM
> To:
> Cc: '? ??'
> Subject: WS Commons again
> As I added myself to
> tPages/Charter
> ForWSCommons , Here's what I'd like to propose.
> 1. Sharing javax.xml.namespace.QName
> The class is used in most of projects such as Axis, JaxMe and jUDDI.
> I suggest making it shared by the projects as a form of a 
> single jar library, for example, qname.jar.
> 2. Sharing javax.xml.namespace.XMLConstants and 
> javax.xml.namespace.NamespaceContext
> Those classes are used in JaxMe and EWS, hosted at 
> , and will be widely 
> adopted because it defines constants which are frequently referenced.
> I suggest making it shared by the projects as a form of a 
> single jar library, for example, namespace.jar
> In near future, all these classes are provided by JAXP 1.3 
> API, but our necessity is prompt and rather narrower than 
> that of JAXP 1.3. Actually I once made this proposal to both 
> XML and WS group in Apache, but there has been neither 
> noticeable agreements nor corresponding moves from XML 
> commons, so I think WS commons is "The One" for the wish now.
> Thanks for your attention and looking forward to your response,
> Ias
> =========================================================
> Lee, Changshin (Korean name)
> Ias (International name)
>                Company Web Site:
>                Personal Web Site:
> ---------------------------------------------------------
> JSR 201, JSR 204 and JSR 222 EG member
> Apache Axis (JAX-RPC and SAAJ) and JaxMe (JAXB) committer R&D 
> Institute Tmax Soft, Inc.
> =========================================================

View raw message