[ http://issues.apache.org/jira/browse/XALANJ-2172?page=comments#action_12316687 ]
Sarah McNamara commented on XALANJ-2172: ---------------------------------------- Hi John, can you please update this JIRA issue with the patch and the additional dependencies that you're proposing as I'm unclear whether this change impacts xalan.jar or just the samples. I believe there's been discussion that we can't move up to 1.4 as our build compiler and leave behind 1.3, so we need to make this enhancement work in a 1.3 environment. You mentioned that an additional jar, jdbc-std-ext.jar, was required in jre/lib/ext or on the classpath. Due to license issues, I don't think we can check in jdbc-std-ext.jar to cvs, therefore, there would be an external requirement for folks to have to obtain this jar before doing a build. This might cause problems for some people. > JNDI code contribution, samples to use Derby > -------------------------------------------- > > Key: XALANJ-2172 > URL: http://issues.apache.org/jira/browse/XALANJ-2172 > Project: XalanJ2 > Type: Improvement > Reporter: Brian Minchau > Assignee: John Gentilin > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
