Save bug with OS X/Java 1.4.1 DP 10?
Save bug with OS X/Java 1.4.1 DP 10?
Here's a scenario I've been experiencing using Oxygen on Mac OS X with Java 1.4.1 Developer Preview 10.
1. I save the results of an XSL transformation to a given filename (i.e., "site.html")
2. I make changes to the stylesheet or the XML file and then re-apply the transformation. Visually, the result panes reflect the changes I made.
3. I save it to the same filename. It asks if I want to overwrite the existing file. I choose "Yes."
4. When I go to inspect the supposedly updated "site.html" file, it has not changed (the time/date stamp has not changed, as well).
Typically, I get around this by deleting the file and then saving afresh, or by adding a number to the filename to distinguish it. Still, it's a little inconvenient. Can anyone else replicate this?
1. I save the results of an XSL transformation to a given filename (i.e., "site.html")
2. I make changes to the stylesheet or the XML file and then re-apply the transformation. Visually, the result panes reflect the changes I made.
3. I save it to the same filename. It asks if I want to overwrite the existing file. I choose "Yes."
4. When I go to inspect the supposedly updated "site.html" file, it has not changed (the time/date stamp has not changed, as well).
Typically, I get around this by deleting the file and then saving afresh, or by adding a number to the filename to distinguish it. Still, it's a little inconvenient. Can anyone else replicate this?
Hi,
We will install DP10 and try to reproduce and fix this problem. This is actually a good news as last time we tried JDK 1.4 DP9 but we were not able to run oXygen due to an exception:
java.lang.NullPointerException
at
sun.java2d.SunGraphicsEnvironment.getAvailableFontFamilyNames(SunGraphicsEnvironment.java:327)
at
sun.java2d.SunGraphicsEnvironment.getAvailableFontFamilyNames(SunGraphicsEnvironment.java:359)
...
Best Regards,
George
We will install DP10 and try to reproduce and fix this problem. This is actually a good news as last time we tried JDK 1.4 DP9 but we were not able to run oXygen due to an exception:
java.lang.NullPointerException
at
sun.java2d.SunGraphicsEnvironment.getAvailableFontFamilyNames(SunGraphicsEnvironment.java:327)
at
sun.java2d.SunGraphicsEnvironment.getAvailableFontFamilyNames(SunGraphicsEnvironment.java:359)
...
Best Regards,
George
We updated the OSX to 10.2.4 yesterday and put also the DP10 but we got the same exception... Commenting out the font selection part we were able to start the program but there was no cursor and we were not able to edit files.
Are you sure you are running JDK 1.4.1 with oXygen ?
Please try to start the application from a terminal using the oxygenMac.sh startup script after you execute a
java -version
to see that it is really 1.4.1.
Due to the non final status of JDK 1.4 on Mac we cannot say we support it (you see that we cannot even run the product with it). When JDK 1.4 will reach a final status we will support it for sure, until then the supported version for Mac is 1.3.
All the best,
George
Are you sure you are running JDK 1.4.1 with oXygen ?
Please try to start the application from a terminal using the oxygenMac.sh startup script after you execute a
java -version
to see that it is really 1.4.1.
Due to the non final status of JDK 1.4 on Mac we cannot say we support it (you see that we cannot even run the product with it). When JDK 1.4 will reach a final status we will support it for sure, until then the supported version for Mac is 1.3.
All the best,
George
Java version
For what it's worth, this is what I get:
I upgraded to 1.4.x because it was so much faster and more responsive than 1.3.x. As I said, I can get around the bug, but I thought I should report what I was experiencing in case it is more widespread.
I upgraded to 1.4.x because it was so much faster and more responsive than 1.3.x. As I said, I can get around the bug, but I thought I should report what I was experiencing in case it is more widespread.
Java 1.4.1 Final
Well Apple released their final version of Java 1.4.1 (11Mar)
[Powerbook-G4:/usr/local/xml-cocoon-2.1-dev] dpetrie% java -version
java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-39)
Java HotSpot(TM) Client VM (build 1.4.1_01-14, mixed mode)
Oxygen still seems to run. Knock on wood...
Darren
[Powerbook-G4:/usr/local/xml-cocoon-2.1-dev] dpetrie% java -version
java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-39)
Java HotSpot(TM) Client VM (build 1.4.1_01-14, mixed mode)
Oxygen still seems to run. Knock on wood...
Darren
Final Java 1.4.1 does not fix
I still have the save bug as originally posted above. Since no one else has reported it, and I have not been able to test this on another OS X installation, it could be something broken in my own setup.