September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBPORTAL-467) Login page needs to use the theme of the requested portal

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-467?page=all ] Julien Viet updated JBPORTAL-467: --------------------------------- Fix Version/s: 2.6.Alpha1 (was: 2.6 Final) > Login page needs to use the theme of the requested portal > --------------------------------------------------------- > > Key: JBPORTAL-467 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-467 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.2 Final > Reporter: Martin Holzner > Fix For: 2.6.Alpha1 > > > The Login.jsp that the web.xml's form login points to is in the portal-server.war. > A call to this jsp does not go through any of the stacks in the portal core, and hence there is no portal or page object available to determine the currently set property for the selected theme. As a result, the Login jsp cannot be styled in synch with the rest of the portal. > In the context of having a synchronized look and feel throughout a portal, the login needs to be able to select the same theme as the portal that was requested, so that the login fits seemlessly into the UI flow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-767) ERROR [org.apache.myfaces.portlet.MyFacesGenericPortlet]

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-767?page=all ] Julien Viet updated JBPORTAL-767: --------------------------------- Fix Version/s: 2.6.Alpha1 (was: 2.6 Final) > ERROR [org.apache.myfaces.portlet.MyFacesGenericPortlet] > -------------------------------------------------------- > > Key: JBPORTAL-767 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-767 > Project: JBoss Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Portal Portlet > Affects Versions: 2.4 Final > Environment: Mac OS X, jboss-portal-2.2.1RC2-bundled > Reporter: Leonard Sitongia > Fix For: 2.6.Alpha1 > > > (I'm using jboss-portal-2.2.1RC2-bundled, but I'm building and deploying 2.4 from CVS into it.) > I've used management to create a new page (tab) at the top level, same as default. I add a few portlets to that, including navigation, user and the CMS content one. I remove the CMS content one. Thereafter, when I use management to enter the default portal (by clicking on "default" in the management portlet's navigation tree on the left), I get an exception, and the management portlet is not rendered on the page. > 2006-03-22 08:26:57,497 ERROR [org.apache.myfaces.portlet.MyFacesGenericPortlet] > The portlet threw an exception > javax.portlet.PortletException: /WEB-INF/jsp/management/index.xhtml @100,58 rend > ered="#{!empty node.children}": org.jboss.portal.core.portlet.management.LazyPor > talObjectTreeNode > at org.apache.myfaces.portlet.MyFacesGenericPortlet.handleExceptionFromL > ifecycle(MyFacesGenericPortlet.java:254) > at org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesG > enericPortlet.java:400) > at org.apache.myfaces.portlet.MyFacesGenericPortlet.doView(MyFacesGeneri > cPortlet.java:266) > at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:167) > at javax.portlet.GenericPortlet.render(GenericPortlet.java:407) > at org.jboss.portal.portlet.PortletContainer.invokeRender(PortletContain > er.java:552) > at org.jboss.portal.portlet.PortletContainer.dispatch(PortletContainer.j > ava:464) > at org.jboss.portal.server.app.ComponentInvocation.dispatch(ComponentInv > ocation.java:79) > at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.j > ava:142) > ... > Thanks, > ==Leonard -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-635) Portlet Container tests

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-635?page=all ] Julien Viet updated JBPORTAL-635: --------------------------------- Fix Version/s: 2.6.Alpha1 (was: 2.6 Final) > Portlet Container tests > ----------------------- > > Key: JBPORTAL-635 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-635 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Portlet > Affects Versions: 2.6 Final > Reporter: Boleslaw Dawidowicz > Assigned To: Boleslaw Dawidowicz > Fix For: 2.6.Alpha1 > > Time Spent: 3 days, 7 hours, 30 minutes > > Implement full range of tests for portlet container > - TCK Assertions from Portlet Specification > - Additional test based on portlet specification to cover any specific behavior of container -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-528) Management portlet creating inaccessible instance with empty name field

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-528?page=all ] Julien Viet updated JBPORTAL-528: --------------------------------- Fix Version/s: 2.6.Alpha1 (was: 2.6 Final) > Management portlet creating inaccessible instance with empty name field > ----------------------------------------------------------------------- > > Key: JBPORTAL-528 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-528 > Project: JBoss Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2 Final > Reporter: Boleslaw Dawidowicz > Assigned To: Julien Viet > Priority: Minor > Fix For: 2.6.Alpha1 > > > as in forum post: > "From the management portlet (page view), I clicked the button "Add instance" without entering anything in the text field. It created a blank portlet window. Since it has no names, there are no links associated with it. As a result, I can't delete it." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-435) Request dumper interceptor

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-435?page=all ] Julien Viet updated JBPORTAL-435: --------------------------------- Fix Version/s: 2.6.Alpha1 (was: 2.6 Final) > Request dumper interceptor > -------------------------- > > Key: JBPORTAL-435 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-435 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Server > Reporter: Julien Viet > Priority: Optional > Fix For: 2.6.Alpha1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Ala tomcat : allows to see what parameters a portlet receive -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-847) Identify common conversion methods (from Set<Mode> to String[] for ex) and put them in a utility class

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-847?page=all ] Julien Viet updated JBPORTAL-847: --------------------------------- Fix Version/s: 2.6.Alpha1 (was: 2.6 Final) > Identify common conversion methods (from Set<Mode> to String[] for ex) and put them in a utility class > ------------------------------------------------------------------------------------------------------ > > Key: JBPORTAL-847 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-847 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.4 Final > Reporter: Chris Laprun > Assigned To: Chris Laprun > Priority: Optional > Fix For: 2.6.Alpha1 > > > There are several similar versions of such code. Try to find some time and gather all this code in a single spot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-372) Basic Publish Approval Workflow

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-372?page=all ] Julien Viet updated JBPORTAL-372: --------------------------------- Fix Version/s: 2.6.Alpha1 (was: 2.6 Final) > Basic Publish Approval Workflow > ------------------------------- > > Key: JBPORTAL-372 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-372 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal CMS > Affects Versions: 2.6 Final > Reporter: James Williams > Assigned To: Roy Russo > Priority: Minor > Fix For: 2.6.Alpha1 > > > Optional feature which mandates that content changes must flow through a simple approval process that involves a Publisher and one or more Managers. Once the publisher makes a content change an email approval request should be sent to the manager list. The content change will not be made available to readers until all Managers approve the change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-857) Deal with non standard Locales better

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-857?page=all ] Julien Viet updated JBPORTAL-857: --------------------------------- Fix Version/s: 2.6.Alpha1 (was: 2.6 Final) > Deal with non standard Locales better > ------------------------------------- > > Key: JBPORTAL-857 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-857 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.4 Final > Reporter: Chris Laprun > Assigned To: Chris Laprun > Priority: Minor > Fix For: 2.6.Alpha1 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > Per the WSRP Spec regarding UnsupportedLocale fault: > The Portlet does not support generating markup for the requested locale. Since the Portlet is not required to generate markup in the requested locale, a Portlet returning this fault message is indicating that it processes locales in a stricter manner and has no markup for the requested locales. The Consumer can treat this as a specialization of the OperationFailed fault message and does not have to retry getting the markup in other locales. > Currently, LocaleInfo throws an IllegalArgumentException if the locale is not standard which gets wrapped into an OperationFailedFault at the handler level. We should deal with locale errors better and maybe be more lenient as to what we accept. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-466) JBossRenderRequest needs to provide access to the current PortalTheme

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-466?page=all ] Julien Viet updated JBPORTAL-466: --------------------------------- Fix Version/s: 2.6.Alpha1 (was: 2.6 Final) > JBossRenderRequest needs to provide access to the current PortalTheme > --------------------------------------------------------------------- > > Key: JBPORTAL-466 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-466 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.2 Final > Reporter: Martin Holzner > Fix For: 2.6.Alpha1 > > > This is a feature that Roy needs in one of the CM portlets. > There is a temp fix for this already in the RenderPageCommand , but it is a hack. It needs to be revisited! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-637) Portlet Container test cases beyond "PLT.F TCK Assertions"

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-637?page=all ] Julien Viet updated JBPORTAL-637: --------------------------------- Fix Version/s: 2.6.Alpha1 (was: 2.6 Final) > Portlet Container test cases beyond "PLT.F TCK Assertions" > ---------------------------------------------------------- > > Key: JBPORTAL-637 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-637 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Portlet > Affects Versions: 2.6 Final > Reporter: Boleslaw Dawidowicz > Assigned To: Boleslaw Dawidowicz > Fix For: 2.6.Alpha1 > > Time Spent: 3 hours > > Implement portlet container test cases which are not in scope of Portlet Specification TCK Assertions. > So any specific test cases which don't belong to http://jira.jboss.com/jira/browse/JBPORTAL-636 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2006