summaryrefslogtreecommitdiffstats
path: root/documentation/portal/portal-deployment.asciidoc
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/portal/portal-deployment.asciidoc')
-rw-r--r--documentation/portal/portal-deployment.asciidoc7
1 files changed, 4 insertions, 3 deletions
diff --git a/documentation/portal/portal-deployment.asciidoc b/documentation/portal/portal-deployment.asciidoc
index 7350fb0536..fec0fd4793 100644
--- a/documentation/portal/portal-deployment.asciidoc
+++ b/documentation/portal/portal-deployment.asciidoc
@@ -7,6 +7,10 @@ layout: page
[[portal.deployment]]
= Deploying to a Portal
+For OSGi portlets in Liferay 7, see
+<<dummy/../../../framework/portal/portal-osgi#portal.osgi.portlet,"Publishing a Portlet With OSGi">>.
+The text below applies mostly to non-OSGi portlets.
+
To deploy a portlet WAR in a portal, you need to provide a
[filename]#portlet.xml# descriptor specified in the Java Portlet API 2.0
standard (JSR-286). In addition, you may need to include possible portal vendor
@@ -33,9 +37,6 @@ changes to the UI itself, but only the following:
* Vaadin libraries installed to portal (optional)
* Portal configuration settings (optional)
-The Vaadin Plugin for Eclipse creates these files for you, when you create a
-portlet project as described in <<portal-eclipse#portal.eclipse,"Creating a Generic Portlet in Eclipse">>.
-
Installing the widget set and themes to the portal is required for running two or more Vaadin portlets simultaneously in a single portal page.
As this situation occurs quite easily, we recommend installing them in any case.
Instructions for Liferay are given in <<portal-liferay#portal.liferay,"Developing Vaadin Portlets for Liferay">> and the procedure is similar for other portals.