[
https://issues.jboss.org/browse/GTNPORTAL-315?page=com.atlassian.jira.plu...
]
Antoine Herzog commented on GTNPORTAL-315:
------------------------------------------
I don't understand why this is out of date ?
Does the deployement (and re-deployement) of the artifacts of the "Extension
Mechanism" can be hot ?
You know, the feature of hot deployement of the portal definition (pages, navigation,...)
that we had with JBoss Portal, before the reshape with Exo portal. This was a very
important feature that is not anymore available.
For development of portals in companies, getting this feature back would be a great dev
productivity jump.
Tug (of Exo) told me a few months ago that the feature was under thinking, even if not
sure it could be done as full hot redeployment.
What could be done is :
- hot redeployement of the EAR, for update of the page and navigation definition (and
locale resource bundle, etc...)
- this is for an existing portal only, yet deployed
What could not be done is :
- not possible to hot redeploy to add or suppress a portal container or a portal (site)
definition
This would be great.
The need is hot redeployement for Page/Nav development (with xml definition) and the
tuning of all this.
Creating a new portal container or portal (site) can be done with stop and restart of the
server.
This was Tug say,... if you want to check about what's on for this feature.
********
This feature is related with the update of the page/nav definition in the JCR, from the
XML definition.
As far as I know, this can be done only with suppression of the JCR content, and
recreation,... for the time being.
Did I missed something about this ?
Thanks for all the dev of the product.
Antoine
www.sysemo.com
Make sample-extension.ear and sample-portal.ear and the like hot
re-deployable
------------------------------------------------------------------------------
Key: GTNPORTAL-315
URL:
https://issues.jboss.org/browse/GTNPORTAL-315
Project: GateIn Portal
Issue Type: Feature Request
Reporter: Thomas Heute
Assignee: Marko Strukelj
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira