WS Commons again

[Ias <ia...@tmax.co.kr>]

As I added myself to
http://nagoya.apache.org/wiki/apachewiki.cgi?WebServicesProjectPages/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
http://sourceforge.net/projects/ews , 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: http://www.tmax.co.kr
               Personal Web Site: http://www.iasandcb.pe.kr
---------------------------------------------------------
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.
=========================================================

RE: WS Commons again

[Ias <ia...@tmax.co.kr>]

> > > library, for example, qname.jar.
> > 
> > [...]
> > 
> > > library, for example, namespace.jar
> > 
> > What is the sense of two different jar files for three 
> classes or so?
> The concept of those libraries comes from Sun's JWSDP 1.3, in 
> particular, jwsdp-shared/lib. In a certain point of view it 
> seems to be too much for a jar to have one or two classes, 
> nevertheles, the rationale for making those jars is 
> componentizing in order to share codes and avoid duplicates.
> 
In addition, I guess that the reason why not having the 3 classes in one jar
is that in some cases you don't need all of them at the same time. For
example, QName is needed by most Apache WS projects, but the others are
needed by JaxMe and EWS.

RE: WS Commons again

[Ias <ia...@tmax.co.kr>]

> Subject: Re: WS Commons again
> 
> Ias wrote:
> 
> > library, for example, qname.jar.
> 
> [...]
> 
> > library, for example, namespace.jar
> 
> What is the sense of two different jar files for three classes or so?
The concept of those libraries comes from Sun's JWSDP 1.3, in particular,
jwsdp-shared/lib. In a certain point of view it seems to be too much for a
jar to have one or two classes, nevertheles, the rationale for making those
jars is componentizing in order to share codes and avoid duplicates.

Ias

Re: WS Commons again

[Jochen Wiedmann <jo...@ispsoft.de>]

Ias wrote:

> library, for example, qname.jar.

[...]

> library, for example, namespace.jar

What is the sense of two different jar files for three classes or so?


Jochen