Debug several eSpaces

By Carlos Freitas on 9 Feb 2012
If we are in Debug mode and the action references some action / page from an external eSpace we should be able to continue debugging (at least if we had the 2 eSpaces opened in Service Studio)
That is already possible.

For the referenced eSpace:
- Open it in service studio,
- Set a breadpoint,
- Click debugger and select 'select entry eSpace',
- Click debugging in public area

Now you can call the action from the public property of the selected entry espace and you action will be debugged.
Kilian Hekhuis16 Feb 2012
Yeah, but that's not very user friendly, and often it fails for some reason.

It indeed can be more user friendly :).

For me it works every time...

João Melo8 May 2015
Guys, when I click 'Select entry eSpace', the only option I get is '(this eSpace)'.

What can I do??
Tiago Neves8 May 2015
João,
You must do that step in the referenced eSpace.
Kilian Hekhuis8 May 2015
Sometimes you don't see them because the consumers aren't published after publishing the consumer. But such a question should really be in a separate forum thread, not on this idea!
João Melo8 May 2015
I don't know why, but it worked today... Thanks folks..
Rebecca Hall8 May 2015
It would be better to just turn on the debugger than selecting entry espace.  Its difficult getting debugger to catch.
João Melo8 May 2015
Totally agree with Rebecca... So it is still an idea!
Gavin Horne2 Jul 2015
Also agree with Rebecca, very flaky behaviour, sometimes it works, sometimes it doesn't, depends on how I hold my tongue when starting the debugger I think :)
Leonardo Fernandes27 Jul (4 weeks ago)

Few people actually know how the Select Entry Module works. I frequently see people complaining that the breakpoint is not stopping, without realizing they were attached to the wrong module. But it's not their fault, this information is hidden, and the Select Entry Module dialog doesn't provide any help on how to use it:

A few ideas on how to improve it:

- Make 'step into' work even for consumed objects. For example, when stepping into a referenced action, Service Studio would ask for download the producer, set the breakpoint at the start of the action, and attach the debugger to the correct module, before actually stepping into the action. Likewise, 'step out' would need to work consistently across modules.

- Document how to debug producers in the help file. Really.

- Have a more concrete text in the Select Entry Module dialog, helping to choose the correct module, referring to scenarios like debugging a consumed web block, or a consumed action, debugging timers and web services...



Merged from 'Simple debugging of producers' (idea created on 2017-07-27 04:40:45 by Leonardo Fernandes), on 2017-07-28 13:27:59 by Leonardo Fernandes
Rebecca Hall27 Jul (4 weeks ago)

I would like to just turn on the debugger and then have it stop on breakpoints for espaces I have open.  This is one of the biggest hangups for new developers too.



Merged from 'Simple debugging of producers' (idea created on 2017-07-27 04:40:45 by Leonardo Fernandes), on 2017-07-28 13:27:59 by Leonardo Fernandes
Vasco Pessanha28 Jul (3 weeks ago)

Totally makes sense (add another Like) ;)

Also related to this one:
https://www.outsystems.com/ideas/1033/debug-several-espaces


Cheers,



Merged from 'Simple debugging of producers' (idea created on 2017-07-27 04:40:45 by Leonardo Fernandes), on 2017-07-28 13:27:59 by Leonardo Fernandes
Justin James28 Jul (3 weeks ago)

You CANNOT get rid of the "Select Entry Espace" step without completely changing the way publishing a producer works. Why? Because each deployed Espace is a separate application in IIS, WAR in JBoss, to attach the debugger to. The system shouldn't attach to ALL deployed applications on the server, that would be nuts.

J.Ja