The fix was wst / server specific. In short, there was just some API I
wasn't aware of where when launching your server's launch
configuration, you're supposed to call back to the server and tell it
what 'mode' it was in. So again, wst specific. Nothing you'll be able
to make use of ;)
On 9/20/06, Max Rydahl Andersen <max.andersen@jboss.com> wrote:
> It was mostly a user error -- he forgot to setup his source lookup in his
> launch configuration.
hmm...didn't know that were required for hot-replacement, but it kinda
make sense
for eclipse to use that to figure out which of possible N debugged
programs that
is running needs hot-replacement when a file changes.
> That being said, there was a bug with WTP not recognizing that the JBoss
> server instance wasn't in "debug" mode.. but Rob has already fixed that
> since last time I talked to him (a few hours ago)
Ok, this explains it all ;)
Rob - what is the fix for that ? (I'm fiddling with "debug-mode" in another
context and would like to avoid repeating the error).
p.s. any news on commit (and jira) mail notification ? :)
/max
> On 9/19/06, Max Rydahl Andersen <max.andersen@jboss.com> wrote:
>>
>> Hi guys,
>>
>> What were the conclusions/reasons for the debugging issues with our
>> current AS adapter we talked shortly about on irc earlier today ?
>>
>> --
>> --
>> Max Rydahl Andersen
>> callto://max.rydahl.andersen
>>
>> Hibernate
>> max@hibernate.org
>> http://hibernate.org
>>
>> JBoss a division of Red Hat
>> max.andersen@jboss.com
>> _______________________________________________
>> jbosside-dev mailing list
>> jbosside-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosside-dev
>>
>
>
>
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
max@hibernate.org
http://hibernate.org
JBoss a division of Red Hat
max.andersen@jboss.com
_______________________________________________
jbosside-dev mailing list
jbosside-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosside-dev