Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "STP/Stardust/KnowledgeBase//Customization/Portal/CustomLaunchPanelUsingPlugin"
(New page: == Extending the Workflow Perspective with a custom launch panel using a portal plugin<br> == === Project Setup<br> === Use a project of type Utility Project and link it into your RAD ...) |
|||
| Line 3: | Line 3: | ||
=== Project Setup<br> === | === Project Setup<br> === | ||
| − | Use a project of type Utility Project and link it into your RAD environment:<br> | + | Use a project of type Utility Project and link it into your RAD environment:<br> <img src="/images/0/0b/ProjectWizardUtilityProject.png" _fck_mw_filename="ProjectWizardUtilityProject.png" alt="Project Wizard - Project Select - Java EE - Utility Project" /><br>In this example the project was named ''exampleCustom''.<br> |
You can use the standard project structure created by eclipse or change it into a maven folder structure. Add the utility project as a J2EE module dependency to your dynamic web project. This way it will automatically be built and included as a jar in the web application's WEB-INF\lib folder. | You can use the standard project structure created by eclipse or change it into a maven folder structure. Add the utility project as a J2EE module dependency to your dynamic web project. This way it will automatically be built and included as a jar in the web application's WEB-INF\lib folder. | ||
| − | + | <img src="/images/2/2c/JavaEEModulDependencies.png" _fck_mw_filename="JavaEEModulDependencies.png" alt="Eclipse Porject Preferences Dynamic Web Project - JavaEE Modul Dependencies" /><br> | |
Create the following folder structure under the project’s source folder:<br> | Create the following folder structure under the project’s source folder:<br> | ||
| Line 17: | Line 17: | ||
Any xhtml file placed into this folder can later be referenced and accessed via | Any xhtml file placed into this folder can later be referenced and accessed via | ||
<pre>/plugins/yourPluginFileName/markupFileName.xhtml</pre> | <pre>/plugins/yourPluginFileName/markupFileName.xhtml</pre> | ||
| − | + | <img src="/images/7/7c/StardustEditExCustomPortalPlugin.png" _fck_mw_filename="StardustEditExCustomPortalPlugin.png" alt="" /> | |
<br> | <br> | ||
| Line 26: | Line 26: | ||
<pre>META-INF\spring\yourPluginName-context.xml | <pre>META-INF\spring\yourPluginName-context.xml | ||
META-INF\spring\yourPluginNameUi-context.xml</pre> | META-INF\spring\yourPluginNameUi-context.xml</pre> | ||
| − | + | <img src="/images/7/70/StardustEditExCustomUi-contextXml.png" _fck_mw_filename="StardustEditExCustomUi-contextXml.png" alt="" /> | |
The backing beans for the custom pages will be decaled in ''yourPuginName-context.xml''.<br>UI extensions to the Infinity Process Platform portal will be declared in ''yourPluginNameUi-context.xml''. | The backing beans for the custom pages will be decaled in ''yourPuginName-context.xml''.<br>UI extensions to the Infinity Process Platform portal will be declared in ''yourPluginNameUi-context.xml''. | ||
Latest revision as of 08:22, 27 October 2011
Contents
Extending the Workflow Perspective with a custom launch panel using a portal plugin
Project Setup
Use a project of type Utility Project and link it into your RAD environment:
<img src="/images/0/0b/ProjectWizardUtilityProject.png" _fck_mw_filename="ProjectWizardUtilityProject.png" alt="Project Wizard - Project Select - Java EE - Utility Project" />
In this example the project was named exampleCustom.
You can use the standard project structure created by eclipse or change it into a maven folder structure. Add the utility project as a J2EE module dependency to your dynamic web project. This way it will automatically be built and included as a jar in the web application's WEB-INF\lib folder.
<img src="/images/2/2c/JavaEEModulDependencies.png" _fck_mw_filename="JavaEEModulDependencies.png" alt="Eclipse Porject Preferences Dynamic Web Project - JavaEE Modul Dependencies" />
Create the following folder structure under the project’s source folder:
META-INF MEAT-INF\spring (for spring configuration files) MEAT-INF\xhtml\yourPluginName (for markup files used by your plugin)
Then create a file yourPluginFileName.portal-plugin. The file contents should be the relative path to your plugin’s markup folder starting from the src folder:
/META-INF/xhtml/yourPluginName/
Any xhtml file placed into this folder can later be referenced and accessed via
/plugins/yourPluginFileName/markupFileName.xhtml
<img src="/images/7/7c/StardustEditExCustomPortalPlugin.png" _fck_mw_filename="StardustEditExCustomPortalPlugin.png" alt="" />
Spring Configuration
Create two spring configuration files:
META-INF\spring\yourPluginName-context.xml META-INF\spring\yourPluginNameUi-context.xml
<img src="/images/7/70/StardustEditExCustomUi-contextXml.png" _fck_mw_filename="StardustEditExCustomUi-contextXml.png" alt="" />
The backing beans for the custom pages will be decaled in yourPuginName-context.xml.
UI extensions to the Infinity Process Platform portal will be declared in yourPluginNameUi-context.xml.
By default the contextConfigLocation parameters in the IPP web application is configured to include META-INF/spring/*-context.xml. Therefore these context files will be added to the spring context automatically and no configuration changes should be required.
JSF markup, backing beans and message bundle
TBD
Linking Extensions into the Portal
TBD