> A jacorb.properties in run.jar would just avoid this warning: > > > #################################################################### > > WARNING: no properties file found! This warning can be ignored for applets. > > > A file file called "jacorb.properties" or ".jacorb_properties" should be > > present in the classpath, the home directory > > (C:\Documents and Settings\jason), the current directory (.) or > > in Javas lib directory (c:\java\jdk1.3.1_02\jre) > > #################################################################### > > The warning may be ignored, so we don't really need to do anything here. > The user can get rid of the warning by putting a jacorb.properties file > in any of the places indicated. Just thought that a dummy properties > file in run.jar would make things look nicer.
Yes, I understand this, but run.jar isn't the place for this. It is created from jboss/system which has *nothing* to do with iiop or jacorb, so this is not the place for such hacks to get jacorb to behave. Drop the file in default/conf. We can't leave this message here, or users will want to know why. > The IBM problem cannot be solved with a jacorb.properties file in run.jar. > To solve it we need one more class file in run.jar. I have implemented > (but did not commit) this. Works perfectly, but run.jar grows from 24264 > bytes to 27211 bytes. A lame workaround (which does not work for netboot) > would be to add jacorb.jar to the system classpath. Yes, I understand this as well... but see my comment above on how run.jar is created. If this is the only was then lets add the file, well commented as to why it is there and when it should be removed (when IBM fixes thier shit). --jason ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
