[Springframework-developer] Assumption about stack trace format and cacao

[Olivier J. <oli...@pc...>]

Hi,
 I'm using spring+GNU classpath right now to ensure that the free java
implementations can get the best framework around running neatly and when
underdoing the Jdk13ControlFlowTests, I noticed that the checks involving
methods were not working.
 After a bit of investigations, I found that the stack trace generated by
cacao was putting an extra space between the end of the method name and
the parenthesis to precise the location. Since for 1.3 spec level the
search is done within the string image of the stack trace, the exact
formatting is very important and breaks in this case.
 I was wondering who was "wrong" there and it seems that the sun javadocs
state that the format used by their jdk (and described in the docs) is
only an example (pasted from the Throwable javadoc : "The format of this
information depends on the implementation, but the following example may
be regarded as typical: [...]") so I don't think cacao can be thought as
non compliant with the spec. On the other hand, I do understand that if
the spec doesn't give details about the format, we either have to make
assumptions or forget it totally (but we don't have any other way to get
the stack trace in jvm1.4- afaik).
 So basically I was wondering whether spring had to be aware of this quirk
(either by using a cacao compliant regexp when looking for methods, using
probably [ ]? or by "flagging" the test as runnable only in certain jvm
implementations) or if cacao had to be adapted.
 Thanks for your feedback
Olivier