Search: concept
Last modified by Vincent Massol on 2014/10/21
Refine your search
Select a category and activate filters on the current results
Result type
-
Document
3
Location
-
Documentation
2
-
Drafts
1
Creator
Creation date
- Sort by:
- Relevance
Results 1 - 3 of 3
Page
1
Portlet Integration
Located in
- Rendered document content
The Java Portlet Specification allows coordination on the UI layer with different means, such as events, application sessions, and public render parameters, in order to provide a deep and seamless integration between the different services. Portlet Concepts a portal is a web based application that commonly provides personalization, authentication, content aggregation from different sources and hosts the presentation layer of information systems a portlet is an application that provides a specific piece of content (information or service) to be included as part of a portal page web clients interact with portlets via a request/response paradigm implemented by the portal a portlet container runs portlets and provides them with the required runtime environment manages the life cycle of portlets provides persistent storage for portlet preferences a portlet mode indicates the function a portlet is performing in the render method standard portlet modes are: view, edit and help view: generate markup reflecting the current state of the portlet edit: customize the behavior of the portlet help: provide help information about the portlet a portlet window is the visual component used to display the content generated by a portlet within portal pages a window state is an indicator of the amount of portal page space that will be assigned to the content generated by a portlet via the render method possible window states are: normal, maximized and minimized Portlet Life Cycle The life cycle of a portlet is expressed through the init, processAction, render and destroy methods of the Portlet interface.
- Raw document content
The Java Portlet Specification allows coordination on the UI layer with different means, such as events, application sessions, and public render parameters, in order to provide a deep and seamless integration between the different services. == Portlet Concepts == image:portalPageCreation.png * a **portal** is a web based application that commonly provides personalization, authentication, content aggregation from different sources and hosts the presentation layer of information systems * a **portlet** is an application that provides a specific piece of content (information or service) to be included as part of a portal page ** web clients interact with portlets via a request/response paradigm implemented by the portal * a **portlet container** runs portlets and provides them with the required runtime environment ** manages the life cycle of portlets ** provides persistent storage for portlet preferences image:elementsOfAPortalPage.png * a **portlet mode** indicates the function a portlet is performing in the render method ** standard portlet modes are: view, edit and help ** view: generate markup reflecting the current state of the portlet ** edit: customize the behavior of the portlet ** help: provide help information about the portlet * a **portlet window** is the visual component used to display the content generated by a portlet within portal pages * a **window state** is an indicator of the amount of portal page space that will be assigned to the content generated by a portlet via the render method ** possible window states are: normal, maximized and minimized == Portlet Life Cycle == The life cycle of a portlet is expressed through the ##init##, ##processAction##, ##render## and ##destroy## methods of the ##Portlet## interface.
Creating a FAQ Application (Manual)
Located in
- Rendered document content
In addition, this tutorial will introduce the concepts of Authoring Templates and Page Design Sheets, patterns that you will find particularly useful in creating XWiki applications.
…If you previously chose to use a "Custom creation form" for creating new FAQ entries, follow these steps: Go to FAQ.WebHome Below the "Add a new question" header, enter a question (which will also be used as the document title) in the Document field Click Create this FAQ You can then enter your question in longer form using the Question field on the template, like this: Click Save & View and then you will see the newly created document, like this: Go back to the FAQ.WebHome page (you can use the breadcrumbs) to see the list of existing questions Conclusion This tutorial has taught you how to use the Class Wizard app and it has detailed the concepts of classes, objects and properties and introduced the authoring templates and page design sheets.
…You can use these basic concepts to build custom applications at the document or presentation layer of XWiki without having to compile or deploy code.
- Raw document content
In addition, this tutorial will introduce the concepts of Authoring Templates and Page Design Sheets, patterns that you will find particularly useful in creating XWiki applications.
…If you previously chose to use a "Custom creation form" for creating new FAQ entries, follow these steps: * Go to ##FAQ.WebHome## * Below the "Add a new question" header, enter a question (which will also be used as the document title) in the //Document// field * Click //Create this FAQ// * You can then enter your question in longer form using the //Question// field on the template, like this:((( {{image reference="FAQSheetEdit.PNG"/}} ))) * Click //Save & View// and then you will see the newly created document, like this:((( {{image reference="FAQSheetView.PNG"/}} ))) * Go back to the ##FAQ.WebHome## page (you can use the breadcrumbs) to see the list of existing questions((( {{image reference="FAQsWithEntry.png"/}} ))) = Conclusion = This tutorial has taught you how to use the Class Wizard app and it has detailed the concepts of classes, objects and properties and introduced the authoring templates and page design sheets.
…You can use these basic concepts to build custom applications at the document or presentation layer of XWiki without having to compile or deploy code.
Data Model
Located in
- Rendered document content
XWiki Classes, Objects, and Properties If you are familiar with object oriented programming, you understand the concept of classes, properties, and objects. The presentation level data model that XWiki exposes is much the same.
- Raw document content
= XWiki Classes, Objects, and Properties = If you are familiar with object oriented programming, you understand the concept of classes, properties, and objects. The presentation level data model that XWiki exposes is much the same
Page
1
RSS feed for search on [concept]