You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Brian Minchau (JIRA)" <xa...@xml.apache.org> on 2005/07/15 01:42:10 UTC
[jira] Created: (XALANJ-2172) JNDI code contribution, samples to use Derby
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
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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Updated: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "John Gentilin (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2172?page=all ]
John Gentilin updated XALANJ-2172:
----------------------------------
Attachment: XalanSQLDocs-Samples.patch
> 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
> Attachments: Xalan-SQL-JNDI-with-reflection.txt, Xalan-SQLSamples-ShowError.patch, XalanSQLDocs-Samples.patch, XalanSQLExamples.txt, derby-jars.zip
>
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "Yash Talwar (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2172?page=comments#action_12316938 ]
Yash Talwar commented on XALANJ-2172:
-------------------------------------
Hi John,
I have verified that samples build and runs fine on Windows.
I believe you need to address Sarah's comments about location of the files.
Patch looks good to me.
Yash Talwar
> 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
> Attachments: Xalan-SQL-JNDI-with-reflection.txt, XalanSQLExamples.txt, derby-jars.zip
>
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "John Gentilin (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2172?page=comments#action_12316830 ]
John Gentilin commented on XALANJ-2172:
---------------------------------------
Yash,
Attached is a patch to the sample directory to update the SQL example to use Derby.
To apply this patch, currently the Derby jars need to be placed in /java/bin. I will modify
the scripts to place the derby jars in either /test/bin or /test/tools, I am awaiting feedback
from Sarah.
To apply this patch, we would also need to remove the following
6-sqllib-instantdb.xsl file
instantDB directory
Please review the contents of the patch. I still need to update the documentation but I included
a simple Getting Started text file that will be able to get the average user up and running in a few
simple steps.
Agian for this patch to work, you also need to put the derby jars in /java/bin
I would like any feedback you have about the process.
Regards
John Gentilin
> 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
> Attachments: Xalan-SQL-JNDI-with-reflection.txt, XalanSQLExamples.txt, derby-jars.zip
>
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Updated: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "John Gentilin (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2172?page=all ]
John Gentilin updated XALANJ-2172:
----------------------------------
Attachment: Xalan-SQLSamples-ShowError.patch
> 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
> Attachments: Xalan-SQL-JNDI-with-reflection.txt, Xalan-SQLSamples-ShowError.patch, XalanSQLDocs-Samples.patch, XalanSQLExamples.txt, derby-jars.zip
>
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Updated: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "John Gentilin (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2172?page=all ]
John Gentilin updated XALANJ-2172:
----------------------------------
Attachment: XalanDocs-ExtensionLib-SQL.patch
> 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
> Attachments: Xalan-SQL-JNDI-with-reflection.txt, Xalan-SQLSamples-ShowError.patch, XalanDocs-ExtensionLib-SQL.patch, XalanSQLDocs-Samples.patch, XalanSQLExamples.txt, derby-jars.zip
>
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Updated: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "John Gentilin (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2172?page=all ]
John Gentilin updated XALANJ-2172:
----------------------------------
Attachment: derby-jars.zip
Rework samples to utilize the Derby embedded DBMS
> 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
> Attachments: Xalan-SQL-JNDI-with-reflection.txt, XalanSQLExamples.txt, derby-jars.zip
>
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2172?page=comments#action_12315878 ]
Brian Minchau commented on XALANJ-2172:
---------------------------------------
Are there going to be any additional testcases to test the JNDI functionality that is being added?
This would require J2EE environment to test.
If someone wants to use this code contribution, allows users in a J2EE environment,
to specify the JNDI name for the connection pool and invoke the JNDI methods to
connect to the pool.
To build this code as part of Xalan it should build just fine, but to use it you need a J2SE
environment. The new code, a new class, JNDIConnectionPool, which wrapers the
connection pool interface and maps it to the JNDI connection pool class.
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Updated: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2172?page=all ]
Brian Minchau updated XALANJ-2172:
----------------------------------
reviewer: ytalwar@ca.ibm.com
Assigning Yash to be the reviewer.
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Updated: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "John Gentilin (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2172?page=all ]
John Gentilin updated XALANJ-2172:
----------------------------------
Attachment: XalanSQLExamples.txt
The revised sample code, requires the derby jars to operate.
> 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
> Attachments: Xalan-SQL-JNDI-with-reflection.txt, XalanSQLExamples.txt, derby-jars.zip
>
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Resolved: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "Sarah McNamara (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2172?page=all ]
Sarah McNamara resolved XALANJ-2172:
------------------------------------
Fix Version: CurrentCVS
Resolution: Fixed
All patches have been applied to cvs. This enhancement will be available in the Xalan Java 2.7 release.
> 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
> Fix For: CurrentCVS
> Attachments: Xalan-SQL-JNDI-with-reflection.txt, Xalan-SQLSamples-ShowError.patch, XalanDocs-ExtensionLib-SQL.patch, XalanSQLDocs-Samples.patch, XalanSQLExamples.txt, derby-jars.zip
>
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "Yash Talwar (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2172?page=comments#action_12316778 ]
Yash Talwar commented on XALANJ-2172:
-------------------------------------
I have looked at this patch and verified that xalan build is successful without any additional dependencies. I have not used this change at runtime as I don't have the samples to test it. However, the patch is good for Xalan build.
Yash Talwar
> 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
> Attachments: Xalan-SQL-JNDI-with-reflection.txt
>
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "Sarah McNamara (JIRA)" <xa...@xml.apache.org>.
[ 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "Sarah McNamara (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2172?page=comments#action_12316840 ]
Sarah McNamara commented on XALANJ-2172:
----------------------------------------
John, thanks for the clarifications in your previous append. I'm glad that you were able to use reflection to avoid the
need for the jdbc-std-ext.jar.
I had a quick peek at your new patches. Just to let you know, the xml-xalan/java/bin directory is gone. As part of
the doc changes in XALANJ-2170, I fixed XALANJ-1556 and put this comment in XALANJ-2170:
"....The biggest change in this patch is a proposed restructuring of the xalan java cvs
so that licenses and notices are under a licenses directory, tools (such as stylebook,
ant, jlex, java_cup, etc) are under a tools directory, and runtime jar dependencies are
under a lib directory. The bin directory will be removed. "
[Please extract the latest code from xml-xalan/java to see the updates].
So, the runDerby.bat/.sh and runXalan.bat/.sh files in your patch need to be slightly reworked to reflect the new
location of _PARSER_JAR and _XML-APIS_JAR (now located in xml-xalan/java/lib) and _JAR_DIR (which I
think you'll also want to have point to xml-xalan/java/lib).
As to the location of where to put the derby.jar and derbytools.jar, you can put them in either xml-xalan/java/tools
or xml-xalan/test/tools directory. Just so you're aware, the xml-xalan/java/tools directory is not included in the binary
distribution (ie. xalan-j_2_7_0-bin.tar.gz/.zip); it is only included in the source distribution package
(ie. xalanj-2.7.0-src.tar.gz/.zip) since the theory is that the jars in the tools directory are not required at
runtime ... they are only required to 'build' the project and its documentation. So, regardless of where you put the
derby jars, I think the samples page in the documentation needs to mention that the user needs to download the
jars from the Derby project. This model of not distributing 3rd party dependent jars is consistent with the
approach we now use for people who want to use non-java extensions (ie. they need to obtain bsf.jar from the
jakarta bsf project). For what its worth, my preference would be to put the derby jars in xml-xalan/test/tools
as we require these jars to run/test the sql samples.
I also noticed a typo in GETTING_STARTED.txt. On the line
+runXalan.bar -XSL basic-connection/dbtest.xsl
I believe you meant to have it read
+runXalan.bat -XSL basic-connection/dbtest.xsl
> 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
> Attachments: Xalan-SQL-JNDI-with-reflection.txt, XalanSQLExamples.txt, derby-jars.zip
>
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Assigned: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2172?page=all ]
Brian Minchau reassigned XALANJ-2172:
-------------------------------------
Assign To: John Gentilin
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Updated: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "John Gentilin (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2172?page=all ]
John Gentilin updated XALANJ-2172:
----------------------------------
Attachment: Xalan-SQL-JNDI-with-reflection.txt
> 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
> Attachments: Xalan-SQL-JNDI-with-reflection.txt
>
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "John Gentilin (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2172?page=comments#action_12316692 ]
John Gentilin commented on XALANJ-2172:
---------------------------------------
Sarah,
I emailed a prerelease of the patch to Yash on 7/24, I have also attached the same patch here.
The fix really only effects the Xalan.jar file. The discussion we were having last week is that it did require the jdbc-std-ext.jar so that xalan.jar could compile with JDK 1.3. This jar file was a step release during the JDK 1.3 era which became standardized for JDK 1.4.
The class file that was causing a problem was DataSource I realized that we may have a problem of getting a quorum before the next release so I modified the patch to use reflection. Now Xalan.jar will compile with an off the shelf JDK 1.3. I have also sent a version to Eric Everman to validate that it works under a JNDI platform since I do not have a proper test setup. I did however compile the Jar under JDK1.3 and ran all the existing tests. Currently I am waiting feedback from both Eric and Yash.
Now as a secondary effect to working on the SQL Extensions, and talking with some of the other Apache contributors at JavaOne. I decided to rework the SQL sample code so it would use Derby both as an effort to promote other Apache products and so that the SQL extensions could be demonstrated without the need to perform complex setups. The existing samples use a combination of MySql and InstantDB, both of which require licensing to redistribute and lack instructions on how to configure the DBMS. This work is almost complete. I have created batch files that create the sample DB under Derby and run the Xalan.jar to make it easier to demonstrate the SQL extensions. What I need to do now is create the equivalent Unix .sh files, which I plan to complete tonight.
> 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
> Attachments: Xalan-SQL-JNDI-with-reflection.txt
>
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2172) JNDI code contribution, samples to use Derby
Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2172?page=comments#action_12315874 ]
Brian Minchau commented on XALANJ-2172:
---------------------------------------
Derby is in the incubator, is that a problem for us?
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org