Ed Ewing

There is a nice directory of java look-and-feels here: http://www.javootoo.com/

You may be able to use the 'Skin' look and feel to emulate KDE.

Good luck!

Yes this seems like the right place to post your question.

I think you should not be trying to write a logging file into a jar file. Certainly you can't write into the same jar file your jnlp application is running from. (Because modifying the file in that way would invalidate the jar signature.)

You need to write your log file somewhere else. Perhaps in the user's home directory, or perhaps ask the user where they want it to be written.

Basically you have to create an instance of the class FileFilter, then call JFileChooser.addChoosableFileFilter().

You will also want to remove the "accept all" file filter. This is the basic idea:
JFileChooser my_chooser = new JFileChooser(); FileFilter my_filter = new MyFileFilter(); my_chooser.removeChoosableFileFilter(my_chooser.getAcceptAllFileFilter()); my_chooser.addChoosableFileFilter(my_filter);

There is a tutorial here:

http://java.sun.com/docs/books/tutorial/uiswing/components/filechooser.html

The problem might be this line

<j2ee-application-client-permissions/>

Or the problem may be that you are trying to access certain System properties. The documentation here might be useful:

http://lopica.sourceforge.net/ref.html#security

On Linux, the files go into your home directory under the directory ".javaws/cache". But you shouldn't need to know that.

In some cases, JComboBox.setPrototypeDisplayValue() can be helpful. It depends on the LayoutManager and the size of the display area whether this will have any affect, but you may want to try it.

Instructions on detecting the presence of WebStart are available on Sun's page:

http://java.sun.com/j2se/1.5.0/docs/guide/javaws/developersguide/launch.html

That script seems good at detecting whether WebStart is installed or not. I'm not sure I like their instructions on how to auto-install WebStart if it isn't installed.

Originally posted by seema pal:
"JAR resources in JNLP file are not signed by same certificate."

The error message above seems pretty clear to me. You are required to sign all of the jar files using the same jarsigning certificate.

One of my coworkers is seeing only numbers in his java console, instead of the text that is being sent there.

Have any of you ever seen something like this:

Java Web Start Console, started Tue Nov 22 12:51:52 PST 2005 Java 2 Runtime Environment: Version 1.5.0 by Sun Microsystems Inc. 8311697114116105110103323473110116101103114971161011003271101110111109 1013266114111119115101114341310861011141151051111105832524648491310131 0108111971001051101033210010110297117108116321121141011021153210211411 1109583247105103989510010110297117108116951121141011021154612010910813 1011210811710310511044321109710910132613278101119327111497112104761119 7100101114443299108971151153261329911110946971021021211091011161141051



He claims he is using WebStart 1.0.1, and clearly it is JRE 1.5.0.

He probably needs to up-date the version of WebStart, but still this is such funny behavior from the console that I just had to ask if anyone has any explanation.

Here is another link at the sun site about this bug. It seems to have been around for a long time:

http://forum.java.sun.com/thread.jspa?threadID=212136&messageID=727737

You probably need this in your jnlp file:
<security> <all-permissions/> </security>

You will also have to sign your jar files with "jarsigner".

Originally posted by soumya ravindranath:
This is my apache/htdocs/Notepad/notepad.jnlp

<j2se version="1.3+" href="http://java.sun.com/products/autodl/j2se"/>

It might be possible that the href to java.sun.com is incorrect. As far as I can tell, that is not a valid URL. Simply remove that href and try again:

<j2se version="1.3+"/>

Note that this is just a guess. You seem to have already tried all the other suggestions I had.

The quick-and-dirty answer is to create a subdirectory in the user's home directory and store your dirty secrets there.

For example:
String user_home = System.getProperty("user.home"); File fil = new File(user_home, "secret_directory"); if (! fil.exists()) { fil.mkdirs(); }


You could take advantage of the separate Windows and Unix conventions of putting data in "Application Data" and in files beginning with ".". If the directory "Application Data" exists, you know you are on Windows. (But I doubt this works in non-English-speaking environments.)
String app_dir = null; String home = System.getProperty("user.home"); String app_data = home + "/Application Data"; File app_data_dir = new File(app_data); if (app_data_dir.exists() && app_data_dir.isDirectory()) { app_dir = app_data + "/MyProgramName/"; } else { app_dir = home + "/.MyProgramName/"; }


A more transparent solution is to ask the user where to store files. The first time the program runs, it checks to see if the user has picked a location to store files. You can do this with the Preferences API.
If that directory has been defined, and exists, use it. Otherwise ask the user where to put your files and remember that location with the Preferences API.
Preferences my_prefs = Preferences.userRoot().node("/com/foogle/goo"); String dir_name = my_prefs.get("Storage Place", null); File dir = null; if (dir_name != null) { dir = new File(dir_name); } if (! dir.exists() || ! dir.isDirectory()) { // The directory specified in the prefs doesn't exist! // Maybe issue a warning, then ask the user what directory to use. dir = null; } if (dir == null) { // pop-up a JFileChooser to ask user where to store file // dir = ... // dir.mkDirs(); // Now that you know the directory, store the name in the Preferences: my_prefs.put("Storage Place", dir.getAbsolutePath()); }


Wherever you put the directory, I recommend that you let the user know where that directory is. For example, if you have a "Help->About" menu item, that could give information about where this directory is at, and might give the user a chance to move this directory and/or clear the contents.

Originally posted by Craig Wood:
I would avoid the plaf code option.
Possibilities:
1 — make a method in your app that will do this for each table
2 — make and use a special JTable class that overrides the method

Thanks for the suggestions.

I don't want to do it that way because I want to encourage a consistent JTable look and feel throught the application without needing to edit every place in the code that creates a JTable. The application has a plug-in architecture (partially), so I can't control the code written by others.

Anyway, I found a fairly simple answer to my own question, and I'm going to try this for a while.

Somewhere in the start-up of the application I call:
javax.swing.UIManager.put("TableUI", MyTableUI.class.getName());

Where the class MyTableUI is defined like this:

public class MyTableUI extends BasicTableUI { public MyTableUI() { super(); } public static ComponentUI createUI(JComponent c) { return new MyTableUI(); } public void installUI(JComponent c) { super.installUI(c); JTable table = (JTable) c; table.setDefaultRenderer(Boolean.class, new BooleanTableCellRenderer()); table.setDefaultRenderer(Color.class, new ColorTableCellRenderer(true)); table.setDefaultEditor(Color.class, new ColorTableCellEditor()); } }


I've left off the import statements, as well as the definition for ColorTableCellRenderer() and ColorTableCellEditor(). Those are based on the ones in Sun's tutorials, but are modified such that "focus", "selected" and "editable" are all taken into account in the same way that they are for the DefaultTableCellRenderer.

Note that this simply re-defines the default renderers for JTable. These defaults can still be overridden by any specific JTable. And I have tested that this looks good with the three big Look-and-Feels: Metal, Aqua, and Windows.

I hope this proves useful to others. It really bothers me that the default renderer for Boolean objects doesn't give good feedback for keyboard focus the way the DefaultTableCellRenderer does. I consider that a bug in Swing. Now that I'm used to using this renderer, it is hard to live without it in other applications.

Hi,

I have written a replacement for the default BooleanTableCellRenderer.

I know how to apply it to a single table:

table.setDefaultRenderer(Boolean.class, new BooleanTableCellRenderer());

But I would like to apply it to ALL JTables in my application.

Is there a simple way to do this? My guess is that I need to create a custom LookAndFeel. All the documentation I've seen on that looks very complicated. Isn't there some simple way to change just one part of the look and feel?


FYI:
I don't like the default renderer because it gives no visual clue where the keyboard focus is or whether the cell is editable. Such visual feedback is very useful when moving through the table with keyboard controls rather than the mouse. I made my renderer display "focus" and "editable" properties in the same way that the renderer for Strings does.

Here is the class, in case you'd like to use it too.

public class BooleanTableCellRenderer extends JCheckBox implements TableCellRenderer { public BooleanTableCellRenderer() { super(); setBorder(null); setBorderPainted(true); setHorizontalAlignment(JLabel.CENTER); } public Component getTableCellRendererComponent(JTable table, Object value, boolean isSelected, boolean hasFocus, int row, int column) { if (isSelected) { setForeground(table.getSelectionForeground()); setBackground(table.getSelectionBackground()); } else { setForeground(table.getForeground()); setBackground(table.getBackground()); } if (hasFocus) { setBorder( UIManager.getBorder("Table.focusCellHighlightBorder") ); if (table.isCellEditable(row, column)) { setForeground( UIManager.getColor("Table.focusCellForeground") ); setBackground( UIManager.getColor("Table.focusCellBackground") ); } } else { setBorder(null); } setSelected((value != null && ((Boolean)value).booleanValue())); return this; } }