[
http://jira.nuxeo.org/browse/NXP-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Darlea resolved NXP-1879.
------------------------------
Resolution: Fixed
Fix Version/s: (was: 5.1.4)
5.1.3
<quote>There are several issues in the current publishing mechanism:
- the getSectionsSelectModel() method is using hardcoded reference to the
"Domain" document type</quote>
This is harder to eliminate because there is no facet defined for this, but a
document type in contribs. Also, it would do little thing, because anyway the
"path" (immediately under the root) is hardcoded. It is left outside.
<quote>- the same method above is using the first domain it founds in the
portal, making it impossible to use publishing if one has more than one
domain</quote>
Solved. It now looks for all the domains under the root.
<quote>- there is also a problem with the way the section root and the section
are found: right now, these are found using the facelets "MasterPublishSpace"
and "PublishSpace". The problem is again when one have many domains, each with
it's own type of section roots and sections. The current implementation is
assuming that only a document type exists with the "MasterPublishSpace"
facelet. Same for "PublishSpace" facelet. There are 2 solution I see: either
check only the document types with those facets that exist in the current
domain and assume there is only on section root / section document type per
domain, or change the API so that the getRootName() and getSectionName() return
a list of document types instead of a single String with one document
type.</quote>
Multiple types are suitable for publishing. Both for "SectionRoot" type, as for
"Section" type ("MasterPublishSpace" and "PublishSpace")
For trunk forward port I will open a different task, as the publishing project
wasn't yet split there.
Thx, Radu
> Eliminate hardcodings in the PublishingActionsBean
> --------------------------------------------------
>
> Key: NXP-1879
> URL: http://jira.nuxeo.org/browse/NXP-1879
> Project: Nuxeo Enterprise Platform 5
> Issue Type: Bug
> Affects Versions: 5.1.3
> Reporter: Dragos Ivan
> Assignee: Radu Darlea
> Fix For: 5.1.3
>
> Time Spent: 3 hours
> Remaining Estimate: 0 minutes
>
> There are several issues in the current publishing mechanism:
> - the getSectionsSelectModel() method is using hardcoded reference to the
> "Domain" document type
> - the same method above is using the first domain it founds in the portal,
> making it impossible to use publishing if one has more than one domain
> - there is also a problem with the way the section root and the section are
> found: right now, these are found using the facelets "MasterPublishSpace" and
> "PublishSpace". The problem is again when one have many domains, each with
> it's own type of section roots and sections. The current implementation is
> assuming that only a document type exists with the "MasterPublishSpace"
> facelet. Same for "PublishSpace" facelet. There are 2 solution I see: either
> check only the document types with those facets that exist in the current
> domain and assume there is only on section root / section document type per
> domain, or change the API so that the getRootName() and getSectionName()
> return a list of document types instead of a single String with one document
> type.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://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
