Not sure if this may be useful but......
In looking up the ASDK - the aglets sdk I noticed that during the setup of the SDK, ANT_HOME is to be set to C:\AGLETS I know that ANT_HOME for TOMCAT is different - not that you are using TOMCAT but that ANT_HOME is used differently in each case.
Upon unzipping the src files for Aglets 2.0.2
it is apparent that there is a file Message.class at the following path - com.ibm.aglet
Could it be that somewhere in your autoexec or environmental varaiables
the Aglets that appear to possibly being used within your code are looking in the wrong place
due to the ANT_HOME not being what it was originally when the Aglets SDK was setup.
Please note - I am not familiar with the ASDK at all - just digging a bit to
assist in any way I might be able - to help point you possibly in the right direction
Hope the above is found to be of some use
Dave Flanagan
At 08:50 PM 3/23/02, you wrote:
cem2 wrote: > java.io.IOException: FileNotFound: > /root/aglets/public/org/apache/xerces/impl/xpath/regex/message.class
I think this is the nature of the way resource bundles are loaded by the Java system. (What platform are you running on?) But...
If you want to get rid of the error messages, fake Java into thinking that those files exist. Simply create new resource bundle classes for org.apache.xerces.impl.xpath.regex.message and org.apache.xerces.impl.xpath.regex.message_en.
There might be an easier solution, though. Because the resource bundle system also looks for .properties files, you might be able to get away with just the following empty files in the Jar file with Xerces (or in the same directory if you've extracted the contents):
org/apache/xerces/impl/xpath/regex/message.properties org/apache/xerces/impl/xpath/regex/message_en.properties
You'll either have to rebuild the Jar file with these files included OR extract the Jar file to a directory, add these files to the appropriate directory, and then make sure to have your application point to the directory instead of the Jar file.
Try it out and see if that works. I don't know what else to suggest because I don't get these types of errors when using Xerces.
-- Andy Clark * [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
