You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@nutch.apache.org by "Hal Finkel (JIRA)" <ji...@apache.org> on 2007/07/22 01:58:06 UTC

[jira] Created: (NUTCH-523) web2 searchform problems with patch

web2 searchform problems with patch
-----------------------------------

                 Key: NUTCH-523
                 URL: https://issues.apache.org/jira/browse/NUTCH-523
             Project: Nutch
          Issue Type: Bug
          Components: web gui
            Reporter: Hal Finkel
         Attachments: SearchForm.patch

In the current trunk, SearchForm.clone() does not make a deep copy of the KeyValue objects which can be then modified by the caller. This causes incorrect behavior when using the spell-check plugin. Also, SearchForm.setValue() can cause the old key-value pair to appear in active along with the new pair, which is also incorrect. This patch fixes both of these issues.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (NUTCH-523) web2 searchform problems with patch

Posted by "Hal Finkel (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/NUTCH-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hal Finkel updated NUTCH-523:
-----------------------------

    Attachment: SearchForm.patch

> web2 searchform problems with patch
> -----------------------------------
>
>                 Key: NUTCH-523
>                 URL: https://issues.apache.org/jira/browse/NUTCH-523
>             Project: Nutch
>          Issue Type: Bug
>          Components: web gui
>            Reporter: Hal Finkel
>         Attachments: SearchForm.patch
>
>
> In the current trunk, SearchForm.clone() does not make a deep copy of the KeyValue objects which can be then modified by the caller. This causes incorrect behavior when using the spell-check plugin. Also, SearchForm.setValue() can cause the old key-value pair to appear in active along with the new pair, which is also incorrect. This patch fixes both of these issues.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.