Skip to Content
author's profile photo Former Member
Former Member

Debugging PAR files containing both Services and Components


Does anyone have experience of debugging PAR files that contain both Portal services and components?

I have written a service, which works fine and can be invoked from a KM Scheduler Task and from other Portal components. In order to transport this in a Portal package I created a dummy Portal component using the wizard in NWDS (2.0.14), which created a blank JSPDynpage component and JSP.

I can create an iView from the Portal component in the PAR file, which enables the .PAR file to be transported in a Portal transport package by checking the 'Inlcude dependant objects' option.

The problem I have is that when I add breakpoints in the service and the component and try and debug them, the debugger only stops at the breakpoints in the service and never stops in the component. I added a breakpoint to a line that would always be called, i.e.





Does anyone have a work around for this or know why it happens? I could build and test the entire component in a seperate project in NWDS and then copy to the service PAR file but its a pain I would rather avoid.



Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Jan 10, 2007 at 11:28 AM

    This sounds like the problem you have when creating a JSPDynPage through the wizards. Basically there is a property in the portalapp.xml file called ComponentType (or something similar). This is set to jspnative by default, which is actually incorrect. If this is set, then it thinks that the component should only be using the JSP page, and therefore calls the JSP directly.

    If you remove this line, then you should be able to debug the component also.

    I hope this helps


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.