July 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-58) Handler rollback gets null instance reference if prepare are invoked

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-58?page=com.atlassian.jira.plugin.... ] James Perkins updated LOGMGR-58: -------------------------------- Fix Version/s: 1.4.2.Final > Handler rollback gets null instance reference if prepare are invoked > -------------------------------------------------------------------- > > Key: LOGMGR-58 > URL: https://issues.jboss.org/browse/LOGMGR-58 > Project: JBoss Log Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > Fix For: 1.4.2.Final, 1.5.0.Beta1, 2.0.0.Beta1 > > > When a forget/rollback is executed after a prepare the instance has already been removed from the refs. The reference should be held so that it can added back to the refs. > The least evasive solution is to not invoke the {{applyPostCreate()}} in the prepare. This will require examination of all implementations to make sure values are set, but references are not removed in this phase. > The other option would be to add a commit step only invoked from the commit phase where references could be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1733) Add subtree views to CLI GUI

by Stan Silvert (JIRA)

Stan Silvert created WFLY-1733: ---------------------------------- Summary: Add subtree views to CLI GUI Key: WFLY-1733 URL: https://issues.jboss.org/browse/WFLY-1733 Project: WildFly Issue Type: Feature Request Components: CLI Affects Versions: 8.0.0.Alpha3 Reporter: Stan Silvert Assignee: Stan Silvert Fix For: 8.0.0.Beta1 For installations with a large management model, it can be difficult to navigate the tree in CLI GUI. This is especially true in a domain model with many hosts and profiles. We need to add the ability to create new tabs that lets you view sub-trees. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBEE-135) JAXWS SPI Provider should use ServiceLoader within a privileged block

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-135?page=com.atlassian.jira.plugin.s... ] Shelly McGowan commented on JBEE-135: ------------------------------------- https://github.com/jboss/jboss-jaxws-api_spec/pull/3 has been merged. I'll perform a Beta2 release with this change. > JAXWS SPI Provider should use ServiceLoader within a privileged block > --------------------------------------------------------------------- > > Key: JBEE-135 > URL: https://issues.jboss.org/browse/JBEE-135 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jaxws-api > Reporter: Alessio Soldano > Assignee: Alessio Soldano > > The JAXWS SPI Provider uses ServiceLoader to look for user specified provider implementations. The search is performed using the current TCCL. > When iterating on the ServiceLoader results, read permission on the relevant jar is required. It looks correct to run in a privileged block there, also considering that the user would need a permission for setting/changing the TCCL. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1406) Hibernate cannot process package-info.java any more

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-1406?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-1406: ------------------------------------ Which is your preferred environment for debugging? Perhaps Eclipse, Intellij or JDB? If you were using Intellij, you would: 1. Click on File/Open... menu and navigate to the pom.xml file in the root of the WildFly source tree. Wait a while for the project to be opened. 2. While the project is being loaded, start the WildFly server with options: standalone.bat --debug 8787 3. After the WildFly project is loaded into Intellij, open the Run/Edit Configurations... menu and add a remote entry for debugging, with port set to 8787. 4. You should be able to start the debugger by clicking on Run/Debug... and choose the default that you create/update in step #3. This will attach to the running WildFly server for debugging. 5. Copy the exception call stack to the clipboard that you get for the "package-info". 6. Open menu Analyze/AnalyzeStackTrace and past the clipboard contents if not already done for you. When you click on one of the source modules mentioned in the exception call stack, the source file should open, from which you can do standard java debugging (set a breakpoint at a line) and investigate. You should be able to open sources for most app server projects. Hope this helps. Scott > Hibernate cannot process package-info.java any more > --------------------------------------------------- > > Key: WFLY-1406 > URL: https://issues.jboss.org/browse/WFLY-1406 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: 8.0.0.Alpha2 > Reporter: Juergen Zimmermann > Attachments: javap.log, server.log, server.log.zip, shop2.war, tar.log > > > I tried the snapshot which contains Hibernate 4.3.0.Beta2. However, package-info.java files are causing problems. For instance, the package de.shop.artikelverwaltung.domain has a package-info.java which causes a NoClassDefFoundError: > "IllegalName: de/shop/artikelverwaltung/domain.package-info". Please see the stacktrace below. > Here is an example for package-info.java which was working with WildFly 8.0.0.Alpha1: > @XmlAccessorType(FIELD) > @Vetoed > package de.shop.artikelverwaltung.domain; > import static javax.xml.bind.annotation.XmlAccessType.FIELD; > import javax.enterprise.inject.Vetoed; > import javax.xml.bind.annotation.XmlAccessorType; > The stacktrace: > ... > 09:29:53,880 WARN [org.jboss.modules] Failed to define class de/shop/artikelverwaltung/domain.package-info in Module "deployment.shop2.war:main" from Service Module Loader: java.lang.LinkageError: Failed to link de/shop/artikelverwaltung/domain/package-info (Module "deployment.shop2.war:main" from Service Module Loader) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:427) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:260) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:75) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.Module.loadModuleClass(Module.java:526) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:188) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final] > at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader.findClass(ClassLoaderServiceImpl.java:218) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2] > at java.lang.ClassLoader.loadClass(ClassLoader.java:423) [rt.jar:1.7.0_21] > at java.lang.ClassLoader.loadClass(ClassLoader.java:356) [rt.jar:1.7.0_21] > at org.hibernate.annotations.common.util.ReflectHelper.classForName(ReflectHelper.java:160) [hibernate-commons-annotations-4.0.2.Final.jar:4.0.2.Final] > at org.hibernate.annotations.common.reflection.java.JavaReflectionManager.packageForName(JavaReflectionManager.java:121) [hibernate-commons-annotations-4.0.2.Final.jar:4.0.2.Final] > at org.hibernate.cfg.AnnotationBinder.bindPackage(AnnotationBinder.java:262) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.cfg.Configuration.addPackage(Configuration.java:792) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.buildHibernateConfiguration(EntityManagerFactoryBuilderImpl.java:1174) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:839) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:836) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:368) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:835) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.jpa.HibernatePersistenceProvider.createContainerEntityManagerFactory(HibernatePersistenceProvider.java:142) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:213) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$800(PersistenceUnitServiceImpl.java:58) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:107) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final] > Caused by: java.lang.NoClassDefFoundError: IllegalName: de/shop/artikelverwaltung/domain.package-info > at java.lang.ClassLoader.preDefineClass(ClassLoader.java:646) [rt.jar:1.7.0_21] > at java.lang.ClassLoader.defineClass(ClassLoader.java:785) [rt.jar:1.7.0_21] > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:344) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:422) [jboss-modules.jar:1.2.0.Final] > ... 28 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1732) :read-children-resources returns ModelType.OBJECT

by Heiko Braun (JIRA)

Heiko Braun created WFLY-1732: --------------------------------- Summary: :read-children-resources returns ModelType.OBJECT Key: WFLY-1732 URL: https://issues.jboss.org/browse/WFLY-1732 Project: WildFly Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry IMO it should return ModelType.LIST -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1628) alias --help print nothing on jboss-cli

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1628?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1628: ----------------------------------------------- pkremens(a)redhat.com made a comment on [bug 980099|https://bugzilla.redhat.com/show_bug.cgi?id=980099] I see :), than something like this would be IMO sufficient. > alias --help print nothing on jboss-cli > --------------------------------------- > > Key: WFLY-1628 > URL: https://issues.jboss.org/browse/WFLY-1628 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.0.Alpha2 > Environment: MacOS X, JDK 1.7.0_09 > Reporter: Alexis Hassler > Assignee: Alexey Loubyansky > > I have no output when I call this : > [standalone@localhost:9990 /] alias --help > [standalone@localhost:9990 /] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1628) alias --help print nothing on jboss-cli

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1628?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1628: ----------------------------------------------- Ståle W. Pedersen <spederse(a)redhat.com> made a comment on [bug 980099|https://bugzilla.redhat.com/show_bug.cgi?id=980099] yes, i know it doesnt support -p and more that one alias on a single line, it was more meant as a general help msg example. - ill try to implement that though later :) > alias --help print nothing on jboss-cli > --------------------------------------- > > Key: WFLY-1628 > URL: https://issues.jboss.org/browse/WFLY-1628 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.0.Alpha2 > Environment: MacOS X, JDK 1.7.0_09 > Reporter: Alexis Hassler > Assignee: Alexey Loubyansky > > I have no output when I call this : > [standalone@localhost:9990 /] alias --help > [standalone@localhost:9990 /] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-193) KnowledgeBuilderResult does not always contain a Resource

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-193?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-193. -------------------------------- Fix Version/s: 6.0.0.CR1 Resolution: Done > KnowledgeBuilderResult does not always contain a Resource > --------------------------------------------------------- > > Key: DROOLS-193 > URL: https://issues.jboss.org/browse/DROOLS-193 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michael Anstis > Assignee: Mario Fusco > Fix For: 6.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1628) alias --help print nothing on jboss-cli

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1628?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1628: ----------------------------------------------- pkremens(a)redhat.com made a comment on [bug 980099|https://bugzilla.redhat.com/show_bug.cgi?id=980099] Hi, this will not work, there is no [-p] option and I wasn't able to add more aliases on single line eg. alias cd="cd subsystem=logging" ls="ls -l" creates alias cd='cd subsystem=logging" ls="ls -l' not alias cd='cd subsystem=logging' alias ls='ls -l' > alias --help print nothing on jboss-cli > --------------------------------------- > > Key: WFLY-1628 > URL: https://issues.jboss.org/browse/WFLY-1628 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.0.Alpha2 > Environment: MacOS X, JDK 1.7.0_09 > Reporter: Alexis Hassler > Assignee: Alexey Loubyansky > > I have no output when I call this : > [standalone@localhost:9990 /] alias --help > [standalone@localhost:9990 /] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1628) alias --help print nothing on jboss-cli

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1628?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1628: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=980099 > alias --help print nothing on jboss-cli > --------------------------------------- > > Key: WFLY-1628 > URL: https://issues.jboss.org/browse/WFLY-1628 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.0.Alpha2 > Environment: MacOS X, JDK 1.7.0_09 > Reporter: Alexis Hassler > Assignee: Alexey Loubyansky > > I have no output when I call this : > [standalone@localhost:9990 /] alias --help > [standalone@localhost:9990 /] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 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 July 2013