http://nagoya.apache.org/bugzilla/show_bug.cgi?id=542

*** shadow/542  Wed Feb  7 08:30:51 2001
--- shadow/542.tmp.694  Wed Feb  7 08:30:51 2001
***************
*** 0 ****
--- 1,34 ----
+ +============================================================================+
+ | Properties.load(InputStream) fails for EJB client run by Ant 1.2           |
+ +----------------------------------------------------------------------------+
+ |        Bug #: 542                         Product: Ant                     |
+ |       Status: NEW                         Version: 1.2                     |
+ |   Resolution:                            Platform: PC                      |
+ |     Severity: Major                    OS/Version: Windows NT/2K           |
+ |     Priority:                           Component: Core tasks              |
+ +----------------------------------------------------------------------------+
+ |  Assigned To: [EMAIL PROTECTED]                                   |
+ |  Reported By: [EMAIL PROTECTED]                                       |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ Ant seems to be having a problem handling classpaths for EJB clients. When I 
+ run the client from Ant, I get a NullPointerException from Properties.load
+ (InputStream); the InputStream is null because the ClassLoader can't find the 
+ properties file in the EJB client jar (generated by the EJB container, 
+ GemStone/J) even though it's looking for the right file name with the right 
+ path. I know the client jar is in the classpath; when I take it out, the 
client 
+ fails with a ClassDefNotFoundException long before trying to load the 
+ properties. When I run the same clients using a .bat file (Windows NT batch 
+ file), the clients work, find the properties file, and connect to the server 
+ properly. So Ant seems to be causing the failure.
+ 
+ A coworker who has used Ant more than me has reproduced the problem on his 
+ machine, can't find what's wrong, and says it seems to be an Ant bug. He has 
+ done this sort of thing with Ant 1.1 and it worked, so this seems to be a new 
+ bug.
+ 
+ If you want my build.xml file or the exception stack trace, contact me at 
+ [EMAIL PROTECTED] Thanks for your help.

Reply via email to