[ 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to