[JBoss JIRA] Created: (GTNPORTAL-1976) Invalid groupsites created in JCR with clean DB.
by Nick Scavelli (JIRA)
Invalid groupsites created in JCR with clean DB.
------------------------------------------------
Key: GTNPORTAL-1976
URL: https://issues.jboss.org/browse/GTNPORTAL-1976
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JCR integration
Affects Versions: 3.2.0-M02
Reporter: Nick Scavelli
On fresh startup of gatein, I noticed that JCR has some invalid groupsite entries: platform/users and platform/administrators, instead to /platform/users and /platform/administrators. (no leading '/')
crash ls output:
% ls
/production/mop:workspace/mop:groupsites
+-properties
| +-jcr:primaryType: mop:groupsites
| +-jcr:uuid: '722b7f497f0000014d0dcfaddc73a818'
+-children
| +-/production/mop:workspace/mop:groupsites/mop:%03platform%03guests
| +-/production/mop:workspace/mop:groupsites/mop:%03organization%03management%03executive-board
| +-/production/mop:workspace/mop:groupsites/mop:%03platform%03administrators
| +-/production/mop:workspace/mop:groupsites/mop:%03platform%03users
| +-/production/mop:workspace/mop:groupsites/mop:platform%03users
| +-/production/mop:workspace/mop:groupsites/mop:platform%03administrators
| +-/production/mop:workspace/mop:groupsites/mop:%03platform
| +-/production/mop:workspace/mop:groupsites/mop:%03organization
| +-/production/mop:workspace/mop:groupsites/mop:%03organization%03management
| +-/production/mop:workspace/mop:groupsites/mop:%03organization%03management%03human-resources
| +-/production/mop:workspace/mop:groupsites/mop:%03organization%03communication
| +-/production/mop:workspace/mop:groupsites/mop:%03organization%03communication%03marketing
| +-/production/mop:workspace/mop:groupsites/mop:%03organization%03communication%03press-and-media
| +-/production/mop:workspace/mop:groupsites/mop:%03organization%03operations
| +-/production/mop:workspace/mop:groupsites/mop:%03organization%03operations%03sales
| +-/production/mop:workspace/mop:groupsites/mop:%03organization%03operations%03finances
| +-/production/mop:workspace/mop:groupsites/mop:%03customers
| +-/production/mop:workspace/mop:groupsites/mop:%03partners
I'm not sure how the two w/out the '/' are being created, but it's causing issues when listing group sites.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (GTNPORTAL-1908) NPE when request to portal which configured to use SSO integration
by Khoi Nguyen (JIRA)
NPE when request to portal which configured to use SSO integration
------------------------------------------------------------------
Key: GTNPORTAL-1908
URL: https://issues.jboss.org/browse/GTNPORTAL-1908
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security
Reporter: Khoi Nguyen
Normally, if GateIn is integrated with any SSO server (CAS, JOSSO, OpenSSO), we will get the login screen delivered from SSO Server when asking for http://localhost:8080/portal/private/classic.
Unfortunately, if there is the first request to portal in private mode, I'd get an exception such:
{code}
Caused by: javax.servlet.ServletException: java.lang.NullPointerException
at org.gatein.sso.agent.GenericSSOAgent.doGet(GenericSSOAgent.java:88)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at org.exoplatform.container.web.AbstractHttpServlet.onService(AbstractHttpServlet.java:183)
at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.exoplatform.portal.application.localization.LocalizationFilter.doFilter(LocalizationFilter.java:179)
... 18 more
Caused by: java.lang.NullPointerException
at org.gatein.sso.agent.opensso.OpenSSOAgent.validateTicket(OpenSSOAgent.java:73)
at org.gatein.sso.agent.GenericSSOAgent.processSSOToken(GenericSSOAgent.java:120)
at org.gatein.sso.agent.GenericSSOAgent.doGet(GenericSSOAgent.java:73)
... 25 more
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (GTNPORTAL-1968) Remote portlet only works for the default portal context but doens't work with extension.
by Gary Hu (JIRA)
Remote portlet only works for the default portal context but doens't work with extension.
-----------------------------------------------------------------------------------------
Key: GTNPORTAL-1968
URL: https://issues.jboss.org/browse/GTNPORTAL-1968
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Gary Hu
If I create a WSRP consumer via the WSRP configuration portlet, the WSRP portlets don't show under the "REMOTE" tab or "wsrp" application type when adding portlet to categories if Site Publisher is deployed.
The same issue doesn't occur if the Site Publisher is not deployed.
The following steps could reproduce the issue.
1) login ecmdemo as "john"
2) create a WSRP consumer via the WSRP configuration portlet. I'm using the NetUnity test public WSDL http://www.netunitysoftware.com/wsrp2interop/wsrpproducer.asmx?WSDL. If you see errors "faultCode=OTHER_ERROR: Inconsistent NS in port bindings" using the url above you can try to change it to
http://www.netunitysoftware.com/wsrp2interop/wsrpproducer.asmx?Operation=...
you are likely to see a different error "Refresh failed (probably because the registration information was not valid). ". Then you change the url back to http://www.netunitysoftware.com/wsrp2interop/wsrpproducer.asmx?WSDL (click the Refresh and Save a couple of times if it doesn't work) you should be able to successfully register the WSRP producer.
3) go to Adminstration->Application Registry->Portlet->REMOTE, the WSRP portlets are not showing there.
If you click "Categories", and under "CATEGORIES", you select any category, for example "Web", can click "+" to add a portlet. And then select "wsrp" as the Application Type and click "Add" button, it shows empty.
If I go through the same steps by logging in "portal" as root, you can see the WSRP portlets are showing up.
The further research shows that this is a limitation in the current EPP 5 product.
This limitation is caused by hard-codes in EPP-5.1.x source code in file component/wsrp/src/main/java/org/gatein/portal/wsrp/WSRPServiceIntegration.java:
...
public WSRPServiceIntegration(ExoContainerContext context, InitParams params, ConfigurationManager configurationManager,
ExoKernelIntegration pc, NodeHierarchyCreator nhc) throws Exception
{
// IMPORTANT: even though PC ExoKernelIntegration and NodeHierarchyCreator is not used anywhere in the code, it's still needed for pico
// to properly make sure that this service is started after the PC one. Yes, Pico is crap. :/
// todo: we currently only allow the service to go through initialization if we are running in the default portal
// as this service is not meant to work with extensions yet...
String consumersConfigLocation;
if ("portal".equals(context.getName()))
{
if (params != null)
{
producerConfigLocation = params.getValueParam(PRODUCER_CONFIG_LOCATION).getValue();
consumersConfigLocation = params.getValueParam(CONSUMERS_CONFIG_LOCATION).getValue();
}
else
{
throw new IllegalArgumentException("Improperly configured service: missing values for "
+ PRODUCER_CONFIG_LOCATION + "and " + CONSUMERS_CONFIG_LOCATION);
}
...
Can you add a new feature that makes the remote portlet also work with the extension?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (GTNPORTAL-1001) GateIn+Opera: problem with script
by Benjamin Seyinbour (JIRA)
GateIn+Opera: problem with script
---------------------------------
Key: GTNPORTAL-1001
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1001
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: User Interface
Affects Versions: 3.0.0-GA
Environment: Linux [Centos 5.4] Opera[version:10.10) Java [version 1.6.0_16]
Reporter: Benjamin Seyinbour
Fix For: 3.0.0-GA
I keep getting the following error in Opera whenever I click a command button or link in GateIn :
<localhost>
[Error:
name: TypeError
message: Statement on line 221: Type mismatch (usually non-object value supplied where object required)
]
When this happens the top half of the screen turns black and I can't see GateIn .
--
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, 11 months
[JBoss JIRA] Created: (GTNPC-70) Behavioral change: New portlet metadata parser silently discards unexpected elements.
by Chris Laprun (JIRA)
Behavioral change: New portlet metadata parser silently discards unexpected elements.
-------------------------------------------------------------------------------------
Key: GTNPC-70
URL: https://issues.jboss.org/browse/GTNPC-70
Project: GateIn Portlet Container
Issue Type: Enhancement
Components: API, Documentation
Affects Versions: 2.3.0-Beta05
Reporter: Chris Laprun
Fix For: 2.3.0-GA
portlet.xml parsing was previously very tolerant with respect to out-of-order elements (XSD kinda sucks for this), thus silently allowing portlet.xml that were not strictly valid according to portlet-app_2_0.xsd. The new staxnav parser, on the other hand, is a lot stricter (while still not validating) meaning that it will silently discard unexpected (in particular, out-of-order) elements, resulting in portlet metadata that previously was imported, now being silently discarded. While this is not strictly a bug (after all, the portlet.xml that result in errors are invalid), this is a rather big behavioral change compounded with the fact that the new parser silently discards information resulting in errors showing up much later than the parsing process and without any informational context that the user could use to fix the issue... :(
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (GTNPORTAL-1311) Split the UIPortalNavigation class into two classes used in UINavigationPortlet and UISitemapPortlet respectively
by Minh Hoang TO (JIRA)
Split the UIPortalNavigation class into two classes used in UINavigationPortlet and UISitemapPortlet respectively
-----------------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-1311
URL: https://jira.jboss.org/browse/GTNPORTAL-1311
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Minh Hoang TO
Assignee: Minh Hoang TO
In legacy code, both UINavigationPortlet and UISitemapPortlet use UIPortalNavigation to handle the underlying navigations. That was logical in the past as before navigation portlet showed all PageNavigations as UISitemap did.
Now, the methods declared in UIPortalNavigaton belongs to two independent groups, one group consists of methods used in sitemap portlet. The other consists of methods used in navigation portlet.
On the other hand, using UIPortalNavigation in sitemap portlet requires storing template name in the PortletPreference.
Hence, it 's better to split UIPortalNavigation into two classes now
--
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, 11 months