[jira] Updated: (SOLR-636) admin page schema link fails for example multicore config

["Lars Kotthoff (JIRA)" <ji...@apache.org>]

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

Lars Kotthoff updated SOLR-636:
-------------------------------

    Attachment: SOLR-636.patch

This occurs because the ShowFileRequestHandler isn't enabled by default in the multicore example configurations (showing the config fails in the same way).

I'm attaching a patch which changes the multicore example configurations to enable all admin handlers through AdminHandlers. The patch also removes some parameters from the <admin> configuration element which appear to be used only in deprecated stuff.

The patch furthermore changes index.jsp to check for the existence of the ShowFileRequestHandler or the all-in-one AdminHandlers before displaying the links to get schema and config. Also the deprecated getSchemaFile()/getConfigFile() methods are changed to getSchemaResource()/getConfigResource().

I've done a quick search for more solrconfig.xml with deprecated stuff in them and updated the ones in solr-ruby, but *not* the ones used in various tests. This should probably be a separate issue?

> admin page schema link fails for example multicore config
> ---------------------------------------------------------
>
>                 Key: SOLR-636
>                 URL: https://issues.apache.org/jira/browse/SOLR-636
>             Project: Solr
>          Issue Type: Bug
>          Components: web gui
>    Affects Versions: 1.3
>         Environment:  linux x86_64 rhel ibm-java-6 prepackaged jetty
> solr snapshot 7-15-2008 
>            Reporter: Jerry Quinn
>            Priority: Minor
>         Attachments: SOLR-636.patch
>
>
> If I try to view the schema.xml for a single core, using the gui link:
> http://localhost:8983/solr/core1/admin/file/?file=schema.xml
> I get instead:
> HTTP ERROR: 404
> NOT_FOUND
> RequestURI=/solr/admin/file/
> Powered by Jetty://

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