January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-510) RuleBase node type

by Michael Neale (JIRA)

RuleBase node type ------------------ Key: JBRULES-510 URL: http://jira.jboss.com/jira/browse/JBRULES-510 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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

19 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-491) add document node type

by Michael Neale (JIRA)

add document node type ---------------------- Key: JBRULES-491 URL: http://jira.jboss.com/jira/browse/JBRULES-491 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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

19 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-405) add support for searching

by Michael Neale (JIRA)

add support for searching ------------------------- Key: JBRULES-405 URL: http://jira.jboss.com/jira/browse/JBRULES-405 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale Priority: Minor Generic search -- 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

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-530) Null Pointer Exception in MyFacesGenericPortlet

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-530?page=all ] Julien Viet resolved JBPORTAL-530. ---------------------------------- Resolution: Won't Fix > Null Pointer Exception in MyFacesGenericPortlet > ----------------------------------------------- > > Key: JBPORTAL-530 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-530 > Project: JBoss Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Jboss 4.0.3 SP1 - portal 2.0.1 RC3 > Reporter: Stefan Tausendpfund > Priority: Minor > Fix For: 2.6.Beta1 > > Attachments: DuplicatePortletTestWeb.tgz > > > Hello, > the initial post is from the Jboss portal forum. > I repost it to attach a sample application showing this error. > <snip> > Hello, > we created an portal application on JBoss Server 4.0.3SP1 with portal 2.0.1RC3 using myfaces MyFacesGenericPortlet. We have several pages and several portlets in one page. One portlet is present in all pages. If I make an action on this portlet (portletwindow0) and switch the page (portletwindow1) i get an NPE in the facesRender method of the MyFacesGenericPortlet. > The lookup of the faces context with > ServletFacesContextImpl facesContext = (ServletFacesContextImpl)request. > getPortletSession(). > getAttribute(CURRENT_FACES_CONTEXT); > returns a null object and the following statement > if (facesContext.getResponseComplete()) return; > fails. > On first entry of doView the getAttribure looks for an Attribute: > javax.portlet.p..<portletwindow0>?org.apache.myfaces.portlet.MyFacesGenericPortlet.CURRENT_FACES_CONTEXT > After switching the page it looks for > javax.portlet.p..<portletwindow1>?org.apache.myfaces.portlet.MyFacesGenericPortlet.CURRENT_FACES_CONTEXT > but the facescontext is still with the key window0 in the session. > Using the same window name in different pages for the same portlet leeds to a portal error. > <snap> > best regards > Stefan Tausendpfund -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-530) Null Pointer Exception in MyFacesGenericPortlet

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-530?page=all ] Julien Viet updated JBPORTAL-530: --------------------------------- Fix Version/s: 2.6.Beta1 (was: 2.6.Alpha1) > Null Pointer Exception in MyFacesGenericPortlet > ----------------------------------------------- > > Key: JBPORTAL-530 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-530 > Project: JBoss Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Jboss 4.0.3 SP1 - portal 2.0.1 RC3 > Reporter: Stefan Tausendpfund > Priority: Minor > Fix For: 2.6.Beta1 > > Attachments: DuplicatePortletTestWeb.tgz > > > Hello, > the initial post is from the Jboss portal forum. > I repost it to attach a sample application showing this error. > <snip> > Hello, > we created an portal application on JBoss Server 4.0.3SP1 with portal 2.0.1RC3 using myfaces MyFacesGenericPortlet. We have several pages and several portlets in one page. One portlet is present in all pages. If I make an action on this portlet (portletwindow0) and switch the page (portletwindow1) i get an NPE in the facesRender method of the MyFacesGenericPortlet. > The lookup of the faces context with > ServletFacesContextImpl facesContext = (ServletFacesContextImpl)request. > getPortletSession(). > getAttribute(CURRENT_FACES_CONTEXT); > returns a null object and the following statement > if (facesContext.getResponseComplete()) return; > fails. > On first entry of doView the getAttribure looks for an Attribute: > javax.portlet.p..<portletwindow0>?org.apache.myfaces.portlet.MyFacesGenericPortlet.CURRENT_FACES_CONTEXT > After switching the page it looks for > javax.portlet.p..<portletwindow1>?org.apache.myfaces.portlet.MyFacesGenericPortlet.CURRENT_FACES_CONTEXT > but the facescontext is still with the key window0 in the session. > Using the same window name in different pages for the same portlet leeds to a portal error. > <snap> > best regards > Stefan Tausendpfund -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-558) Navigation with JSF/Facelets broken with multiple portlets in one page

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-558?page=all ] Julien Viet updated JBPORTAL-558: --------------------------------- Fix Version/s: 2.6.Beta1 (was: 2.6.Alpha1) > Navigation with JSF/Facelets broken with multiple portlets in one page > ---------------------------------------------------------------------- > > Key: JBPORTAL-558 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-558 > Project: JBoss Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.2 Final > Environment: Linux Red Hat Enterprise Server 4 64 Bit, JDK 1.5.0_06 > Reporter: gressho > Fix For: 2.6.Beta1 > > > Navigation results in JSF/Facelet appear allways in the first portlet of the page. The "result" is the same, but "from" and "to" aren't. > Everything works correct with JSF/JSP. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-522) Edit modes and window states in the portalobject manager

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-522?page=all ] Julien Viet resolved JBPORTAL-522. ---------------------------------- Resolution: Won't Fix Management portlet is being redone in beta. > Edit modes and window states in the portalobject manager > -------------------------------------------------------- > > Key: JBPORTAL-522 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-522 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.2 Final > Reporter: Julien Viet > Fix For: 2.6.Alpha1 > > -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-522) Investigate usage of java.util.concurrent in place of EDU.oswego...util.concurrent where possible.

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-522?page=all ] Manik Surtani closed JBCACHE-522. --------------------------------- Resolution: Done Decided to move to Java5 concurrent classes. > Investigate usage of java.util.concurrent in place of EDU.oswego...util.concurrent where possible. > --------------------------------------------------------------------------------------------------- > > Key: JBCACHE-522 > URL: http://jira.jboss.com/jira/browse/JBCACHE-522 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.GA > Reporter: Ben Wang > Assigned To: Manik Surtani > Fix For: 2.0.0.GA > > > Whether this is done via Retroweaver or just the equivalent package needs to be investigated so it will be easy to migrate to JDK1.5 package. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBCACHE-522) Investigate usage of java.util.concurrent in place of EDU.oswego...util.concurrent where possible.

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-522?page=all ] Manik Surtani reopened JBCACHE-522: ----------------------------------- > Investigate usage of java.util.concurrent in place of EDU.oswego...util.concurrent where possible. > --------------------------------------------------------------------------------------------------- > > Key: JBCACHE-522 > URL: http://jira.jboss.com/jira/browse/JBCACHE-522 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.GA > Reporter: Ben Wang > Assigned To: Manik Surtani > Fix For: 2.0.0.GA > > > Whether this is done via Retroweaver or just the equivalent package needs to be investigated so it will be easy to migrate to JDK1.5 package. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBCACHE-664) Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-664?page=all ] Manik Surtani reopened JBCACHE-664: ----------------------------------- > Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary > ------------------------------------------------------------------------- > > Key: JBCACHE-664 > URL: http://jira.jboss.com/jira/browse/JBCACHE-664 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0.GA > Reporter: Manik Surtani > Assigned To: Manik Surtani > Priority: Critical > Fix For: 2.0.0.BETA1, 2.0.0.GA > > Original Estimate: 2 days > Remaining Estimate: 2 days > > * Use JBossRetro to build a compat version of JBossCache > * Baseline against Java5 for 'normal' builds > * Don't migrate concurrent.jar - still stick with concurrent.jar for concurrent utils rather than java.util.concurrent. -- 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

19 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2007