[JBoss JIRA] Created: (GTNPORTAL-590) Portal extension deployment issues
by Matt Wringe (JIRA)
Portal extension deployment issues
----------------------------------
Key: GTNPORTAL-590
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-590
Project: GateIn Portal
Issue Type: Bug
Reporter: Matt Wringe
Portal extensions are not working very well right now with GateIn with regards to how the extensions are deployed or redeployed.
Starting the Server without the Extension:
-If you start the server from a clean state (ie the server has not run before) without gatein-sample-extension.ear, then when accessing the portal it will just be text (no images, no css, ...)
-If you try and deploy the extension while the server is running, then it will fail with a bunch of errors about the portal already being intialized
-if you stop the server and restart it again, then the portal will render properly but the extra pages the extensions was suppose to create will be missing
-in order to get the pages the extension was suppose to add, you will need to delete the data directory and restart the server. You will also need to do this if you want to modify what the extension adds.
--
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
12 years, 5 months
[JBoss JIRA] Created: (GTNPORTAL-740) main portal should contain only mandatory services
by Benjamin Paillereau (JIRA)
main portal should contain only mandatory services
--------------------------------------------------
Key: GTNPORTAL-740
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-740
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Packaging
Affects Versions: 3.0.0-CR01
Reporter: Benjamin Paillereau
Take eXo WCM on top of GateIn. To summarize, we add 2 war files :
- wcm-extensions : all the "core services" we need
- ecmdemo : a portal instance with its own realm and rest
ecmdemo creates two sites with some public navigation, group navigation, users, contents, etc
With GateIn, we have some kind of navigation, membership, default portal templates,default page templates, default portal (/portal) and we don't need this but worse than that you don't want it.
GateIn should provide a basic portal war with mandatory features only, all the other feature we need te redifined in sample sites must be bundled in another war like the other products do.
--
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
12 years, 5 months
[JBoss JIRA] Created: (GTNPORTAL-1431) UIPortlet management of events, PRPs and mode information is sub-optimal
by Chris Laprun (JIRA)
UIPortlet management of events, PRPs and mode information is sub-optimal
------------------------------------------------------------------------
Key: GTNPORTAL-1431
URL: https://jira.jboss.org/browse/GTNPORTAL-1431
Project: GateIn Portal
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: PC integration
Affects Versions: 3.1.0-GA
Reporter: Chris Laprun
Assignee: Matt Wringe
Priority: Minor
Fix For: 3.2.0-GA
Attachments: uiportlet.patch
Attached is a patch that removes unneeded code and cleans-up processing. However, some of the things that were done didn't quite make sense (in particular management of the "config" mode, see inline comments in the patch) so I'd like someone who knows more about the UIPortlet codebase than me to check my modifications. Note that in testing WSRP2 I didn't see any problems with that patch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] Created: (GTNPORTAL-1388) Determine navigation target before entering webui layer
by Julien Viet (JIRA)
Determine navigation target before entering webui layer
-------------------------------------------------------
Key: GTNPORTAL-1388
URL: https://jira.jboss.org/browse/GTNPORTAL-1388
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Julien Viet
Assignee: Trong Tran
Fix For: 3.2.0-GA
The PortalRequestContext when it is created should fully determine the navigation target decomposed into:
- target site type
- target site name
- target navigation path, the value being a normalized path that starts with a /
Examples:
/private/classic -> "portal" site type, "classic" site name and "/" target navigation path
/private/classic/home -> "portal" site type, "classic" site name and "/home" target navigation path
/public/classic/ -> "portal" site type, "classic" site name and "/" target navigation path
/private/classic/Tab_0 -> "user" site type, "root" site name (for user root") and /Tab_0 navigation path
/private/classic/administration/registry -> "group" site type, "/platform/administrators" site name and "/administration/registry" navigation path
So those values are determined before the request happens and then can be used with the webui code to generate potential navigation events
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months