The java file is in different project. I actually got some additional
info on that one: It seems that this is an isolated case, as only
this Java file isn't reloaded for hot-fix, while other ones are. It
might be because some strong reference to static handles prevent the
VM to reload a new version of the class, I don't know. So please
disregard this issue for now. I'll see if I can dig more into that
one and file a bug report to Eclipse.
Thanks,
Sebastien
On May 24, 2006, at 4:48 AM, Ulrich Köster wrote:
> Is the java class on the classpath / in a different project?
>
> Uli
>
> Am 23.05.2006 um 01:43 schrieb Sébastien Sahuc:
>
>> OK, more info. The hot-fix on non-WOComponent java source works
>> once and only once. After that, all subsequent hot-fix attempts
>> become 'obsolete method', and stepping down in those methods while
>> debugging gives me this:
>> <pastedGraphic.png>
>>
>> Isn't that weird when you know that java source for WOComponents
>> do not have this limitation !
>>
>> Sebastien
>>
>> On May 22, 2006, at 4:27 PM, Sébastien Sahuc wrote:
>>
>>> Folks,
>>>
>>> With the lastest everything (RC5 + WOLips 2.0.0.131), the hot-fix
>>> feature is not picking up any change that happens in a Non-
>>> WOComponent java class. It does work for java classes that are
>>> part of WOComponents. Even if I set a breakpoint inside the non-
>>> WOComponent java source, it never suspends, always bypassing the
>>> breakpoint.
>>>
>>> Any idea what's going on ?
>>>
>>> Thanks,
>>>
>>> Sebastien
>>
>
This archive was generated by hypermail 2.0.0 : Wed May 24 2006 - 13:04:26 EDT