[JBoss JIRA] (GTNPORTAL-2179) NavigationResource Constructor have to init SiteType attribute
by Hai Nguyen (Created) (JIRA)
NavigationResource Constructor have to init SiteType attribute
--------------------------------------------------------------
Key: GTNPORTAL-2179
URL: https://issues.jboss.org/browse/GTNPORTAL-2179
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Hai Nguyen
Priority: Minor
When using this constructor:
{code:xml}
public NavigationResource(String siteName)
{
this(null, siteName, null);
}
{code}
the siteType isn't initialized.
So when using this contructor like here:
{code:xml}
RequestContext ctx = RequestContext.getCurrentInstance();
NodeURL nodeURL = ctx.createURL(NodeURL.TYPE);
NavigationResource resource = new NavigationResource("classic");
return nodeURL.setResource(resource).toString();
{code}
You 'll get a NullPointerException:
{code:xml}
Caused by: java.lang.NullPointerException
at org.exoplatform.web.url.navigation.NodeURL.getParameterValue(NodeURL.java:90)
at org.exoplatform.portal.url.PortalURLContext.render(PortalURLContext.java:135)
at org.exoplatform.web.url.PortalURL.toString(PortalURL.java:307)
{code}
caused by the non intialized siteType attribute.
--
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
12 years, 8 months
[JBoss JIRA] Created: (GTNMGMT-22) Session closed when trying to use autocomplete for export/import commands
by Tomas Kyjovsky (JIRA)
Session closed when trying to use autocomplete for export/import commands
-------------------------------------------------------------------------
Key: GTNMGMT-22
URL: https://issues.jboss.org/browse/GTNMGMT-22
Project: GateIn Management
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: cli
Affects Versions: 1.0.0-Beta04
Environment: EPP-5.2.0.ER01
Reporter: Tomas Kyjovsky
Assignee: Nick Scavelli
Priority: Minor
09:56:22,966 INFO [ChannelSession] Send SSH_MSG_CHANNEL_EOF on channel 0
09:56:22,966 INFO [ChannelSession] Send SSH_MSG_CHANNEL_REQUEST exit-status on channel 0
09:56:22,966 INFO [ChannelSession] Send SSH_MSG_CHANNEL_CLOSE on channel 0
09:56:22,967 ERROR [STDERR] Exception in thread "CRaSH"
09:56:22,967 ERROR [STDERR] java.lang.UnsupportedOperationException: Need to find next argument and use it for completion
09:56:22,967 ERROR [STDERR] at org.crsh.cmdline.matcher.impl.MatcherImpl.getCompletion(MatcherImpl.java:315)
09:56:22,967 ERROR [STDERR] at org.crsh.cmdline.matcher.impl.MatcherImpl.complete(MatcherImpl.java:200)
09:56:22,967 ERROR [STDERR] at org.crsh.command.CRaSHCommand.complete(CRaSHCommand.java:138)
09:56:22,967 ERROR [STDERR] at org.crsh.shell.impl.CRaSH.complete(CRaSH.java:221)
09:56:22,967 ERROR [STDERR] at org.crsh.shell.concurrent.AsyncShell.complete(AsyncShell.java:173)
09:56:22,967 ERROR [STDERR] at org.crsh.Processor$2.execute(Processor.java:247)
09:56:22,967 ERROR [STDERR] at org.crsh.Processor.execute(Processor.java:341)
09:56:22,967 ERROR [STDERR] at org.crsh.Processor.run(Processor.java:142)
09:56:22,967 ERROR [STDERR] at org.crsh.ProcessorIOHandler.handle(ProcessorIOHandler.java:66)
09:56:22,967 ERROR [STDERR] at org.crsh.ssh.term.CRaSHCommand.run(CRaSHCommand.java:69)
09:56:22,967 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619)
09:56:22,968 INFO [ChannelSession] Received SSH_MSG_CHANNEL_CLOSE on channel 0
09:56:22,968 INFO [ServerSession] Closing session
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (GTNMGMT-18) Authentication doesn't work in CLI
by Tomas Kyjovsky (JIRA)
Authentication doesn't work in CLI
----------------------------------
Key: GTNMGMT-18
URL: https://issues.jboss.org/browse/GTNMGMT-18
Project: GateIn Management
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: cli
Affects Versions: 1.0.0-Beta03
Environment: SSH-2.0-OpenSSH_4.3
Reporter: Tomas Kyjovsky
Assignee: Nick Scavelli
Authentication doesn't work in CLI. It seems passords aren't verified, so anyone can login as root with blank password, and even if user isn't logged in as root he can execute "mgmt connect" command and export full portal structure.
----
[tkyjovsk@perf13 ~]$ ssh -p 2000 perf13
tkyjovsk@perf13's password: BLANK_PASSWORD_HERE
______
.~ ~. |`````````, .'. ..'''' | |
| |'''|''''' .''```. .'' |_________|
| | `. .' `. ..' | |
`.______.' | `. .' `. ....'' | | 1.0.0-beta22
Follow and support the project on http://crsh.googlecode.com
GateIn Management CLI running @ perf13.mw.lab.eng.bos.redhat.com
It is Tue Sep 27 15:41:23 EDT 2011 now
% mgmt connect
Successfully connected to gatein management system: [user=root, container='portal', host='perf13.mw.lab.eng.bos.redhat.com/10.16.88.191']
% export mop /home/tkyjovsk/tmp
Export complete ! File location: /home/tkyjovsk/tmp/mop_2011-09-27_15-41-44.zip
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (GTNPORTAL-2174) Use the new ExoCache config instead of adding a new creator
by Hai Nguyen (Created) (JIRA)
Use the new ExoCache config instead of adding a new creator
-----------------------------------------------------------
Key: GTNPORTAL-2174
URL: https://issues.jboss.org/browse/GTNPORTAL-2174
Project: GateIn Portal
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Hai Nguyen
Priority: Minor
Exo JCR 1.14 has added a new Feature that allows us to choose the ExoCache implementation. (https://issues.jboss.org/browse/EXOJCR-1180 for more details)
So no need to define a new ExoCacheCreator( org.exoplatform.commons.cache.SimpleExoCacheCreator ) in order to instantiate org.exoplatform.services.cache.concurrent.ConcurrentFIFOExoCache, you will have simply to choose the type of cache in config, as follows:
<type>org.exoplatform.services.cache.ExoCacheConfigPlugin</type>
<description>add Exo Cache Config</description>
<init-params>
<object-param>
<name>cache.config.MOPSessionManager</name>
<description>The JBoss Cache configuration for the MOP session Manager</description>
<object type="org.exoplatform.services.cache.ExoCacheConfig">
<field name="name">
<string>MOPSessionManager</string>
</field>
<field name="maxSize">
<int>5000</int>
</field>
<field name="liveTime">
<long>600</long>
</field>
<field name="implementation"><string>org.exoplatform.services.cache.concurrent.ConcurrentFIFOExoCache</string></field>
</object>
</object-param>
</init-params>
</component-plugin>
via the implementation field.
--
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
12 years, 8 months