cancel
Showing results for 
Search instead for 
Did you mean: 

Debugging of Portal Components with Netweaver developer studio

Former Member
0 Kudos
56

Hi,

I am trying to debug a portal component. When I start a debug session I can see the connection being set up. All the threads are running, but my portal component is NOT started in a browser session.

The only thing I see is the source code of the "Object" class.

Does anyone experienced the same problems?

Has anyone else experience with debugging portal components?

Thanks,

Ryan Douglas

Accepted Solutions (1)

Accepted Solutions (1)

darrell_merryweather
Active Contributor
0 Kudos

Ryan

How are things, long time no speak.

I debug my portal components all of the time. As long as you have configured everything up to be able to debug, which it sounds like you have, then you need to specifically start your component/application manually. Make sure that you have a breakpoint in your code where you would like it to start the debugger. Once the component starts and this breakpoint has been reached you will then see the source code in NWDS ready for debugging

I hope this helps

Darrell

Former Member
0 Kudos

Hi Darrell,

How are you doing?

This is what happens:

1) I created a very basic AbstractPortalComponent (hello word),

2) I set a break point.

3) I select the debug perspective, select "run==>debug", select the right project and press "debug"

4)I see that a connection is established, the netweaver developer studio navigates automatically back to the "EP perspective"

5) I switch back to the "debug" perspective

6) manually open a new browser session and run the portal component directly (/irj/servlet/prt/portal/prtroot/debug.test).

7) The component runs without being stopped.

So do you have any suggestions?

Regards,

Ryan

darrell_merryweather
Active Contributor
0 Kudos

Strange. The perspective shouldn't switch back to the EP perspective but should display the active threads in a box on the top left, the code just below that, the list of variables in the top right. Also, the breakpoint needs to be on a specific line of code and cannot be on a blank line as blank lines don't get executed. Also, make sure that the line that is actually executed.

Try that and let me know

D

Former Member
0 Kudos

Hi Ryan,

I often have the annoying switch back to the EP perspective as well. Anyways it works.

You might check your configuration against my weblog:

It's a portal debugging step-by-step description.

Regards, Karsten

darrell_merryweather
Active Contributor
0 Kudos

I have had a look at Ryans code and it looks like the problem lies with the portalapp.xml file that was generated from NWDS. When generating a JspDynPage it creates the entry ComponentType with a value of JspNative, which is incorrect for a JspDynPage

I am waiting for Ryan to confirm whether this is the problem or not

D

Former Member
0 Kudos

Hi Darrell,

this will definitely be the problem since the JSPDynpage is never called then.

regards, Karsten

Former Member
0 Kudos

Yes!

This is the solution. This also solved the debugging problem I had.

Many thanks Darrel

Answers (0)