June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (GPD-111) Add ability to forward and reverse map Semantic Elements to/from Dom Node/Xml Adapters jpdl

by Matthew Sandoz (JIRA)

Add ability to forward and reverse map Semantic Elements to/from Dom Node/Xml Adapters jpdl ------------------------------------------------------------------------------------------- Key: GPD-111 URL: http://jira.jboss.com/jira/browse/GPD-111 Project: JBoss jBPM GPD Issue Type: Feature Request Components: jpdl Environment: all? :) Reporter: Matthew Sandoz Assigned To: Koen Aers Addresses need to add new semantic elements without adding new xml types. Current mapping forces 1-1 mapping between them. this change allows one-to-many mapping between elements by introducing a mapping object for each semantic element. this mapping object's responsibility is to determine if a chunk of xml should map to a semantic element and xml adapter or not. the xml adapter registry holds a set of these mappers and loops through them all, giving each a chance to accept the xml chunk. all accepting mappers are then sorted by priority and the lowest priority number is selected. mappings with no priority are given Integer.MAX priority. Mappings with no mapperClass are given a default mapper class of ConfiguredSemanticElementDomMapper so that existing plugin.xml should continue to function normally. The priority property allows the maintainer of the plugin.xml to change priorities for different circumstances, giving different potentially conflicting mappers a specific preference order. Details of change: Added two elements to xmlMappings.exsd: mapperClass and mapperClassPriority Created interface SemanticElementDomMapper to determine if a given Dom Node can be assigned to a semantic element Created class ConfiguredSemanticElementDomMapper as a base implementation of the SemanticElementDomMapper. This default implementation checks the current configured xml node name against the node name of the passed Dom Node. This should duplicate the existing functionality for existing standard jpdl xml node types. JythonNodeDomMapper is included as an example but should not be committed to the project as it is for specialized use. XmlAdapterRegistry constructs a HashMap of Mappers and has a new getConfigurationElementByNode method. XmlAdapter has 2 lines modified in the createSemanticElementFor method to use the new registry method. XmlAdapterFactory has modifications in createAdapter and createAdapterFromModel -- 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, 11 months

3
36
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1231) Management beans initialized too many times

by Ryszard Kozmik (JIRA)

Management beans initialized too many times ------------------------------------------- Key: JBPORTAL-1231 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1231 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha1, 2.6.Alpha2 Environment: AS 4.0.5 Portal 2.6Alpha1 or Alpha2 from svn tag Reporter: Ryszard Kozmik Assigned To: Julien Viet Priority: Minor Fix For: 2.6.Beta1 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'portalobjectmgr' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'portalAction' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'addPageAction' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'addWindowAction' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'themePropertyAction' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'instancemgr' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'preferenceAction' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'portletmgr' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'createInstanceAction' - only keeping the Those warnings are harmless and are caused by newer myfaces libraries in AS 4.0.5. Please look at forum link included in this task for sollution. However, this sollution might not fully work as Portal has quite old Facelets libraries. -- 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, 11 months

4
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1146) java.lang.NegativeArraySizeException in uploading zip archive

by Antoine Herzog (JIRA)

java.lang.NegativeArraySizeException in uploading zip archive ------------------------------------------------------------- Key: JBPORTAL-1146 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1146 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4 Final Environment: Windows XP / JBP 2.4 Reporter: Antoine Herzog Assigned To: Roy Russo when uploading an archive file, there is an exception : java.lang.NegativeArraySizeException at org.jboss.portal.cms.impl.jcr.command.StoreArchiveCommand.execute(StoreArchiveCommand.java:72) at org.jboss.portal.cms.impl.jcr.JCRCommand.dispatch(JCRCommand.java:61) It is because of the zipEntry.getSize() that return -1 (unknown size). this is because of the use of ZipInputStream class. there is a turnaround with using the ZipFile class instead. see : http://forum.java.sun.com/thread.jspa?threadID=492219&messageID=2316626 -- 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, 11 months

5
9
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-123) Better mechanism to determine Array class

by Adrian Brock (JIRA)

Better mechanism to determine Array class ----------------------------------------- Key: JBMICROCONT-123 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-123 Project: JBoss MicroContainer Issue Type: Task Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock Priority: Minor The current implementation of getArrayClass uses the horrible public static Class getArrayClass(Class clazz, int depth) { return Array.newInstance(clazz, depth).getClass(); } there must be a better way to do this? -- 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, 11 months

4
6
0 / 0

[JBoss JIRA] Created: (JBBUILD-382) Testrun of a project with circular dependencies errantly includes older version of itself

by Jason T. Greene (JIRA)

Testrun of a project with circular dependencies errantly includes older version of itself ----------------------------------------------------------------------------------------- Key: JBBUILD-382 URL: http://jira.jboss.com/jira/browse/JBBUILD-382 Project: JBoss Build System Issue Type: Bug Components: Maven Reporter: Jason T. Greene jboss-common-core has a dependency on jboss-test <dependency> <groupId>jboss</groupId> <artifactId>jboss-test</artifactId> <version>1.0.3.GA</version> <scope>test</scope> </dependency> jboss-test has a dependancy on jboss-common-core <dependency> <groupId>jboss</groupId> <artifactId>jboss-common-core</artifactId> <version>2.0.4.GA</version> </dependency> This leads to the surefire classpath containing 2 versions of jboss-common-core in the classpath, and unfortunately the older version wins. This means the testsuite never actually runs on the version you are modifying, which is a severe problem. Maven should be smart enough not to include the same artifact-id twice. [DEBUG] Test Classpath : [DEBUG] /devel/common-core/trunk/target/classes [DEBUG] /devel/common-core/trunk/target/test-classes [DEBUG] /home/jason/.m2/repository/apache-log4j/log4j/1.2.8/log4j-1.2.8.jar [DEBUG] /home/jason/.m2/repository/jboss/jboss-test/1.0.3.GA/jboss-test-1.0.3.GA.jar [DEBUG] /home/jason/.m2/repository/org/apache/ant/ant-junit/1.7.0/ant-junit-1.7.0.jar [DEBUG] /home/jason/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar [DEBUG] /home/jason/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar [DEBUG] /home/jason/.m2/repository/jboss/jboss-common-logging-spi/2.0.4.GA/jboss-common-logging-spi-2.0.4.GA.jar [DEBUG] /home/jason/.m2/repository/jboss/jboss-logging-log4j/2.0.2.GA/jboss-logging-log4j-2.0.2.GA.jar [DEBUG] /home/jason/.m2/repository/jboss/jboss-common-core/2.0.2.GA/jboss-common-core-2.0.2.GA.jar [DEBUG] /home/jason/.m2/repository/apache-slide/webdavlib/2.0/webdavlib-2.0.jar [DEBUG] /home/jason/.m2/repository/oswego-concurrent/concurrent/1.3.4/concurrent-1.3.4.jar [DEBUG] /home/jason/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar [DEBUG] /home/jason/.m2/repository/jboss/profiler/jvmti/jboss-profiler-jvmti/1.0.0.CR5/jboss-profiler-jvmti-1.0.0.CR5.jar [DEBUG] /home/jason/.m2/repository/apache-xerces/xml-apis/2.7.1/xml-apis-2.7.1.jar [DEBUG] /home/jason/.m2/repository/jboss/jboss-logging-spi/2.0.2.GA/jboss-logging-spi-2.0.2.GA.jar [DEBUG] /home/jason/.m2/repository/org/apache/ant/ant-launcher/1.7.0/ant-launcher-1.7.0.jar [DEBUG] /home/jason/.m2/repository/apache-httpclient/commons-httpclient/2.0.2/commons-httpclient-2.0.2.jar -- 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, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBBUILD-375) Change surefire plugin to accept package names when running a single test.

by Paul Gier (JIRA)

Change surefire plugin to accept package names when running a single test. -------------------------------------------------------------------------- Key: JBBUILD-375 URL: http://jira.jboss.com/jira/browse/JBBUILD-375 Project: JBoss Build System Issue Type: Feature Request Components: Maven Reporter: Paul Gier Fix For: MavenBuild 2007 Currently the surefire plugin only accepts a slash delimited path when running a single test. mvn -Dtest=org/jboss/test/SomeTestCase test This should also accept a package path like this mvn -Dtest=org.jboss.test.SomeTestCase test -- 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, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-992) Give wiki pages a facelift

by Tim Fox (JIRA)

Give wiki pages a facelift -------------------------- Key: JBMESSAGING-992 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-992 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Priority: Minor Fix For: 1.4.0.CR1 The current wiki pages - both user and development contain outdated information. We should update info, and add new content as necessary. -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-519) Replace BoundedList/List with java.util(.concurrent) class

by Bela Ban (JIRA)

Replace BoundedList/List with java.util(.concurrent) class ---------------------------------------------------------- Key: JGRP-519 URL: http://jira.jboss.com/jira/browse/JGRP-519 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.6 E.g. BoundedList could be a subclass of java.util.LinkedList -- 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, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-868) java.lang.IllegalArgumentException: Unable to find operation XYZ for dependent beans in seperate jars

by William DeCoste (JIRA)

java.lang.IllegalArgumentException: Unable to find operation XYZ for dependent beans in seperate jars ----------------------------------------------------------------------------------------------------- Key: EJBTHREE-868 URL: http://jira.jboss.com/jira/browse/EJBTHREE-868 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: William DeCoste Assigned To: William DeCoste java.lang.IllegalArgumentException: Unable to find operation sayHello() javax.ejb.EJBException: java.lang.IllegalArgumentException: Unable to find operation sayHello() at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:999) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:848) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:454) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:527) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:261) Caused by: java.lang.IllegalArgumentException: Unable to find operation sayHello() at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:231) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy89.sayHello(Unknown Source) at org.jboss.ejb3.test.dependency.ABean.getHelloB(ABean.java:18) -- 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, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-385) Research customizing package names for each release or each project.

by Paul Gier (JIRA)

Research customizing package names for each release or each project. -------------------------------------------------------------------- Key: JBBUILD-385 URL: http://jira.jboss.com/jira/browse/JBBUILD-385 Project: JBoss Build System Issue Type: Feature Request Components: JBossRetro Reporter: Paul Gier Fix For: JBossRetro-1.1.1.GA It could be helpful for backwards compatibility to have unique package names for each release of the retro runtime. That way multiple versions of retro included in a product with multiple components could co-exist. The projects that require the retro runtime would be run against a particular version of retro and point to the appropriate fully qualified class names. So a package name could be something like: org.jboss.retro.runtime_1_1_0.* -- 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, 11 months

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 June 2007