[XALANJ-2172] JNDI code contribution, samples to use Derby

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.7
• Fix priority: fp2
• Assignee: John Gentilin
• Reporter: Brian Minchau
• Reviewer: Yash Talwar
• Created: 15/Jul/05 08:33
• Updated: 09/Aug/05 09:15
• Resolved: 05/Aug/05 08:13

Description

I'm opening this issue to track the status of John Gentilin's contribution of Eric's code for new JNDI work.

John has also reworked some samples to use Derby (hope I'm expressing this correctly).

The new code will more easily create a database and run code/tests.
The amount of setup needed to get involved in this code was rather
high, one needs to install a database management system, plus get
the JDBC libraries, etc. Derby has an embeded version where all
you need to do use a jar file.

John G. has reviewed Eric's JNDI code,
and integrated/tested on his
system. Eric will test in a JNDI environment.

One new class, the rest is patches to existing parts.

Instant DB is no longer used, MySQL is not used and John G. has reworked
the examples to use Derby ( http://incubator.apache.org/projects/derby.html )

Rather than include the Derby jars in the distribution, or in the
./lib directory or the ./examples directory, we should propably point
users to where they can get the jars. For example we no longer ship
the Jakarta bsf.jar with our distribution.

If the jars go in ./test/java/bin that is OK, it is not part of
the distribution, and the smoketest could use them.

The old ./instantdb that can go.

John will be providing documentation changes as well.
Yash has agreed to review.

There are still open issues on this one regarding dependencies.
Please record discussion/patches/reviews in this issue.