[#WET-223] The DeleteParameter() method of the Transaction class produces some undesirable output

WET

The DeleteParameter() method of the Transaction class produces some undesirable output

Created: 11/Sep/06 02:24 AM Updated: 18/Jun/07 10:20 AM

Component/s:

None

Affects Version/s:

0.9.8_beta1, 0.9.8 Final

Fix Version/s:

Future

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Description

« Hide

The Transaction.DeleteParameter(int index ) deletes even the last element along with the parameter to be removed ..

Steps ::

Create a transaction object .
    Add around 5 parameters through AddParameter(int key, String value)
   Now try to remove any element other than the last element ..
      For example ::
                     transactionObject. DeleteParameter(2) ,
    This statement deletes the parameter at index 2 .
But along with that it also Deletes the last Parameter ..

Result of execution::

The parameter at index 2 is set to null.
But the last parameter is removed from the parameters list

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Raghu Venkataramana - 16/Sep/06 01:20 AM

This typically shouldn't cause any problem at the usage level because we dont call this method yet. It will be used when we allow insertion / deletion of parameters.

[ Permlink | « Hide ]

Raghu Venkataramana - 23/Jan/07 02:49 AM

See previous comment. Since this is not of high impact, we'll leave it out of the 1.0 release