October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMICROCONT-187) Complete the single deployment api

by Adrian Brock (JIRA)

Complete the single deployment api ---------------------------------- Key: JBMICROCONT-187 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-187 Project: JBoss MicroContainer Issue Type: Task Components: Deployment Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC-2.0.0.GA The single deployment api needs finishing. 1) deploy()/undeploy() on the DeployerClient/MainDeployer need making threadsafe such that they only do work on the deployment passed a parameter 2) The incomplete checking for a single deployment needs to "know" look at only those microcontainer contexts that it created (+ those contexts/deployments referenced as dependencies). -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-556) Consolidate thread pools

by Vladimir Blagojevic (JIRA)

Consolidate thread pools ------------------------ Key: JGRP-556 URL: http://jira.jboss.com/jira/browse/JGRP-556 Project: JGroups Issue Type: Task Reporter: Vladimir Blagojevic Assigned To: Bela Ban Fix For: 2.6 For JGroups 2.5 we have used numerous instances of ThreadPoolExecutor(s) as we needed them. For instance, STREAMING_STATE_TRANSFER, Multiplexer, TP, and ProtocolStack. Undoubtedly this lead to increased overhead and performance impact that we have not measured. First of all we should stop indiscriminately introducing new thread pools as we go further. Second, we should Investigate possibility to consolidate thread pools so they can be reused by various protocols and components of a channel. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1720) Profile / enhance error message : DatePropertyAccessor

by Antoine Herzog (JIRA)

Profile / enhance error message : DatePropertyAccessor ------------------------------------------------------- Key: JBPORTAL-1720 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1720 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: 2.6.1 Final Reporter: Antoine Herzog Priority: Optional Fix For: 2.6.2 Final Line 552 catch (ParseException e) { throw new IllegalArgumentException(); } Some more information on the error will be helpfull, espcially for integration of legacy user datasource. Like it is done for the boolean property accessor something like : catch (ParseException e) { throw new IllegalArgumentException("Can't convert the date in the user profile. value=[" + value + "].", e); } -- 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, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-4152) Upgrade to hsql 1.8.0.7 causes org.jboss.test.cmp2.idxandusersql.test.IdxAndUsersqlUnitTestCase::testCMRmn2 to fail

by Vivek Lakshmanan (JIRA)

Upgrade to hsql 1.8.0.7 causes org.jboss.test.cmp2.idxandusersql.test.IdxAndUsersqlUnitTestCase::testCMRmn2 to fail ------------------------------------------------------------------------------------------------------------------- Key: JBAS-4152 URL: http://jira.jboss.com/jira/browse/JBAS-4152 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.0.5.CR1 Environment: BEA JRockit 1.5.0_08 on Red Hat Enterprise Linux AS release 4 (Nahant Update 4) Reporter: Vivek Lakshmanan Assigned To: Scott M Stark On upgrade of HSQLDB from 1.8.0.2 to 1.8.0.7 the following testcase seems to consistently fail: org.jboss.test.cmp2.idxandusersql.test.IdxAndUsersqlUnitTestCase::testCMRmn2 Error: FKey cmr2_id is indexed The test reports say: junit.framework.AssertionFailedError: Error: FKey cmr2_id is indexed at org.jboss.test.cmp2.idxandusersql.test.IdxAndUsersqlUnitTestCase.testCMRmn2(IdxAndUsersqlUnitTestCase.java:190) at net.sourceforge.junitejb.EJBTestCase.runBare(EJBTestCase.java:133) at net.sourceforge.junitejb.EJBTestRunnerBean.runTestCase(EJBTestRunnerBean.java:102) at net.sourceforge.junitejb.EJBTestRunnerBean.run(EJBTestRunnerBean.java:44) at org.jboss.invocation.Invocation.performCall(Invocation.java:359) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:237) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158) at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121) at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:173) at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:77) at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:169) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136) at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648) The sourcefile for the test says: /* * Look for indices on the m:n mapping table * This is for hsql a strange case, at indices are put there * anyway, but it has been told that other databases don't do * it by themselves, so we check if the creation succeeds. */ Would like to get an experts opinion 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

18 years, 8 months

5
16
0 / 0

[JBoss JIRA] Created: (JBXB-108) Expand DefaultSchemaResolver and SchemaResolverConfig to support namespace to binding class mappings

by Scott M Stark (JIRA)

Expand DefaultSchemaResolver and SchemaResolverConfig to support namespace to binding class mappings ---------------------------------------------------------------------------------------------------- Key: JBXB-108 URL: http://jira.jboss.com/jira/browse/JBXB-108 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Affects Versions: JBossXB-2.0.0.CR4 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossXB-2.0.0.CR5 The org.jboss.xb.builder.JBossXBBuilder class supports the creation of a SchemaBinding from a class annotated with JAXB annotations. The DefaultSchemaResolver and SchemaResolverConfig bean need to be updated to allow specification of a namespace URI to binding class mapping. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBXB-109) Element type causes parse error

by Scott M Stark (JIRA)

Element type causes parse error ------------------------------- Key: JBXB-109 URL: http://jira.jboss.com/jira/browse/JBXB-109 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.0.CR5 Reporter: Scott M Stark Assigned To: Adrian Brock Fix For: JBossXB-2.0.0.CR5 If I uncomment the proxyFactoryConfig property on the InvokerProxyBindingMetaData bean, the JBoss5xEverything.testEverything test starts to fail with a CCE: org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/home/svn/Common/trunks/jbossxb/target/test-classes/org/jboss/test/ejb/metadata/test/JBoss5xEverything_testEverything.xml@2693,38 at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:184) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:139) at org.jboss.test.xb.builder.JBossXBTestDelegate.unmarshal(JBossXBTestDelegate.java:121) at org.jboss.test.javaee.metadata.AbstractJavaEEMetaDataTest.unmarshal(AbstractJavaEEMetaDataTest.java:184) at org.jboss.test.javaee.metadata.AbstractJavaEEMetaDataTest.unmarshal(AbstractJavaEEMetaDataTest.java:154) at org.jboss.test.javaee.metadata.AbstractJavaEEMetaDataTest.unmarshal(AbstractJavaEEMetaDataTest.java:120) at org.jboss.test.ejb.metadata.test.JBoss5xEverythingUnitTestCase.unmarshal(JBoss5xEverythingUnitTestCase.java:106) at org.jboss.test.ejb.metadata.test.JBoss5xEverythingUnitTestCase.testEverything(JBoss5xEverythingUnitTestCase.java:113) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: java.lang.RuntimeException: QName {http://java.sun.com/xml/ns/javaee}description error adding java.util.ArrayList@16e1eea8 to collection org.jboss.javaee.metadata.spec.DescriptionsImpl@4afb6354 at org.jboss.xb.builder.runtime.CollectionPropertyHandler.handle(CollectionPropertyHandler.java:137) at org.jboss.xb.builder.runtime.AbstractPropertyHandler.doHandle(AbstractPropertyHandler.java:98) at org.jboss.xb.builder.runtime.PropertyWildcardHandler.setParent(PropertyWildcardHandler.java:72) at org.jboss.xb.binding.group.ValueListHandler$FACTORY$1.newInstance(ValueListHandler.java:401) at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endRepeatableParticle(SundayContentHandler.java:825) at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:319) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:180) ... 23 more Caused by: java.lang.ClassCastException: java.util.ArrayList at org.jboss.javaee.metadata.support.MappedAnnotationMetaData.add(MappedAnnotationMetaData.java:1) at org.jboss.xb.builder.runtime.CollectionPropertyHandler.handle(CollectionPropertyHandler.java:133) ... 40 more The JBoss5xEverything_testEverything.xml was updated to include a proxy-factory-config element, but this is not being reached. -- 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, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBXB-110) Resolve testcase regressions

by Scott M Stark (JIRA)

Resolve testcase regressions ---------------------------- Key: JBXB-110 URL: http://jira.jboss.com/jira/browse/JBXB-110 Project: JBoss XML Binding (JBossXB) Issue Type: Sub-task Reporter: Scott M Stark Fix For: JBossXB-2.0.0.CR5 We need to resolve issues with conflicting defaults and thirdparty based regressions. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4892) WebService ignores java.rmi.server.codebase system property

by Takayoshi Kimura (JIRA)

WebService ignores java.rmi.server.codebase system property ----------------------------------------------------------- Key: JBAS-4892 URL: http://jira.jboss.com/jira/browse/JBAS-4892 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Reporter: Takayoshi Kimura server/src/main/org/jboss/web/WebService.java The trailing semicolon of if statement is a bug. String codebase = getCodebase(); // This returns system property value if (codebase == null); // HERE { codebase = "http://" + getHost() + ":" + getPort() + "/"; System.setProperty("java.rmi.server.codebase", codebase); } log.info("Using RMI server codebase: " + codebase); -- 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, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1567) Simplify WSRP Consumer GUI configuration tool

by Chris Laprun (JIRA)

Simplify WSRP Consumer GUI configuration tool --------------------------------------------- Key: JBPORTAL-1567 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1567 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.2 Final, 2.8 Final - Default action should be Save & Refresh instead of Save. - Validate registration is kind of useless as it is and only serves to make the interface more confusing, it should be removed. - Add more visual separation between elements. - Use better form code. -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4728) AS's JChannelFactory subclass should ignore duplicate lifecycle calls

by Brian Stansberry (JIRA)

AS's JChannelFactory subclass should ignore duplicate lifecycle calls --------------------------------------------------------------------- Key: JBAS-4728 URL: http://jira.jboss.com/jira/browse/JBAS-4728 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta3 If already created, ignore create(), etc. -- 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, 8 months

1
4
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 October 2007