April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-392) Document cflow fails with JRockit

by Flavia Rainone (JIRA)

Document cflow fails with JRockit --------------------------------- Key: JBAOP-392 URL: http://jira.jboss.com/jira/browse/JBAOP-392 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Flavia Rainone We need to document that cflow may not work correctly with JRockit. This happens when JBoss AOP needs to verify if a method or constructor is in the current stack, and this stack is too big. JRockit shortens the stack, by omitting the oldest elements of the stack. That way, JBoss AOP cannot find those elements and may fail a cflow matching when it should succeed. -- 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: (JBJMX-104) SNMP Adaptor doen't accept TruthValue according to SNMP v2

by Luca Stancapiano (JIRA)

SNMP Adaptor doen't accept TruthValue according to SNMP v2 ---------------------------------------------------------- Key: JBJMX-104 URL: http://jira.jboss.com/jira/browse/JBJMX-104 Project: JBoss JMX Issue Type: Patch Environment: linux , eclipse, I'm using jboss 4.0.4-GA Reporter: Luca Stancapiano hi.......if you try to take a TruthValue using a MIB Browser , you receive nothing because org.jboss.jmx.adaptor.snmp.agent.RequestHandlerImpl doesn't manage booleans ....I added a patch into getValueFor method ( row 474 ) that manage it with good results. I think that setValue method doesn't need the same correction because joesnmp can simply to interpret TruthValue as SnmpStringOctet object row 474: else if (val instanceof Boolean) { Boolean in = (Boolean) val; ssy = new SnmpOctetString(in.toString().getBytes()); } -- 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

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-4338) Improve version information in jar-versions.xml

by Arjan van Bentem (JIRA)

Improve version information in jar-versions.xml ----------------------------------------------- Key: JBAS-4338 URL: http://jira.jboss.com/jira/browse/JBAS-4338 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.0.CR1 Environment: All Reporter: Arjan van Bentem Priority: Optional jboss-4.2.0.CR1.zip as available at http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16... shows the same information for many of the JAR files, in fact referring to the version of JBoss AS rather than the version of those specific JARs. For example: <jar name="antlr.jar" specVersion="4.2.0.CR1" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.CR1 (build: SVNTag=JBoss_4_2_0_CR1 date=200703051212)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="a107fc899a0c4a329cc04f8938fd607b"/> Reading the following Javadoc I guess this is caused by missing MANIFEST information in the third-party libraries. Therefore, some other means of telling which versions are used would be appreciated very much! http://fisheye.jboss.com/browse/JBoss/build/jboss/VersionRelease.java?r=1.5 /** A utility which goes through a standard dist build and tags every jar * with the current build version using the jar file version manifest * headers. The unique jars and their version info and md5 digests are * output to the jboss.home/jar-versions.xml. * * @author Scott.Stark(a)jboss.org * @version $Revision: 1.5 $ */ public class VersionRelease { : } Thanks, Arjan. -- 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: (JBAOP-379) Arguments array should be null when the joinpoint arguments list is empty

by Flavia Rainone (JIRA)

Arguments array should be null when the joinpoint arguments list is empty ------------------------------------------------------------------------- Key: JBAOP-379 URL: http://jira.jboss.com/jira/browse/JBAOP-379 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha4 Reporter: Flavia Rainone Assigned To: Flavia Rainone Fix For: 2.0.0.alpha5 The arguments array contained in Invocation instances should be null when the joinpoint arguments list is empty. The same applies to arguments array contained in @Args annotated parameters (for before/after/afterthrowing/finally advices). -- 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] Created: (JGRP-456) Make thread pool in Multiplexer non-static, implement shutdown

by Bela Ban (JIRA)

Make thread pool in Multiplexer non-static, implement shutdown -------------------------------------------------------------- Key: JGRP-456 URL: http://jira.jboss.com/jira/browse/JGRP-456 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Vladimir Blagojevic Fix For: 2.5 -- 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] Updated: (EJBTHREE-585) ejb3 fine-grained sfsb replication support

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-585?page=all ] Brian Stansberry updated EJBTHREE-585: -------------------------------------- Fix Version/s: EJB 3.0 RC11 - FD (was: AS 4.2.0 GA) This is not going to happen for 4.2.0.GA, and even RC11 is unlikely. > ejb3 fine-grained sfsb replication support > ------------------------------------------ > > Key: EJBTHREE-585 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-585 > Project: EJB 3.0 > Issue Type: Feature Request > Components: Clustering > Reporter: Ben Wang > Assigned To: Jason T. Greene > Fix For: EJB 3.0 RC11 - FD > > > This is the parent issue to track the overal fine-grained implementation using PojoCache -- 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] Updated: (EJBTHREE-127) Create Docbook for @Consumer

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-127?page=all ] Carlo de Wolf updated EJBTHREE-127: ----------------------------------- Fix Version/s: AS 4.2.0 GA (was: AS 4.2.0 CR2) > Create Docbook for @Consumer > ---------------------------- > > Key: EJBTHREE-127 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-127 > Project: EJB 3.0 > Issue Type: Task > Reporter: Bill Burke > Assigned To: Bill Burke > Fix For: AS 4.2.0 GA > > -- 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] Updated: (EJBTHREE-124) @PersistenceContext(EXTENDED) should follow new Spec defined rules

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-124?page=all ] Carlo de Wolf updated EJBTHREE-124: ----------------------------------- Fix Version/s: AS 4.2.0 GA (was: AS 4.2.0 CR2) > @PersistenceContext(EXTENDED) should follow new Spec defined rules > ------------------------------------------------------------------ > > Key: EJBTHREE-124 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-124 > Project: EJB 3.0 > Issue Type: Feature Request > Affects Versions: Preview 5 > Reporter: Bill Burke > Fix For: AS 4.2.0 GA > > > I don't yet follow all the spec defined rules for @PersistenceContext(EXTENDED) -- 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] Updated: (EJBTHREE-27) Allowed methods

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-27?page=all ] Carlo de Wolf updated EJBTHREE-27: ---------------------------------- Fix Version/s: AS 4.2.0 GA (was: AS 4.2.0 CR2) > Allowed methods > --------------- > > Key: EJBTHREE-27 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-27 > Project: EJB 3.0 > Issue Type: Feature Request > Affects Versions: Preview 5 > Reporter: Bill Burke > Assigned To: Bill Burke > Fix For: AS 4.2.0 GA > > > EJB specification has semanatics for what methods can be called when. -- 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] Updated: (EJBTHREE-217) The container should Instruments Hibernate classes

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-217?page=all ] Carlo de Wolf updated EJBTHREE-217: ----------------------------------- Fix Version/s: AS 4.2.0 GA (was: AS 4.2.0 CR2) > The container should Instruments Hibernate classes > -------------------------------------------------- > > Key: EJBTHREE-217 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-217 > Project: EJB 3.0 > Issue Type: Feature Request > Components: EJB3 Extensions > Affects Versions: EJB 3.0 Beta 1 > Reporter: Emmanuel Bernard > Assigned To: Bill Burke > Priority: Minor > Fix For: AS 4.2.0 GA > > > Right now, the user has to instrument Hibernate classes itself through a InstrumentAnt task to enable some features such as property level lazy loading > It'd be cool if the container execute the same job at class load time in an automatic manner. > http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#performanc... -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2007