On Mon, 28 Mar 2005, Brad BARCLAY wrote: > The javax.usb JARs themselves are found due to the copy placed in the >jre/lib/ext directory,
I didn't put them there, I assume you copied them there? That should be ok just checking. > I've come up with a temporary work-around here by simply using the JAR >tool to add the property file to the Linux RI JAR far. Is there any >reason why this isn't the default? As you can't use the Linux RI >without this file, IMO adding it with the proper Linux settings to the >Linux RI JAR file makes some sense (although at the same time, this >does make it somewhat more onerous upon the user if that have to edit >any of the default parameters in that file). That's exactly why it was taken out of the jarfile, it's much harder to actually modify any of the settings when it's in a jarfile. Personally, I am reluctant to include a configuration file inside a library/package...it would be kind-of like (e.g.) putting /etc/ssh/sshd_config inside /usr/sbin/sshd and if a user wanted to modify the sshd settings, they'd have to use some tool to extract the sshd_config file, modify it, and re-create the sshd program... > I'm thinking that it might be useful to have a "default" version of >the properties file in the Linux RI JAR under a different name, which >can be loaded if the user-modifiable properties file >(javax.usb.properties) can't be loaded for some reason. The current >setup prevents applications using the API from being launchable JARs, >unless each application re-bundles javax.usb itself. If there's a properties file inside the jar, it doesn't really need to be named anything different, the ordering of the CLASSPATH can be used to determine which is used. But I'm worried about mass confusion if there are multiple properties files that are used depending on one thing or another. "I changed the setting in my properties file but it didn't do anything..." or "I checked my properties file and the tracing is enabled but it doesn't trace anything!". Because of course the other properties file is being used... I'd like the properties file to be (by default) /opt/javax-usb/etc/javax.usb.properties, period...if you modify that file, you know the changes will get used. > Thoughts? Ideas? There has to be a better way to handle this file -- >while not really your fault, it seems unfortunate to have to tell >people they can't launch an application via the -jar parameter because >of a property file :). Is the -jar behavior part of the JVM spec or specific to a single JVM implementation? Seems like disregarding the env CLASSPATH is just stupid... :) > As an aside, with the latest javax.usb for Linux implementation, I'm >getting an "Unable to log: JavaxUsb class has no log method." error >message when running on FC3 with Sun JDK v1.5.0. Any thoughts as to >why? Ick, no idea...I will check on that. Open a bug to track it. -- Dan Streetman [EMAIL PROTECTED] --------------------- 186,272 miles per second: It isn't just a good idea, it's the law! ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ javax-usb-devel mailing list javax-usb-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
