[ 
https://issues.apache.org/jira/browse/JS2-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851309#action_12851309
 ] 

Randy Watler commented on JS2-1138:
-----------------------------------

Initial SVN commits:
    j2: 929033
    j2-admin: 929032

Notes:
--------------------------------------------------------------

Urls like the following can now be used to view various template documents:

http://localhost:8080/jetspeed/ui/definition.fpsml
http://localhost:8080/jetspeed/ui/template.tpsml
http://localhost:8080/jetspeed/ui/default-content.dpsml

Missing fragment references and page templates currently generate empty 
portlets with errors like this when rendered:

Failed to create rendering job

This is due to the PAGE and REFERENCE portlet types not being recognized and 
portlet names left null. This still needs to be cleaned up.

None of these features have been tested in the "/portal" pipeline: it is 
unlikely that these types will be editable in that portal configuration.

The following important APIs have been added and/or modified:

PageLayoutComponent:
-----------------------------------------------------------------------------
ContentFragment addFragmentReference(ContentFragment contentFragment, String 
id, int row, int column);
ContentFragment addFragmentReference(ContentFragment contentFragment, String 
id);
ContentFragment addFragmentReference(ContentPage contentPage, String id);
void newSiblingDynamicPage(ContentPage contentPage, String pageName, String 
contentType, String layoutName, String pageTitle, String pageShortTitle);
void newSiblingPageTemplate(ContentPage contentPage, String templateName, 
String layoutName, String templateTitle, String templateShortTitle);
void newSiblingFragmentDefinition(ContentPage contentPage, String 
definitionName, String defId, String portletName, String definitionTitle, 
String definitionShortTitle);
void updateContent(ContentPage contentPage, String contentType, Boolean 
inheritable);
void updateRefId(ContentFragment contentFragment, String refId);

ContentPage:
--------------------------------------------------------------------------------
String getContentType();
boolean isInheritable();
String getDefId();
ContentFragment getFragmentByFragmentId(String id, boolean nonTemplate);
List getFragmentsByName(String name, boolean nonTemplate);
ContentFragment getNonTemplateRootFragment();
ContentFragment addFragmentReference(String id);
void newSiblingDynamicPage(String pageName, String contentType, String 
layoutName, String pageTitle, String pageShortTitle);
void newSiblingPageTemplate(String templateName, String layoutName, String 
templateTitle, String templateShortTitle);
void newSiblingFragmentDefinition(String definitionName, String defId, String 
portletName, String definitionTitle, String definitionShortTitle);
void updateContent(String contentType, Boolean inheritable);

ContentFragment:
---------------------------------------------------------------------------------
String getRefId();
boolean isTemplate();
void updateRefId(String refId);




> Page Layout/Portal Site components should support requests and rendering of 
> *.tpsml, *.fpsml, and *.dpsml documents
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: JS2-1138
>                 URL: https://issues.apache.org/jira/browse/JS2-1138
>             Project: Jetspeed 2
>          Issue Type: Improvement
>          Components: Profiling/Portal Navigation, PSML
>    Affects Versions: 2.2.1
>         Environment: General base Jetspeed page pipelines.
>            Reporter: Randy Watler
>            Assignee: Randy Watler
>            Priority: Blocker
>             Fix For: 2.2.1
>
>
> In addition to general ability to treat  PSML *.tpsml, *.fpsml, and *.dpsml 
> documents as pages, test cases need to be written for the Page Layout 
> component and the Portal Site tests extended.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to