Skip to Content
author's profile photo
Former Member

error in browser

Posted on Apr 20, 2011 at 06:12 AM 11 Views

Hi Folks,

I developed one WDC for seletoptions with tabstrip.Component is activatedwithout any error.But in browser iam getting error attribute could not find.How i will debug this WDA application without seeing any thing on browser

UI Web Dynpro ABAP
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • author's profile photo
    Kiran Kumar Valluru
    Posted on Apr 20, 2011 at 06:17 AM

    Hi,

    Put a break point in WDDOINIT method., and test ur application, then it will open debugger., now u can debug and test where the error is.,

    Thanks & Regards

    Kiran

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Posted on Apr 20, 2011 at 08:36 AM

    Hi Ravi,

    If you are using Select options(Reusable WD component), you might have written some code in the WDDOINIT.

    you might be calling create_range_table and add_selection_field methods. Put a breakpoint at these methods and debug.

    Hope you will find the reason why it is throwing error message.

    Regards,

    Bharath.

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Ashish Shah
    Posted on Apr 20, 2011 at 12:44 PM

    Go to ST22 and check where is the error.

    You might get a hint at what attribute is not found.

    Can you paste the entire stack that you are getting on browser?

    Regards,

    Ashish

    Add comment
    10|10000 characters needed characters exceeded

    • Margaret A Hilsbos Former Member
      Apr 20, 2011 at 01:41 PM

      Hi,

      Is it possible that the node is mapped to the view from the controller but you added attribute 'LOW' later and did not update the mapping?

      Best thing for debugging is to set an external breakpoint in your code right before it tries to access this attribute. Then under 'special tools' in the debugger (you're using the 'new' debugger, right?) look for the webdynpro tool. expand your context to find this attribute. If the attribute isn't there you have to figure out why.

      Hope this helps!

      Margaret