July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JASSIST-132) Instrumenting fails with ArrayIndexOutOfBoundsException

by Thomas Mauch (JIRA)

Instrumenting fails with ArrayIndexOutOfBoundsException ------------------------------------------------------- Key: JASSIST-132 URL: https://jira.jboss.org/browse/JASSIST-132 Project: Javassist Issue Type: Bug Affects Versions: 3.13.0.GA Environment: JDK 1.6.0_18 Reporter: Thomas Mauch Assignee: Shigeru Chiba I will upload a test case showing the issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (JASSIST-110) CtClassType.isModified does not check for edited attributes in the ClassFile

by Flavia Rainone (JIRA)

CtClassType.isModified does not check for edited attributes in the ClassFile ---------------------------------------------------------------------------- Key: JASSIST-110 URL: https://jira.jboss.org/jira/browse/JASSIST-110 Project: Javassist Issue Type: Bug Affects Versions: 3.11.0.GA Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 3.12.0.GA If you edit an attribute of a CtClass and call isModified, it will return false. It should return true. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JASSIST-143) Getting an exception NotFoundException

by sagar shinde (JIRA)

Getting an exception NotFoundException -------------------------------------- Key: JASSIST-143 URL: https://issues.jboss.org/browse/JASSIST-143 Project: Javassist Issue Type: Feature Request Affects Versions: 3.14.0.GA Environment: Windows Vista, Jdk 1.6 Reporter: sagar shinde Assignee: Shigeru Chiba I am facing problem in using JavaAssist in Eclipse 3.6.1. I have added the javassist.jar file in the project created in eclipse through buildpath option. My program details r as follows: // 1st program: package temp; //import javassist.*; public class Hello { public void say() { System.out.println("Hello"); } } _________________________________________________________ 2nd program: package temp; import javassist.ClassPool; import javassist.CtClass; import javassist.CtMethod; public class Test { public static void main(String[] args) throws Exception { ClassPool cp = ClassPool.getDefault(); CtClass cc = cp.get("Hello"); CtMethod m = cc.getDeclaredMethod("say"); m.insertBefore("{ System.out.println(\"Hello.say():\"); }"); Class c = cc.toClass(); Hello h = (Hello)c.newInstance(); h.say(); System.out.println("test prog:"); } } Test class while executing shows the error for cp.get() method saying NotFoundException. Whts the error? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (AS7-1229) XML parser changes broke the seam booking example

by Stuart Douglas (JIRA)

XML parser changes broke the seam booking example ------------------------------------------------- Key: AS7-1229 URL: https://issues.jboss.org/browse/AS7-1229 Project: Application Server 7 Issue Type: Bug Reporter: Stuart Douglas Assignee: Stuart Douglas java.lang.RuntimeException: java.lang.ClassNotFoundException: com.sun.org.apache.xerces.internal.parsers.SAXParser from [Module \"deployment.seam-booking.war:main\" from Service Module Loader] at org.jboss.seam.config.xml.parser.ParserMain.parse(ParserMain.java:70) at org.jboss.seam.config.xml.bootstrap.XmlConfigExtension.beforeBeanDiscovery(XmlConfigExtension.java:97) 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:597) at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234) at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:88) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:52) at org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl.fire(BeforeBeanDiscoveryImpl.java:48) at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:351) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:80) at org.jboss.as.weld.services.WeldService.start(WeldService.java:89) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.ClassNotFoundException: com.sun.org.apache.xerces.internal.parsers.SAXParser from [Module \"deployment.seam-booking.war:main\" from Service Module Loader] at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:189) at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:150) at org.jboss.seam.config.xml.parser.ParserMain.parse(ParserMain.java:62) ... 26 more Caused by: java.lang.ClassNotFoundException: com.sun.org.apache.xerces.internal.parsers.SAXParser from [Module \"deployment.seam-booking.war:main\" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:358) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:307) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:101) at org.xml.sax.helpers.NewInstance.newInstance(NewInstance.java:49) at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:187) ... 28 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Issue Comment Edited: (JBEE-86) Add LICENSE.txt to binary's META-INF

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-86?page=com.atlassian.jira.plugin.sy... ] Shelly McGowan edited comment on JBEE-86 at 7/7/11 6:09 PM: ------------------------------------------------------------ I'll make the necessary adjustment to the build to be sure the license files are included. Note, the version being used in most projects is: jboss-transaction-api_1.1_spec-1.0.0.Final.jar. jboss-transaction-api_1.1_spec-1.0.1-Beta1.jar was released specifically for the Infinispan team (JBEE-67). This request prompted a wider discussion of whether all API releases should be OSGi bundles. In the informal discussions I've participated in, sounded like a good idea. was (Author: shelly.mcgowan): I'll make the necessary adjustment to the build to be sure the license files are included. Note, the version being used in most projects is: jboss-transaction-api_1.1_spec-1.0.0.Final.jar. jboss-transactino-api_1.1_spec-1.0.1-Beta1.jar was released specifically for the Infinispan team (JBEE-67). This request prompted a wider discussion of whether all API releases should be OSGi bundles. In the informal discussions I've participated in, sounded like a good idea. > Add LICENSE.txt to binary's META-INF > ------------------------------------ > > Key: JBEE-86 > URL: https://issues.jboss.org/browse/JBEE-86 > Project: JBoss JavaEE APIs > Issue Type: Task > Environment: jboss-transaction-api-1.0.1.GA.jar > Reporter: Pete Muir > > The jboss-transaction-api-1.0.1.GA.jar is missing this file, which is useful as it means a user can easily verify the licensing requirements for dependencies -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Issue Comment Edited: (JBEE-86) Add LICENSE.txt to binary's META-INF

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/JBEE-86?page=com.atlassian.jira.plugin.sy... ] Pete Muir edited comment on JBEE-86 at 7/7/11 2:46 PM: ------------------------------------------------------- FYI I blogged about how we do this in Infinispan and Weld :-) http://in.relation.to/Bloggers/HowToAddADependenciesReportToYourJarWithMaven I also add a DEPENDENCIES.txt report to every jar, with the license of all deps. was (Author: petemuir): FYI I blogged about how we do this in Infinispan and Weld :-) I also add a DEPENDENCIES.txt report to every jar, with the license of all deps. > Add LICENSE.txt to binary's META-INF > ------------------------------------ > > Key: JBEE-86 > URL: https://issues.jboss.org/browse/JBEE-86 > Project: JBoss JavaEE APIs > Issue Type: Task > Environment: jboss-transaction-api-1.0.1.GA.jar > Reporter: Pete Muir > > The jboss-transaction-api-1.0.1.GA.jar is missing this file, which is useful as it means a user can easily verify the licensing requirements for dependencies -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBEE-86) Add LICENSE.txt to binary's META-INF

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/JBEE-86?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on JBEE-86: ------------------------------- FYI I blogged about how we do this in Infinispan and Weld :-) I also add a DEPENDENCIES.txt report to every jar, with the license of all deps. > Add LICENSE.txt to binary's META-INF > ------------------------------------ > > Key: JBEE-86 > URL: https://issues.jboss.org/browse/JBEE-86 > Project: JBoss JavaEE APIs > Issue Type: Task > Environment: jboss-transaction-api-1.0.1.GA.jar > Reporter: Pete Muir > > The jboss-transaction-api-1.0.1.GA.jar is missing this file, which is useful as it means a user can easily verify the licensing requirements for dependencies -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBEE-86) Add LICENSE.txt to binary's META-INF

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/JBEE-86?page=com.atlassian.jira.plugin.sy... ] Paul Gier commented on JBEE-86: ------------------------------- For a temporary fix we can just add the LICENSE.txt file to each project's src/main/resources/META-INF dir, then Maven will add it to the jar. Longer term maybe we want to use the remote-resources plugin to do this similar to how it works in upstream Maven. > Add LICENSE.txt to binary's META-INF > ------------------------------------ > > Key: JBEE-86 > URL: https://issues.jboss.org/browse/JBEE-86 > Project: JBoss JavaEE APIs > Issue Type: Task > Environment: jboss-transaction-api-1.0.1.GA.jar > Reporter: Pete Muir > > The jboss-transaction-api-1.0.1.GA.jar is missing this file, which is useful as it means a user can easily verify the licensing requirements for dependencies -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBEE-86) Add LICENSE.txt to binary's META-INF

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-86?page=com.atlassian.jira.plugin.sy... ] Shelly McGowan commented on JBEE-86: ------------------------------------ I'll make the necessary adjustment to the build to be sure the license files are included. Note, the version being used in most projects is: jboss-transaction-api_1.1_spec-1.0.0.Final.jar. jboss-transactino-api_1.1_spec-1.0.1-Beta1.jar was released specifically for the Infinispan team (JBEE-67). This request prompted a wider discussion of whether all API releases should be OSGi bundles. In the informal discussions I've participated in, sounded like a good idea. > Add LICENSE.txt to binary's META-INF > ------------------------------------ > > Key: JBEE-86 > URL: https://issues.jboss.org/browse/JBEE-86 > Project: JBoss JavaEE APIs > Issue Type: Task > Environment: jboss-transaction-api-1.0.1.GA.jar > Reporter: Pete Muir > > The jboss-transaction-api-1.0.1.GA.jar is missing this file, which is useful as it means a user can easily verify the licensing requirements for dependencies -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCL-179) backport the removal of the use of toLongString() from the line: throw new ClassNotFoundException(name + " from " + toLongString());

by Tom Fonteyne (JIRA)

backport the removal of the use of toLongString() from the line: throw new ClassNotFoundException(name + " from " + toLongString()); -------------------------------------------------------------------------------------------------------------------------------------- Key: JBCL-179 URL: https://issues.jboss.org/browse/JBCL-179 Project: JBoss ClassLoader Issue Type: Bug Components: ClassLoader Affects Versions: JBossCL.2.0.7.GA Environment: all Reporter: Tom Fonteyne Assignee: Ales Justin Priority: Minor Fix For: JBossCL.2.0.7.GA When a class is not found, the classloader code throws: ClassNotFoundException(name + " from " + toLongString()); The toLongString uses a lot of memory each time it's called. In 2.0.9 the line is using: ClassNotFoundException(name + " from " + toString()); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011