[
https://jira.jboss.org/jira/browse/GTNPORTAL-702?page=com.atlassian.jira....
]
Julien Viet commented on GTNPORTAL-702:
---------------------------------------
Here is the comment I did on the GateIn dev list a few months ago when it was debated:
"Application registry is a business view of the applications, where applications such
as portlet and gadget are provisioned. Application registry is originally populated from
an XML deployment descriptor in a file configuration, so there is already a mechanism to
populate it. The auto import feature is a development feature that is designed to help
application developer to see his portlets in the composer when editing a layout.
So I'm not sure if we want to keep or remove the auto import feature, but what I am
certain is that we do not want to have *all* applications imported on every startup as it
would be contradictory with the concept of of having an application registry where things
are provisioned. For instance there are certain portlets that you don't want to see in
the application registry when gatein is used in a non development mode.
So we could remove the auto import feature in the future but not for an auto import
mechanism that would auto import any portlets, it would need to be smarter and take in
account development mode and production mode.
At some point I thought about having a specific deployment descriptor (similar to
portlet-instances.xml in JBoss Portal) that would be used to provision portlet instances.
It's an idea that we should think about for a later revision of GateIn. But still it
would be interesting to keep an "import" feature but instead of scoping it at
the global level, it would be scoped at a finer granularity such as the web application
level (that would import portlets from a specified portlet application that do not have an
XML instance deployment descriptor inside).
Another reason is that application registry is also about Gadgets, and today there is no
way to detect the life cycle of a gadget so at some point the gadgets must be
"imported" wether it's done by at boot time by the configuration mentionned
above or by the auto import."
Remove "Import Applications" feature from Administration
category menu
-----------------------------------------------------------------------
Key: GTNPORTAL-702
URL:
https://jira.jboss.org/jira/browse/GTNPORTAL-702
Project: GateIn Portal
Issue Type: Feature Request
Components: User Interface
Affects Versions: 3.0.0-CR01
Reporter: Nicolas Martignole
Priority: Minor
GateIn Portal has an "Import Applications" submenu feature that is used to
import applications the very first time GateIn is used. Julien Viet told me that this is
related to the JCR.
I would suggest to remove this feature, that has to be manually triggered, and let the
Portal adds any valid WAR package at startup-time. This would avoir the need to execute
this task once for all.
When we compare with Liferay 5.2, any valid web application is automatically available in
the "Control Panel" Menu. When an application is not valid, but some of its meta
can be extracted, the Liferay control panel will show the Portlet name grayed out.
As a GateIn Portal user, I'd like to drop my WAR in the webapp folder, reload the
list of available applications, and see all my Portlets, without the need to call this
"Import Applications" feature.
Nicolas
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira