February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBFORUMS-92) UTF-8 doesn't work in topic subjects

by Ryszard Kozmik (JIRA)

[ http://jira.jboss.com/jira/browse/JBFORUMS-92?page=all ] Ryszard Kozmik updated JBFORUMS-92: ----------------------------------- Fix Version/s: 1.2.0 Alpha (was: 1.0.0 Beta) No hurry with this one and there are more important tasks. > UTF-8 doesn't work in topic subjects > ------------------------------------ > > Key: JBFORUMS-92 > URL: http://jira.jboss.com/jira/browse/JBFORUMS-92 > Project: JBoss Forums > Issue Type: Bug > Components: Forum View Layer > Reporter: Tomasz Szymanski > Assigned To: Ryszard Kozmik > Fix For: 1.2.0 Alpha > > Time Spent: 1 hour, 30 minutes > Remaining Estimate: 0 minutes > > http://65.244.175.213:8080/portal-forums/views/index.jsf > shows some silly chars instead of polish diacritic letters. -- 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] Created: (JBFORUMS-158) Class Cast Exception when using JBoss Forums with Portal 2.6Alpha1

by Ian White (JIRA)

Class Cast Exception when using JBoss Forums with Portal 2.6Alpha1 ------------------------------------------------------------------ Key: JBFORUMS-158 URL: http://jira.jboss.com/jira/browse/JBFORUMS-158 Project: JBoss Forums Issue Type: Bug Affects Versions: 1.0.0 Alpha Environment: AS 4.0.5.GA Portal 2.6 Alpha 1 jboss-forums-1.0.0Alpha-P2.6DR Oracle 9i using oci driver Reporter: Ian White Assigned To: Ryszard Kozmik On startup, you get: ... 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'shared' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'summary' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'category' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'forum' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'topic' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'newTopic' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'replyTopic' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'editPost' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'jumpbox' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'profile' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'moderator' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'splitTopic' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'deletePost' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'pollController' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'adminPanel' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'adminController' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'prefController' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'topicWatch' - only keeping the last 17:17:23,359 WARN [FacesConfigurator] More than one managed bean w/ the name of 'forumWatch' - only keeping the last 17:17:23,359 INFO [MyFacesGenericPortlet] PortletContext 'C:\jboss-4.0.5.GA\server\oracle-portal26\.\deploy\jboss-forums.ear\portal-forums.war\' initialized. 17:17:23,421 ERROR [PortletAppDeployment] Error when creating instances java.lang.ClassCastException: org.jboss.portal.core.deployment.jboss.PortletAppDeployment$InstanceMetaDataContext at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.buildInstances(PortletAppDeployment.java:231) at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.start(PortletAppDeployment.java:97) at org.jboss.portal.server.deployment.jboss.DeploymentContext.start(DeploymentContext.java:99) at org.jboss.portal.server.deployment.jboss.PortalDeploymentInfoContext.start(PortalDeploymentInfoContext.java:210) at org.jboss.portal.server.deployment.jboss.ServerDeployer.start(ServerDeployer.java:217) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) ... -- 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

2
3
0 / 0

[JBoss JIRA] Updated: (JBBUILD-252) How would the testsuite work?

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-252?page=all ] Paul Gier updated JBBUILD-252: ------------------------------ Assignee: Paul Gier > How would the testsuite work? > ----------------------------- > > Key: JBBUILD-252 > URL: http://jira.jboss.com/jira/browse/JBBUILD-252 > Project: JBoss Build System > Issue Type: Feature Request > Reporter: Ruel Loehr > Assigned To: Paul Gier > Fix For: MavenBuild 1.2 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > How would the testsuite work using maven? -- 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] Created: (JBAS-4047) PooledInvokerProxy.getPooledConnection() could hold a lock for shorter period of time

by Scott Marlow (JIRA)

PooledInvokerProxy.getPooledConnection() could hold a lock for shorter period of time ------------------------------------------------------------------------------------- Key: JBAS-4047 URL: http://jira.jboss.com/jira/browse/JBAS-4047 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Remoting Affects Versions: JBossAS-5.0.0.Beta1, JBossAS-4.0.5.GA Reporter: Scott Marlow Assigned To: Scott Marlow Priority: Optional I'm seeing Java lock object contention in the org.jboss.invocation.pooled.interfaces.PooledInvokerProxy.getPooledConnection(). I would like to reduce the time that we hold the lock to boost performance. for the current 4.0 head implementation, I'm thinking about something like this: svn diff server\src\main\org\jboss\invocation\pooled\interfaces\PooledInvokerProxy.java Index: server/src/main/org/jboss/invocation/pooled/interfaces/PooledInvokerProxy.java =================================================================== --- server/src/main/org/jboss/invocation/pooled/interfaces/PooledInvokerProxy.java (revision 60160) +++ server/src/main/org/jboss/invocation/pooled/interfaces/PooledInvokerProxy.java (working copy) @@ -493,17 +493,23 @@ return cs; } + protected ClientSocket firstConnection() + { + synchronized (pool) + { + if(pool.size() > 0) + return (ClientSocket)pool.removeFirst(); + } + return null; + } + protected synchronized ClientSocket getPooledConnection() { ClientSocket socket = null; - while (pool.size() > 0) + while ((socket = firstConnection()) != null) { try { - synchronized( pool ) - { - socket = (ClientSocket)pool.removeFirst(); - } // Test to see if socket is alive by send ACK message if( trace ) log.trace("Checking pooled socket: "+socket+", address: "+socket.socket.getLocalSocketAddress()); -- 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

2
10
0 / 0

[JBoss JIRA] Assigned: (JBAS-3162) Testcase to validate set up of a root context web app

by Stan Silvert (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3162?page=all ] Stan Silvert reassigned JBAS-3162: ---------------------------------- Assignee: Stan Silvert (was: Anil Saldhana) > Testcase to validate set up of a root context web app > ----------------------------------------------------- > > Key: JBAS-3162 > URL: http://jira.jboss.com/jira/browse/JBAS-3162 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Anil Saldhana > Assigned To: Stan Silvert > Priority: Minor > Fix For: JBossAS-4.2.0.CR1, JBossAS-5.0.0.Beta2 > > > Need to have a testcase that validates > http://wiki.jboss.org/wiki/Wiki.jsp?page=SetupARootContextApp -- 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] Created: (JBESB-389) Transformation Console should support 1024 x 768

by Burr Sutter (JIRA)

Transformation Console should support 1024 x 768 ------------------------------------------------ Key: JBESB-389 URL: http://jira.jboss.com/jira/browse/JBESB-389 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.0 CR2 Reporter: Burr Sutter Assigned To: Tom Fennelly Priority: Minor Fix For: 4.0 Maintenance Pack 1 The current transformation console requires horizontal scrolling to see all of the contents on a 1024 by 768 capable monitor. The majority of users will only have 1024 x 768. Plus most presenters using projectors are limited to 1024 by 768. -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-780) document how to replace hashtable with ehcache cacheprovider

by Tom Baeyens (JIRA)

document how to replace hashtable with ehcache cacheprovider ------------------------------------------------------------ Key: JBPM-780 URL: http://jira.jboss.com/jira/browse/JBPM-780 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM 3.2 alpha 3 -- 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] Updated: (JBPM-653) make the process parent classloader configurable

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-653?page=all ] Tom Baeyens updated JBPM-653: ----------------------------- Fix Version/s: jBPM 3.2 (was: jBPM 3.2 beta 2) i'll have to postpone this for a later release. > make the process parent classloader configurable > ------------------------------------------------ > > Key: JBPM-653 > URL: http://jira.jboss.com/jira/browse/JBPM-653 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM 3.2 > > > now, always the jBPM classloader is taken as a parent for the process classloaders. this should be made configurable. at least one other possibility should be to configure the context classloader. -- 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

Si quiere pagar de más...llame por otro Carrier

by Carrier 179

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBXB-95) marshalling subclasses of java.util.Date mapped to xsd:dateTime

by Alexey Loubyansky (JIRA)

marshalling subclasses of java.util.Date mapped to xsd:dateTime --------------------------------------------------------------- Key: JBXB-95 URL: http://jira.jboss.com/jira/browse/JBXB-95 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-1.0.0.CR8 Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Fix For: JBossXB-1.0 Attempt to marshal a subclass of java.util.Date as xsd:dateTime should pass. We shouldn't require a binding customization for marshalling. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2007