[JBoss JIRA] Created: (GTNPORTAL-971) Various [STDOUT] on console
by Arthur Peltier (JIRA)
Various [STDOUT] on console
---------------------------
Key: GTNPORTAL-971
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-971
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: Ubuntu 9.10, Java(TM) SE Runtime Environment (build 1.6.0_16-b01), JBoss AS
Reporter: Arthur Peltier
Priority: Optional
After the server started there are [STDOUT] outputs on console: 15:21:51,986 INFO [STDOUT] Creating a new session of the 'sample-ext' 15:22:51,163 INFO [STDOUT] Destroying a session of the 'sample-ext' 15:22:51,196 INFO [STDOUT] Creating a new session of the 'sample-ext' It wold be better to use logger for output instead of System.out.println();
--
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-957) Provide an administration feature to allow or not the addition of remote gadget by end user on its dashboard
by Tugdual Grall (JIRA)
Provide an administration feature to allow or not the addition of remote gadget by end user on its dashboard
------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-957
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-957
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: User Interface
Affects Versions: 3.0.0-GA
Reporter: Tugdual Grall
In GTN 3.0 any user can on its dashboard add a remote gadget using the module.xml URL.
This is a very cool feature, but we should provide a way to limit this feature.
Basic features:
1- by default we keep the current behavior
2- the improved feature could be the following:
- in the application registry we add a new screen to configure the dashboard behavior (this must be global to all portal instance)
- provide a selector to select who can add gadget on their dashboard "Any Users" or "a list of membership"
This is safer for production environment on intranet
--
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-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