On Feb 13, 2009, at 9:51 AM, Marcelo Morales wrote:
> > Thank you very much. > > On Fri, Feb 13, 2009 at 12:30 PM, Joshua Marinacci > <[email protected]> wrote: >> >> Couldn't you download JavaSE 6u12 and test it yourself on another >> machine? The bug appears to have been closed down because the testers >> couldn't reproduce it. >> If your environment is suffering from the bug and you know how to >> reproduce it then please submit instructions. > > Unfortunately I don't know how to reproduce it. It happens one or > twice every week on heavy load on a veeery busy application. The > workarround is very ugly, catching a NPE and retry. Ah. Well, please test the new version if you can. Lot of things were improved in the font handling in 6u10. >> Yes, upgrading your version of Java is generally safe (especially >> point releases like u3 to u10). We place a very high priority on >> backwards compatibility and do endless testing. It doesn't catch >> everything, but it caches most things and any regressions are quickly >> escalated to blockers. >> > > Excellent!. Can I quote you? absolutely. Compatibility is one of the main drivers of Java. > > >> - J >> > > Best regads > >> On Feb 13, 2009, at 6:09 AM, [email protected] wrote: >> >>> >>> Hi >>> >>> I've got a couple of questions. >>> >>> I've (well... my clients have) been suffering from a closed, >>> tagged as >>> Not Reproducible, bug on bugs.sun.com. >>> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6367148 >>> There is no way to vote for a closed issue, so I just left a comment >>> there. >>> Is there any other/better/faster way to influence a re-open? >>> >>> Maybe it is not the case anymore, since I am using an older >>> release of >>> java (java version "1.6.0_03"). Is there a way to see if the >>> proposed >>> change made it into newer releases, like update 10?. "Just upgrade, >>> just in case" you would say, but the enterprise will NOT upgrade >>> unless there is a compelling reason to do it, like a documented >>> bugfix >>> they are suffering from. And will upgrade only after an expensive >>> and >>> time-consuming round of testing, since it is a mission-critical >>> application. So I am reluctant to recommend a change before getting >>> all bases covered. >>> >>> Does the "write once, run everywhere" mantra still works with all >>> these language changes nonsense?. I mean, Do you think is it safe to >>> just upgrade java?, Do you think it will still be after the proposed >>> changes for openjdk and java 7? >>> >>> regards >>>> >> >> >>> >> > > > > -- > Marcelo Morales > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
