This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 110918 - Last initparam value is always taken as null
Summary: Last initparam value is always taken as null
Status: VERIFIED FIXED
Alias: None
Product: contrib
Classification: Unclassified
Component: Portalpack (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Satyaranjan D
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-25 12:41 UTC by uchithra
Modified: 2009-03-17 07:24 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description uchithra 2007-07-25 12:41:05 UTC 
Create a portletfilter .Assign init param name and value as "param1" and "value1".

Now check the portlet.xml file.It displays the value as null as follows.If you create more than on parameter,
the last value tends to be null.

<filter>
    <filter-name>test</filter-name>
    <filter-class>NewnewFilterWizard</filter-class>
    <lifecycle>ACTION_PHASE</lifecycle>
    <init-param>
      <name>param1</name>
      <value />
    </init-param>
  </filter>
Comment 1 Satyaranjan D 2007-08-01 12:24:28 UTC 
The problem happens when user enters something in a JTable cell and then go to an another component without pressing
enter. In this scenario the enter value doesn't get registered in the table model. This problem is fixed by explicitly
calling table.editCellAt(-1,-1) .
Comment 2 uchithra 2007-08-02 13:48:38 UTC 
verified