October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2127) Upgrade to RESTEasy 2.2.2

by Jozef Hartinger (Created) (JIRA)

Upgrade to RESTEasy 2.2.2 ------------------------- Key: AS7-2127 URL: https://issues.jboss.org/browse/AS7-2127 Project: Application Server 7 Issue Type: Feature Request Components: REST Affects Versions: 7.0.2.Final Reporter: Jozef Hartinger Assignee: Stuart Douglas Fix For: 7.1.0.CR1 This has been already done as part of AS7-1471 but has been subsequently reverted to 2.2.1.GA again. Git log message[1] indicates that this has been done as part of JBCTS-1075. I cannot see any direct relation between JBCTS-1075 and the version of RESTEasy on AS7 (perhaps a different issue?). Stuart, is there any chance to get 2.2.2.GA into AS7? [1] https://github.com/jbossas/jboss-as/commit/1ee0f8f2996ff9e7c32e88153da6f3... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
7
0 / 0

[JBoss JIRA] (AS7-2008) Tests must fail the build by default.

by Ondrej Zizka (Created) (JIRA)

Tests must fail the build by default. ------------------------------------- Key: AS7-2008 URL: https://issues.jboss.org/browse/AS7-2008 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Affects Versions: 7.1.0.Alpha1 Reporter: Ondrej Zizka Assignee: Ondrej Zizka -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

5
4
0 / 0

[JBoss JIRA] (LOGTOOL-36) Have the annotation processor output more information on invalid methods

by Sanne Grinovero (Created) (JIRA)

Have the annotation processor output more information on invalid methods ------------------------------------------------------------------------ Key: LOGTOOL-36 URL: https://issues.jboss.org/browse/LOGTOOL-36 Project: Log Tool Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Sanne Grinovero Assignee: James Perkins Priority: Minor If an error is logged like in {quote} [INFO] diagnostic error: All message bundles and message logger messageMethods must have or inherit a message. {quote} It would be nice to actually log to which method it's referring to. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
2
0 / 0

[JBoss JIRA] (JBAS-9450) Throwing exception annotated with @ApplicationException from bean with Bean-Managed transaction is causing exception to be wrapped in EJBException

by Martin Gold (Created) (JIRA)

Throwing exception annotated with @ApplicationException from bean with Bean-Managed transaction is causing exception to be wrapped in EJBException -------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-9450 URL: https://issues.jboss.org/browse/JBAS-9450 Project: Legacy JBoss Application Server 6 Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB Affects Versions: 6.1.0 Environment: Windows XP OS, JDK 1.6.0_15 Reporter: Martin Gold Assignee: Carlo de Wolf If exception (even if annotated with @ApplicationException) is thrown from stateless session bean with Bean-Managed transaction (@TransactionManagement(TransactionManagementType.BEAN)) then this exception is wrapped in EJBException. This does not happened in JBoss 6.0.0.Final and it is also not happening for beans with Container-managed transaction. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-1706) Handler change-file command fails every other time.

by Stan Silvert (JIRA)

Handler change-file command fails every other time. --------------------------------------------------- Key: AS7-1706 URL: https://issues.jboss.org/browse/AS7-1706 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.0.1.Final Reporter: Stan Silvert Assignee: David Lloyd The change-file command will fail with every other request. {code} [standalone@localhost:9999 periodic-rotating-file-handler=FILE] :read-resource { "outcome" => "success", "result" => { "append" => true, "autoflush" => true, "encoding" => undefined, "file" => { "path" => "server3.log", "relative-to" => undefined }, "formatter" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n", "level" => "INFO", "suffix" => ".yyyy-MM-dd" } } [standalone@localhost:9999 periodic-rotating-file-handler=FILE] :change-file(path=server4.log) { "outcome" => "failed", "failure-description" => "Operation handler failed to complete", "rolled-back" => true } [standalone@localhost:9999 periodic-rotating-file-handler=FILE] :change-file(path=server4.log) {"outcome" => "success"} [standalone@localhost:9999 periodic-rotating-file-handler=FILE] :read-resource { "outcome" => "success", "result" => { "append" => true, "autoflush" => true, "encoding" => "UTF-8", "file" => { "path" => "server4.log", "relative-to" => undefined }, "formatter" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n", "level" => "INFO", "suffix" => ".yyyy-MM-dd" } } {code} On the server console, you see: {code} 18:06:22,179 INFO [org.jboss.as.controller] (MSC service thread 1-5) Service status report New missing/unsatisfied dependencies: service jboss.logging.handler-file.FILE (missing) 18:06:27,050 INFO [org.jboss.as.controller] (pool-2-thread-53) Service status report Newly corrected services: service jboss.logging.handler-file.FILE (now available) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (AS7-738) Provide a JNDI View operation, similar to AS6

by Heiko Braun (JIRA)

Provide a JNDI View operation, similar to AS6 --------------------------------------------- Key: AS7-738 URL: https://issues.jboss.org/browse/AS7-738 Project: Application Server 7 Issue Type: Enhancement Components: Domain Management Reporter: Heiko Braun Assignee: Jason Greene -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
10
0 / 0

[JBoss JIRA] (JBJCA-687) AdminObject: javax.naming.Referenceable

by Jesper Pedersen (Created) (JIRA)

AdminObject: javax.naming.Referenceable --------------------------------------- Key: JBJCA-687 URL: https://issues.jboss.org/browse/JBJCA-687 Project: IronJacamar Issue Type: Bug Components: Deployer Affects Versions: 1.1.0.Alpha2, 1.0.5.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Critical Fix For: 1.0.6.Final, 1.1.0.Alpha3 If an AdminObject only implements javax.naming.Referenceable it isn't bound. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-952) Expose infinispan management operations

by Heiko Braun (JIRA)

Expose infinispan management operations --------------------------------------- Key: AS7-952 URL: https://issues.jboss.org/browse/AS7-952 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Affects Versions: 7.1.0.Beta1 Reporter: Heiko Braun Assignee: Brian Stansberry so we can include it in the console -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
4
0 / 0

[JBoss JIRA] (LOGTOOL-35) Processor fails to validate log messages defined in an inheriting interface

by Sanne Grinovero (Created) (JIRA)

Processor fails to validate log messages defined in an inheriting interface --------------------------------------------------------------------------- Key: LOGTOOL-35 URL: https://issues.jboss.org/browse/LOGTOOL-35 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR3 Reporter: Sanne Grinovero Assignee: James Perkins In both Infinispan and Hibernate we define a main logger in the core project, and extend this in each other module. In practice it looks like: {code:title="Main project"} @MessageLogger(projectCode = "ISPN") public interface Log extends BasicLogger { @LogMessage(level = WARN) @Message(value = "Field %s not found!!", id = 2) void fieldNotFound(String fieldName); ... {code} {code:title="Extending module"} @MessageLogger(projectCode = "ISPN") public interface Log extends org.infinispan.util.logging.Log { @LogMessage(level = ERROR) @Message(value = "Could not locate key class %s", id = 14001) void keyClassNotFound(String keyClassName, @Cause Exception e); ... {code} since the last release 1.0.0.CR3 all extending modules fail to build with the following error message: {quote} [INFO] diagnostic error: All message bundles and message logger messageMethods must have or inherit a message. [INFO] diagnostic error: All message bundles and message logger messageMethods must have or inherit a message. [INFO] diagnostic error: All message bundles and message logger messageMethods must have or inherit a message. [INFO] diagnostic error: All message bundles and message logger messageMethods must have or inherit a message. [many more..] {quote} So we had to rollback this dependency upgrade and stick with older versions. See also https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/268/or... caused by https://github.com/infinispan/infinispan/blob/master/query/src/main/java/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
5
0 / 0

[JBoss JIRA] (AS7-2214) NPE from the resolver when deploying bundle

by David Bosschaert (Created) (JIRA)

NPE from the resolver when deploying bundle ------------------------------------------- Key: AS7-2214 URL: https://issues.jboss.org/browse/AS7-2214 Project: Application Server 7 Issue Type: Bug Components: OSGi Affects Versions: 7.1.0.Beta1 Reporter: David Bosschaert Assignee: Thomas Diesler While I was in the process of getting the CXF DOSGi project to work on AS7 I found that a number of the resolver was throwing a NPE when a number of bundles were being deployed. An example bundle was the pax-web-service-0.5.1 bundle. Deploying that will cause the following exception: {code}11:23:01,920 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-8) Install bundle: org.ops4j.pax.web.service:0.5.1 11:23:01,942 ERROR [org.jboss.msc.service] (MSC service thread 1-8) MSC00002: Invocation of listener "org.jboss.as.osgi.deployment.BundleStartTracker$1@7fad5275" failed: java.lang.NullPointerException at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117) [jbosgi-resolver-felix-1.0.9.jar:1.0.9] at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148) [jbosgi-resolver-spi-1.0.9.jar:1.0.9] at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155) [jbosgi-framework-core-1.0.0.jar:1.0.0] at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) [jbosgi-framework-core-1.0.0.jar:1.0.0] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.0.0.jar:1.0.0] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.0.jar:1.0.0] at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144) [jboss-as-osgi-service-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119) [jboss-as-osgi-service-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1429) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:49) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1952) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:680) [:1.6.0_26] 11:23:01,959 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "pax-web-service-0.5.1.jar"{code} Also note that the bundle is still marked as successfully deployed, which is probably not correct. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

5
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2011