> I have my jar file that requires 3 files to be placed
> in the bin and lib of the JRE folder.
This is generally bad design. You should not require your client to place any files inside the JRE folder.
What is it that you are attempting to resolve by imposing this requirement on your client.
> I am implementing comm.jar or rxtx.org, both which require
> there be a file or two in the JRE folder.
What do you mean.. Is comm.jar a special vendor jar or is it your jar. Are you working with a third
party software jar that has these requirements about the JRE folder..
I don't see any reference to javax.commm in the current java 5 API. Do you mean to suggest that you are attempting to distribute an application which requires another jar file, with 3rd party classes, or older Sun classes, to be on the classpath?
> I have my jar file that requires 3 files to be placed in the bin and lib of the JRE folder.
So when you refer to files you mean jar files? Jar files that contain the classes in the javax.comm package?
Yeah, you don't really want to assume any programmatic control over the bin directory of the JRE as it is exists on the client. Normally when an application that is developed requires the presence of 3rd party jars on the classpath, you could distribute those jars with your own application jar and edit the classpath header in the Manifest file for the application jar. But it sounds like distributing the Sun jars with your app may not be feasible, and in that case alerting the client in writing before hand that your app requires other software to be installed would be the way to go. Have the end user take the responsbility for putting those jars in their own JRE ext lib maybe...
btw: thanks
Message was edited by:
nantucket