Update 9 to issue 2544 ("Internal compiler exception, appears to be related to multiple static blocks -- when compiling on AIX")- September 17, 2008 IBM has released an SR2 update to J9 for AIX. I've successfully run my test on both the 32-bit and 64-bit versions. So the problem has been fixed. Complete version information below: bash$ java -version java version "1.6.0" Java(TM) SE Runtime Environment (build pap3260sr2-20080818_01(SR2)) IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 AIX ppc-32 jvmap3260-20080816_22093 (JIT enabled, AOT enabled) J9VM - 20080816_022093_bHdSMr JIT - r9_20080721_1330ifx2 GC - 20080724_AA) JCL -...http://code.google.com/p/google-web-toolkit/issues/detail?id=2544#c9 Update 1 to issue 2893 ("Add ability to associate Object user-data with ListBox elements")- September 17, 2008 This will be a little tricky, as it will require a separate table of Objects to be maintained in parallel with the list values. This is because hanging Objects directly from the <select> items will cause memory leaks (circular reference among js and native objects). Summary: Add ability to associate Object user-data with ListBox elementsStatus: AcceptedOwner: j...google.comLabels: Category-UI Type-Enhancementhttp://code.google.com/p/google-web-toolkit/issues/detail?id=2893#c1 Update 1 to issue 2894 ("I18NSync uses SystemCL to get resources")- September 17, 2008 Owner: sco...google.comLabels: Category-Other Type-Defecthttp://code.google.com/p/google-web-toolkit/issues/detail?id=2894#c1 Issue 2895 created: "oncontextmenu event not always previewed correctly"- September 17, 2008 Found in GWT Release: 1.5 Detailed description: 1.5 added support for the oncontextmenu event at the DOM level, but failed to hook it on the document (in DOMImpl.initEventSystem()), so it's not usually previewed unless it happens to occur over an element that has sunk the event. Workaround if you have one: If you call sinkEvents(Event.ONCONTEXTMENU) on those elements you care about, you should still get previews of this event (as well as receiving them directly on the elements where this...http://code.google.com/p/google-web-toolkit/issues/detail?id=2895 Issue 2894 created: "I18NSync uses SystemCL to get resources"- September 17, 2008 Found in GWT Release: 1.5.2 Detailed description: Trying to embed I18NSync (in a maven plugin) fails as it uses SystemClassLoader to load resources. Workaround if you have one: Use ContextClassLoader as this is the expected usage. Links to the relevant GWT Developer Forum posts:http://code.google.com/p/google-web-toolkit/issues/detail?id=2894 Issue 2893 created: "object list box"- September 17, 2008 Found in GWT Release: 1.5.2 Detailed description: enhancement request for an ObjectListBox, a list box that takes an object instead of 2 strings addItem(String item, Object o) the DOM list box item value would be the same as the name but getValue() would return the object in place of a string value. A list behind the scenes could easily manage this task. Any time a list item is moved simply move the corresponding index of the array. A set collection would keep duplicate item strings out of..http://code.google.com/p/google-web-toolkit/issues/detail?id=2893 Update 2 to issue 2886 ("Internal compiler error with autoboxed fields and ++ operator")- September 17, 2008 I am confident that the correct patch is to the inliner. Having a local decl statement is fine if you actually need to run an initializer, but it shouldn't be required. Inliner should instead be patched to not crash. We could: 1) Check local refs up front and abort early. 2) Abort late if everything succeeds but we notice a local ref in the result expression (ie, remove CloneCalleeExpressionVisitor.visit(JLocalRef) and check afterwards) 3) Throw a well-known exception from...http://code.google.com/p/google-web-toolkit/issues/detail?id=2886#c2 Update 6 to issue 780 ("Programatically selecting text in a TextBox, which is in a Poup Panel")- September 16, 2008 Sorry, I goofed again. I'm actually calling setCursorPos(0), not setFocus, when I get this exception.http://code.google.com/p/google-web-toolkit/issues/detail?id=780#c6 Update 16 to issue 1385 ("TextBoxBase.selectAll() fails in Firefox")- September 16, 2008 Sorry, I goofed again. I'm actually calling setCursorPos(0), not setFocus, when I get this exception.http://code.google.com/p/google-web-toolkit/issues/detail?id=1385#c16 Update 15 to issue 1385 ("TextBoxBase.selectAll() fails in Firefox")- September 16, 2008 Oops, sorry about the hasty comment - I misread the code. The snippet reported in the group post I just linked to has indeed been fixed. Sorry about the false lead. if (length <= 0) throw new IndexOutOfBoundsException() has already been corrected to if (length < 0) throw new IndexOutOfBoundsException() --------- I'm getting the following exception in FF3: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) nsIDOMNSHTMLInputElement.setSelectionRange when calling...http://code.google.com/p/google-web-toolkit/issues/detail?id=1385#c15 |