javax.naming work (Classpath vs ClasspathX)

[Nic Ferrier <nferrier at tf1 dot tapsellferrier dot co dot uk>]

David Brownell (of the ClasspathX project amongst other things) has
asked me to forward this to the list because it's not accepting
anything from him right now.


David Brownell wrote: 
 
> > FWIW I've never liked the fact that there are two separate projects, 
> > one for java.* and one for javax.*.  However, I'm resigned to it. 
> 
> Actually the distinction is not about java.* vs javax.*. The GNU Classpath 
> project was setup to give us a set of free standard java library classes. 
 
"Standard" has changed over time.  When Classpath was set up, there was no 
such thing as "javax.*" ... 
 
> So in principle all standards defined by what Sun calls J2SE (Java 2 Standard 
> Edition) will become part of Classpath (some day). Whatever package they are 
> in. 
 
Including moving projects betwen ClasspathX and Classpath when Sun 
changes its mind about how it thinks bundling should be done?  Seems 
to me the "java.*" vs "javax.*" distinction is a LOT more natural 
than trying to track Sun's marketing efforts.   Tracking Sun's marketing 
is pointless thrash, AFAICT. 
 
> The GNU Classpath Extensions <http://www.gnu.org/software/classpathx/> 
> project was setup to work on all extension classes that are not part of 
> the standard classes. They mainly work on things that are defined in what 
> Sun calls J2EE (Java 2 Enterprise Edition) which might or might not be 
> defined in the javax.* packages. (It includes things like the Servlet API, 
> Java Mail, Bean Activation framework, etc.) 
 
Well, the JAXP support (XML) is part of "extensions".  For all that Sun 
has recently moved it into JDK 1.4, it's still a "javax.*" class. 
 
And there's nothing in the Classpath Extensions project today that 
falls into the J2EE-only bag.  (Again, servlets existed for ages before 
Sun decided to market a J2EE bag ... and they run fine as an "extension" 
to J2SE, always have.) 
 
>        And the ClasspathX 
> people seem to agree that using the Classpath/libgcj GPL+linking-exception 
> license is OK. 
 
Certainly that's what the JAXP support is using. 
 
- Dave