February 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBUILD-421) Classpath is incorrect when running javadoc reports

by Paul Gier (JIRA)

Classpath is incorrect when running javadoc reports --------------------------------------------------- Key: JBBUILD-421 URL: http://jira.jboss.com/jira/browse/JBBUILD-421 Project: JBoss Build System Issue Type: Bug Components: Maven Reporter: Paul Gier Fix For: Maven Build - Maint 2007 JBoss Cache build has an issue with the javadoc plugin. The javadocs work fine when run from the main build, but fail with errors when generating the site. It appears that the testng jar is required for the javadoc generation, but this jar is not getting included in the classpath when run from the reports section. The issue could be related to this one: http://jira.codehaus.org/browse/MJAVADOC-140 -- 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

13 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-442) Fix pom.xmls so that maven-eclipse-plugin generate correct eclipse settings files

by pether (JIRA)

Fix pom.xmls so that maven-eclipse-plugin generate correct eclipse settings files --------------------------------------------------------------------------------- Key: JBBUILD-442 URL: http://jira.jboss.com/jira/browse/JBBUILD-442 Project: JBoss Build System Issue Type: Feature Request Components: Maven Affects Versions: Maven Build - Maint 2008 Reporter: pether Priority: Minor Fix For: Maven Build - Maint 2008 Two different cases that should work for developers to choose from 1. Using eclipse project references generate files with : mvn eclipse:clean eclipse:eclipse -Declipse.useProjectReferences=true 2. Using maven repository jar references generate files with : mvn eclipse:clean eclipse:eclipse -Declipse.useProjectReferences=true In some ways an audit of http://jira.jboss.org/jira/browse/JBBUILD-258 and resolve any issues with dependencies. Current issues with jboss/trunk The projects below have compile errors, mostly incorrect project dependencies jboss-as-deployment jboss-as-console jboss-as-iiop jboss-as-varia -- 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

13 years, 5 months

2
13
0 / 0

[JBoss JIRA] Created: (JGRP-685) Perf test

by Bela Ban (JIRA)

Perf test --------- Key: JGRP-685 URL: http://jira.jboss.com/jira/browse/JGRP-685 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.7 Things to do with the perf test: - Mimick buddy replication: send messages not to self, but only to a selected buddy - Measure time to send 100MB to A, B, C, D - New look at HTOTAL, might help with perf in this scenario - TcpTransport (95MB/sec) versus JGroupsTransport/tcp.xml (54MB/sec): why the diff ? - Members: A (send), B (receive) - Might get better perf with impl of first bullet item (above) - JPerf (between A and B) gets 113MB/sec ! -- 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

13 years, 5 months

1
12
0 / 0

[JBoss JIRA] Created: (EJBTHREE-909) Injection of Simple Environment Entries Using Resource Annotation without name

by Roland R?z (JIRA)

Injection of Simple Environment Entries Using Resource Annotation without name ------------------------------------------------------------------------------ Key: EJBTHREE-909 URL: http://jira.jboss.com/jira/browse/EJBTHREE-909 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: Roland R?z The name of the @Resource annotations should default to the property or method name. The following simple environment injections are not working as expected: @Resource String stringValue; Long longValue = Long.valueOf(1); @Resource void setLongValue(Long longValue) { this.longValue = longValue; } Workaround: @Resource(name = "stringValue") String stringValue = "hi"; Long longValue = Long.valueOf(1); @Resource(name = "longValue") public void setIntValue(Long longValue) { this.longValue = longValue; } -- 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

13 years, 6 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-4363) OSGi Bundle Repository support

by Scott M Stark (JIRA)

OSGi Bundle Repository support ------------------------------ Key: JBAS-4363 URL: http://jira.jboss.com/jira/browse/JBAS-4363 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3 The OSGi Bundle Repository support requirements need to be considered. -- 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

13 years, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-3778) AttributePersistenceService does not allow absolute path for data-directory value

by Darran Lofthouse (JIRA)

AttributePersistenceService does not allow absolute path for data-directory value --------------------------------------------------------------------------------- Key: JBAS-3778 URL: http://jira.jboss.com/jira/browse/JBAS-3778 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-4.0.4.GA Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: JBossAS-4.0.6.CR1 AttributePersistenceService does not allow absolute path for data-directory value, any value specified even with a leading '/' is created within the folder of the configuration being executed. Also the default configuration in the jboss-service.xml should take into account the setting for jboss.server.data.dir -- 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

13 years, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-3630) JMSTransportSupport is not portable across different JMS providers.

by Darran Lofthouse (JIRA)

JMSTransportSupport is not portable across different JMS providers. ------------------------------------------------------------------- Key: JBAS-3630 URL: http://jira.jboss.com/jira/browse/JBAS-3630 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: JBossAS-4.0.4.GA Reporter: Darran Lofthouse Assigned To: Thomas Diesler Fix For: JBossAS-4.0.6.CR1 JMSTransportSupport is not portable across different JMS providers, the queue name is retrieved using the following code: - String fromName = null; Destination destination = message.getJMSDestination(); if (destination instanceof Queue) fromName = "queue/" + ((Queue)destination).getQueueName(); if (destination instanceof Topic) fromName = "topic/" + ((Topic)destination).getTopicName(); For JBossMQ this is fine and it results in a name that matches the JNDI name of the queue, for WebSphereMQ this returns the name of the queue as configured on WebSphere not the JNDI name the queue is bound to in JBoss. The Javadoc for Queue describes the getQueueName as not being suitable for portable clients: - http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Queue.html A more portable solution could be to lookup a variable in the ENC that contains the name of the web service, this could either be provided by the user deploying the MDB or the web service deployer could bind a value to the ENC of the message driven bean as the web service is deployed. -- 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

13 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-5102) Crossreferencing EJBs using comp-names does not work

by Christian Nolte (JIRA)

Crossreferencing EJBs using comp-names does not work ---------------------------------------------------- Key: JBAS-5102 URL: http://jira.jboss.com/jira/browse/JBAS-5102 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.2.2.GA Reporter: Christian Nolte Assigned To: Carlo de Wolf I have two stateless session beans which are referencing each other like that: @Stateless public class SessionBeanA implements SessionBeanALocal { @EJB private SessionBeanB sessionB; } and @Stateless public class SessionBeanB implement SessionBeanBLocal { @EJB private SessionBeanA sessionA; } When deploying the application on JBoss AS I get --- MBeans waiting for other MBeans --- ObjectName: jboss.j2ee:jar=test.jar,name=SessionBeanA,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:jar=test.jar,name=SessionBeanB,service=EJB3 persistence.units:jar=test.jar,unitName=test.jar Depends On Me: jboss.j2ee:jar=test.jar,name=SessionBeanB,service=EJB3 ObjectName: jboss.j2ee:jar=test.jar,name=SessionBeanB,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:jar=test.jar,name=SessionBeanA,service=EJB3 Depends On Me: jboss.j2ee:jar=test.jar,name=SessionBeanA,service=EJB3 and the deployment fails. -- 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

13 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-5197) Add "RetryInterceptor" functionality to all clustered proxies

by Brian Stansberry (JIRA)

Add "RetryInterceptor" functionality to all clustered proxies ------------------------------------------------------------- Key: JBAS-5197 URL: http://jira.jboss.com/jira/browse/JBAS-5197 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.1.0.CR1 Container issue for ensuring "RetryInterceptor" functionality is added to all clustered proxies. "RetryInterceptor" functionality consists of adding an interceptor that is able to access the cluster (currently via JNDI) and get an updated set of cluster targets when all current targets have failed. Needed when a complete cluster restart has occurred since the current list of targets was deserialized on the client. We currently have this for EJB2 proxies; need it for EJB3, HA-JNDI and generic AOP-based and ProxyFactoryHA-based proxies. -- 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

13 years, 6 months

4
9
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1074) Circular @EJB3 references in session beans fail to deploy.

by Gunnar Grim (JIRA)

Circular @EJB3 references in session beans fail to deploy. ---------------------------------------------------------- Key: EJBTHREE-1074 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1074 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.1.GA Reporter: Gunnar Grim The following circular references makes the application undeployable: In ArchiveBrokerBean: @EJB private SeriesBrokerLocal itsSeriesBroker; In SeriesBrokerBean @EJB private ArchiveBrokerLocal itsArchiveBroker; Circular references like these work fine in Glassfish but JBoss shows the following error message: ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3 jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveTypeBroker,service=EJB3 persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU Depends On Me: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveOrigBroker,service=EJB3 jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3 ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveOrigBroker,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3 persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3 persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU Depends On Me: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3 jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=VolumeBroker,service=EJB3 ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=VolumeBroker,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3 persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU -- 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

13 years, 6 months

10
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2008