July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (JBPORTAL-727) ClassCastException from JBoss AS Tomcat ApplicationDispatcher when forwarding with portal provided DispatchedHttpServletRequest

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-727?page=all ] Julien Viet resolved JBPORTAL-727. ---------------------------------- Resolution: Done We rewrote the request dispatching in 2.6 and we use a more compliant way to do it. > ClassCastException from JBoss AS Tomcat ApplicationDispatcher when forwarding with portal provided DispatchedHttpServletRequest > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBPORTAL-727 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-727 > Project: JBoss Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.2 Final > Environment: JBoss Portal 4.0.3SP1 > MyFaces > Reporter: Tuomas Kiviaho > > The portal.xml for reproducing the problem > <portlet-class>org.apache.myfaces.portlet.MyFacesGenericPortlet</portlet-class> > <init-param> > <name>default-view</name> > <value>/myservlet</value> > </init-param> > MyServlet service method > req.getRequestDispatcher("/myjsp.jsp").forward(req, resp); > The request seen below that is given to the servlet causes following exception. > java.lang.ClassCastException: org.jboss.portal.portlet.impl.DispatchedHttpServletRequest > at org.apache.catalina.core.ApplicationDispatcher.unwrapRequest(ApplicationDispatcher.java:814) > at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:401) > The problem most propably relies either in Tomcat ApplicationDispatcher forwarding mechanism since inclusion works ok, but both request and servletcontext based dispachings using forward fail. > Couple of notes from Tomcat ApplicationDispatcher > - doubled request unwrapping when forwarding maybe due to tomcat bug fix number 30949 > - wrapped request not discarded after unwrapping > These may be the real causes but this class mentions to function properly as long as request extends the standard wrapper. This is not the case with DispatchedHttpServletRequest. -- 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

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-710) Producer clustering support

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-710?page=all ] Julien Viet resolved JBPORTAL-710. ---------------------------------- Resolution: Done > Producer clustering support > --------------------------- > > Key: JBPORTAL-710 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-710 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.6 CR3 > Reporter: Julien Viet > Assigned To: Chris Laprun > Fix For: 2.8 Final, 2.6 Final > > -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-710) Producer clustering support

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-710?page=all ] Julien Viet updated JBPORTAL-710: --------------------------------- Fix Version/s: 2.8 Final 2.6 Final Normally producer clustering should be possible out of the box. > Producer clustering support > --------------------------- > > Key: JBPORTAL-710 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-710 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.6 CR3 > Reporter: Julien Viet > Assigned To: Chris Laprun > Fix For: 2.8 Final, 2.6 Final > > -- 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

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPTL-35) Clustered search engine

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPTL-35?page=all ] Julien Viet resolved JBPTL-35. ------------------------------ Resolution: Rejected We will not implement that, we rather focus on making searchable content aggregated in the portal. > Clustered search engine > ----------------------- > > Key: JBPTL-35 > URL: http://jira.jboss.com/jira/browse/JBPTL-35 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Core > Reporter: Julien Viet > > Discussed with bwang at the dev conf, it should be possible to do that by using treecache as a file system implementation for lucene. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-974) Add support for "drools" variable in rule consequences

by Kris Verlaenen (JIRA)

Add support for "drools" variable in rule consequences ------------------------------------------------------ Key: JBRULES-974 URL: http://jira.jboss.com/jira/browse/JBRULES-974 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.0.MR3 Reporter: Kris Verlaenen Assigned To: Kris Verlaenen The variable drools should be supported by code completion in the rule rhs, including all functions etc. that can be invoked on 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

19 years

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1520) Window list state error

by Chris Laprun (JIRA)

Window list state error ----------------------- Key: JBPORTAL-1520 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1520 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6 Final Reporter: Chris Laprun Fix For: 2.6.1 Final Go to a page configuration screen in the management portlet. Click on a window name, you're taken to the window screen. Click back in your browser, click on another window name, you're taken back to the same window page, not the new one. -- 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

2
1
0 / 0

[JBoss JIRA] Commented: (JBPORTAL-860) Update DTDs to reflect changes in descriptors.

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-860?page=comments#action_12367707 ] Julien Viet commented on JBPORTAL-860: -------------------------------------- Is it going to be a never closed issue ? which descriptors are targetted by this issue ? > Update DTDs to reflect changes in descriptors. > ---------------------------------------------- > > Key: JBPORTAL-860 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-860 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.4 Final > Reporter: Chris Laprun > Fix For: 2.8 Final, 2.6.1 Final > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Update and document changes. Should we move to XSD since some of the DTD elements don't seem to reflect the internal structure of descriptors. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1000) Randomise first node chosen using client side load balancing

by Tim Fox (JIRA)

Randomise first node chosen using client side load balancing ------------------------------------------------------------ Key: JBMESSAGING-1000 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1000 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Priority: Minor Fix For: 1.4.0.CR1 When creating the first connection using a connection factory with supportsLoadBalancing = true, then this goes to the same node. This means that if you have multiple JMS clients in different VMs each only opening one connection they all go to the same node. The first connection should instead be randomly chosen from the list. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-971) concurrent issue on Rete node's ObjectTypeConf buildCache

by Mark Proctor (JIRA)

concurrent issue on Rete node's ObjectTypeConf buildCache --------------------------------------------------------- Key: JBRULES-971 URL: http://jira.jboss.com/jira/browse/JBRULES-971 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.MR3, 4.0.0.MR2, 3.1-m1 Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 4.0.0.MR4 java.lang.ArrayIndexOutOfBoundsException: 17 at org.drools.util.AbstractHashTable$HashTableIterator.next(AbstractHashTable.java:250) at org.drools.reteoo.Rete$ObjectTypeConf.buildCache(Rete.java:434) at org.drools.reteoo.Rete$ObjectTypeConf.getObjectTypeNodes(Rete.java:425) at org.drools.reteoo.Rete.assertObject(Rete.java:172) at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:190) at org.drools.reteoo.ReteooWorkingMemory$WorkingMemoryReteAssertAction.execute (ReteooWorkingMemory.java:163) at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:1135) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:781) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:584) at org.drools.jsr94.rules.StatefulRuleSessionImpl.addObject(StatefulRuleSessionImpl.java:162) -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1119) Genericize notification events

by Brian Stansberry (JIRA)

Genericize notification events ------------------------------ Key: JBCACHE-1119 URL: http://jira.jboss.com/jira/browse/JBCACHE-1119 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani Priority: Minor The org.jboss.cache.notifications.event classes/interfaces are not genericized. Therefore you get compiler warning when you try to use an Fqn retrieved via getFqn(). -- 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

1
1
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 July 2007