When you set codebase_lookup to false (which unfortunately is the recommended approach, due to the way the JDK looks up service providers), any resources used by your application need to live in your application's JARs. How do you generate your JARs? Could you modify your build process to add the log4j.xml file to your main JAR before you sign it?
On Jun 22, 2010, at 3:40 PM, JohnRodey wrote: > > It appears as though I have even more problems: > > I sign my jars during build, and then my startup script can either copy the > log4j.xml into a jar or I enable the codebase_lookup. This causes me to get > a popup saying the application contains signed and unsigned code. I would > like to avoid this too. > > What do people do if they want to edit a config file for their application > if its signed? > -- > View this message in context: > http://apache-pivot-users.399431.n3.nabble.com/Help-understanding-classpaths-codebase-with-applets-tp914940p915063.html > Sent from the Apache Pivot - Users mailing list archive at Nabble.com.
