Hi,
I have a strange problem.
For my engine (eEngine) I use managed images and all worked well and fast. I get accelerated images when starting from eclipse or command line. I use Java 1.5 and Java 1.6-ea.
But when I start from webstart, then all acceleration seem to be away. 
In the webstart console I see the application runs with Java 1.6. Is this a known problem or am I missing some flags for webstart with acceleration?
Do you specify sun.java2d.xxx system properties? If yes, then you must know that webstart ignores any of those for security reasons according to the doc of JDK 1.5. Yes security. What’s unsecure with those parameters? I still don’t know.
I’ve filed bug 6265026, which was closed a dup of this one:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6250769
It should be fixed in mustang. You might want to vote for them, just to let them know
you’re watching =)
Regarding to what’s insecure about these options: by forcing some of them to “true” by default you may
put your users at risk: there are buggy drivers out there which could reboot the system.
Your customers would never know what hit them.
You need to be really careful about enabling them by default. It’s best to devise a way to at least
notify the user what to do in case something goes wrong, or have different .jnlp files or something.
You can also present a user with a preference dialog and then exec a new vm with the chosen parameters
(if there’s enough security permissions)…
Thanks,
Dmitri
Java2D Team
[quote]Regarding to what’s insecure about these options: by forcing some of them to “true” by default you may
put your users at risk: there are buggy drivers out there which could reboot the system.
Your customers would never know what hit them.
[/quote]
Dmitri, I don’t understand your reasoning. To me it’s like saying that executing a graphics app or playing a video game is risky a thing. No one can predicts bad situations like PC reboot because of the so wide variation of hardware. Maybe I miss the point here? Are those sys properties so risky that a bad video drvier might reboot the system?
The reason is that a java-application could (and it will!) under some cirumstances reboot the system or the application will not work on a lot boards if accerlation turned on.
If it crashes users will blame java for failing … which is simply not fair?!
lg Clemens
Thanks for your help.
Is there an option to enable this by default in the jnlp file?
I’m using jnlp spec 1.5+.
I don’t believe there’s a way to enable it in jnlp file in 1.5…