Re: [MO-java-dev] confused about naming/sql classes

[Jeff M. <je...@mk...>]

That's a good point. This all stems from javax.naming and javax.sql used
to be optional to the jdk and so sat better in j2ee. However as of
jdk1.3 javax.naming became part of the jdk and as of jdk1.4 to has
javax.sql

We should probably move these across, although which classes go in which
jars is going to depend on the jdk that being build against, which is
going to confuse the shit outta me.


On Tue, 2004-05-18 at 02:59, J. Joseph Benavidez wrote:
> Hello,
> 
> I'm trying to figure out the mockobject packages and how they're
> distributed amongst the jar files.
> 
> My confusion stems from the fact that the naming.* (and some sql.*)
> classes are in the j2ee jars, but javax.naming.* and javax.sql.* are in
> the standard jdks.
> 
> Would it be possible to put those classes in their respective plain
> jdk1.3/jdk1.4 jars and pull them out of the j2ee jars?
> 
> Thanks,
> 
> j.joseph
> 
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> Mockobjects-java-dev mailing list
> Moc...@li...
> https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev
-- 
Jeff Martin
 
Memetic Engineer
 
http://www.custommonkey.org/