[
https://jira.nuxeo.org/browse/NXP-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anahide Tchertchian resolved NXP-2110.
--------------------------------------
Resolution: Won't Fix
Note sure this is still needed (but that has nothing to do with content views).
We always define prefix for schemas anyway nowadays, so maybe this issue is not
visible anymore.
> Sorting on custom search results columns and schema prefix
> ----------------------------------------------------------
>
> Key: NXP-2110
> URL: https://jira.nuxeo.org/browse/NXP-2110
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Components: Core, Search / Query, Web UI
> Affects Versions: 5.1.3.1
> Reporter: Georges Racinet
> Assignee: Thomas Roger
>
> When using the search column management system (SearchUIService,
> searchColumns Seam component, querymodel's SearchInfo), if the schema
> referred in querymodel's SortInfo has no prefix, the column(s) can't be
> sortable.
> This is due to a discrepancy between what the core and the search service do
> in case of missing prefix.
> Say the schema name is "myschema" and the field name is "myfield". Then the
> search service treats it has
> myschema:myfield, while on the core's Field object, the method
> getPrefixedName() returns simply "myfield"
> A simple solution would be that (webapp-core) FieldHelper throws
> ClientException in that case, therefore forcing the developper to define a
> prefix, which is the good practice anyway.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
