You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Uri Boness (JIRA)" <ji...@apache.org> on 2010/03/17 22:03:27 UTC

[jira] Updated: (SOLR-1829) Cleaned up analysis.jsp - removed all token API scriptlets

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

Uri Boness updated SOLR-1829:
-----------------------------

    Attachment: SOLR-1829.patch

this patch uses jquery to generate the proper requests to the field analysis request handler, then applies xsl transformation on the response to render it appropriately. It also updates the jquery version to 1.4.2. 

The UI is *slightly* different for simplicity, but also a bit enhanced. Now when choosing to analyze by field type/name, a drop down with all possible types/names will be populated.

In order to support all functionality of the analysis.jsp, the FieldAnalysisRequestHandler & co. had to be enhanced. They now accept analysis.verbose parameter which dumps more information over the tokenizer/filter. The verbose format differs a bit from the non-verbose, but that will not break BWC as when not using this parameter, the old format is returned.

> Cleaned up analysis.jsp - removed all token API scriptlets
> ----------------------------------------------------------
>
>                 Key: SOLR-1829
>                 URL: https://issues.apache.org/jira/browse/SOLR-1829
>             Project: Solr
>          Issue Type: Improvement
>          Components: web gui
>    Affects Versions: 1.4
>            Reporter: Uri Boness
>             Fix For: 1.5, 1.6, 3.1
>
>         Attachments: SOLR-1829.patch
>
>
> The analysis.jsp was polluted with the old token stream api in scriptlets all over the place. Since the introduction of the FieldAnalysisRequestHandler, there's no need to keep this mess. Instead, the page can just call the analysis request handler and with parameter generated by the form and display the xml response the same way as it is displayed at the moment. Moreover, it will save some work when updating the code base to the new token stream API.

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