Hi Eric,
I'm sure that you're talking about Xalan 2.7.0, there is no 2.7.1 yet.

Sounds like you are not running the class files that you think you are,
probably a class loading issue.

Put a:
   throw new RuntimException("Eric E");
in your code. In a place that you are sure is getting executed. Then build
with ant.

I'm willing to bet that when you run your transformation in the IDE,  the
exception is never thrown, i.e. you built a xalan.jar, but that is not the
xalan.jar being used in your IDE.

If you IDE is Eclipse, I can probably give assistance.

- Brian
- - - - - - - - - - - - - - - - - - - -
Brian Minchau
[EMAIL PROTECTED]



                                                                           
             Eric Everman                                                  
             <[EMAIL PROTECTED]                                             
             esign.com>                                                 To 
                                       xalan-j-users@xml.apache.org        
             11/16/2005 10:42                                           cc 
             AM                                                            
                                                                   Subject 
                                       Incorrect Java Source Line Numbers  
                                       in Xalan Classes (Xalan 2.7.1)      
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




Hi-

The Xalan 2.7.1 classes seem to report wildly incorrect java source
line numbers when running in debug mode via an IDE.  (Note: I'm not
talking about XSLT line numbers).

I've tried tracing the xalan.jar using the source provided from the
source distribution, and I've also trying building the xalan.jar from
the build.sh script and just using ant directly.  All class files
report incorrect tracing line numbers - Here is an example:

----------------------------------------------------------------
In my IDE, I see execution stopped at this breakpoint:
Class breakpoint occurred at line 143 of DefaultConnectionPool.java,
in method: void
org.apache.xalan.lib.sql.DefaultConnectionPool.setDriver
(java.lang.String)

Looking at the source code, line 143 is near the end of a method
named freeUnused(), approximately 40 lines down from the setDriver()
method.
----------------------------------------------------------------

What am I doing wrong??  I'm not an ant expert - is ant modifying the
source code before compile?

Platform:
Oracle's JDeveloper on Mac OS X 10.4.3, which is running on JDK 1.5.
All compiling and class compatibility is JDK 1.4.2, including ant and
build.sh builds.


Any help is appreciated - I'm pulling my hair out on this one.

Eric Everman


Reply via email to