January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3480) security-domain in jboss-ejb3.xml is not recognized for EJB-Jars packaged inside a WAR

by Robert Reimann (JIRA)

Robert Reimann created AS7-3480: ----------------------------------- Summary: security-domain in jboss-ejb3.xml is not recognized for EJB-Jars packaged inside a WAR Key: AS7-3480 URL: https://issues.jboss.org/browse/AS7-3480 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.0.CR1b Reporter: Robert Reimann Assignee: jaikiran pai The jboss-ejb3.xml descriptor is not recognized when placed inside META-INF of an EJB-Jar that is packaged inside a WAR. -- 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

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] (AS7-2998) Lock down the ability to set/reset EJB client context selector on the server side by user code

by jaikiran pai (Created) (JIRA)

Lock down the ability to set/reset EJB client context selector on the server side by user code ---------------------------------------------------------------------------------------------- Key: AS7-2998 URL: https://issues.jboss.org/browse/AS7-2998 Project: Application Server 7 Issue Type: Task Components: EJB Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 7.1.0.CR1 On the server side we shouldn't allow setting/resetting the EJB client context selector, by the user code. An API to lock down setting the selector is being added in the next version of EJB client API. The server should use that API to lock down the selector once it has setup the server wide selector. Creating this as a task for 7.1.0.CR1 so as to not forget adding this implementation. -- 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

14 years, 3 months

4
4
0 / 0

[JBoss JIRA] (AS7-2343) Remove dependency on rhq plugin annotations

by Paul Gier (Created) (JIRA)

Remove dependency on rhq plugin annotations ------------------------------------------- Key: AS7-2343 URL: https://issues.jboss.org/browse/AS7-2343 Project: Application Server 7 Issue Type: Enhancement Components: Build System, Clustering Reporter: Paul Gier Assignee: Manik Surtani The AS 7 build currently pulls in a transitive dependency on the artifact org.rhq.helpers:rhq-pluginAnnotations:jar:3.0.1. This jar is not included in the AS zip, and the dependency should be removed from the build. However, just excluding this dependency causes a compile error in the infinispan module, so some of the source probably needs to be changed. {quote} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project jboss-as-clustering-infinispan: Compilation failure [ERROR] Failure executing javac, but could not parse the error: [ERROR] org/infinispan/manager/DefaultCacheManager.class(org/infinispan/manager:DefaultCacheManager.class): warning: Cannot find annotation method 'displayName()' in type 'org.rhq.helpers.pluginAnnotations.agent.Metric': class file for org.rhq.helpers.pluginAnnotations.agent.Metric not found [ERROR] org/infinispan/manager/DefaultCacheManager.class(org/infinispan/manager:DefaultCacheManager.class): warning: Cannot find annotation method 'dataType()' in type 'org.rhq.helpers.pluginAnnotations.agent.Metric' [ERROR] An exception has occurred in the compiler (1.6.0_20). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you. [ERROR] com.sun.tools.javac.code.Symbol$CompletionFailure: class file for org.rhq.helpers.pluginAnnotations.agent.DataType not found {quote} -- 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

14 years, 3 months

9
12
0 / 0

[JBoss JIRA] (AS7-2634) SessionBeanComponentDescriptionFactory silently ignores EJBs declared in ejb-jar.xml

by Richard Opalka (Created) (JIRA)

SessionBeanComponentDescriptionFactory silently ignores EJBs declared in ejb-jar.xml ------------------------------------------------------------------------------------ Key: AS7-2634 URL: https://issues.jboss.org/browse/AS7-2634 Project: Application Server 7 Issue Type: Bug Components: EJB Reporter: Richard Opalka Assignee: Carlo de Wolf Fix For: 7.1.0.CR1 If I'm trying to provide another EJB in ejb-jar.xml that is using different name than the name derived from its class (I'm trying to provide multiple EJBs based on same class with different names), my bean is silently ignored by the following piece of code: {code:title=SessionBeanComponentDescriptionFactory.java|borderStyle=solid} ... final SessionType sessionType = sessionBean.getSessionType(); if(sessionType == null && sessionBean instanceof GenericBeanMetaData) { //TODO: this is a hack return; } ... {code} The code should * either detect bean type according to its associated class annotation (@Singleton, @Stateless) for EJB3 beans * or print warning or throw exception that <session-type> must be provided in ejb-jar.xml descriptor for EJB21 endpoints -- 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

14 years, 3 months

9
8
0 / 0

[JBoss JIRA] (AS7-669) Missing error message for composite operations

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-669?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry reassigned AS7-669: ------------------------------------ Assignee: Tomaz Cerar (was: Brian Stansberry) Tomaz, reading this it sounds very similar to the other HTTP API issue you have assigned. > Missing error message for composite operations > ---------------------------------------------- > > Key: AS7-669 > URL: https://issues.jboss.org/browse/AS7-669 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.0.0.Beta3 > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Labels: eap6-ux > Fix For: 7.1.0.Final > > > Heiko Braun reports: > I don't see any error details when composite op's fail. > Is it just me or a general problem? > Request > { > "operation" => "composite", > "address" => [], > "steps" => [ > { > "operation" => "write-attribute", > "address" => [ > ("host" => "local"), > ("server-config" => "server-one") > ], > "name" => "socket-binding-group", > "value" => "standard-sockets" > }, > { > "operation" => "write-attribute", > "address" => [ > ("host" => "local"), > ("server-config" => "server-one") > ], > "name" => "socket-binding-port-offset", > "value" => 0 > } > ], > "child-type" => undefined > } > > Response > > Internal Server Error -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-2661) Build Number needs to be inserted into the build process so people can know which version they have

by Jim Tyrrell (Created) (JIRA)

Build Number needs to be inserted into the build process so people can know which version they have --------------------------------------------------------------------------------------------------- Key: AS7-2661 URL: https://issues.jboss.org/browse/AS7-2661 Project: Application Server 7 Issue Type: Feature Request Components: Build System Reporter: Jim Tyrrell Assignee: Paul Gier I found a few issues, and developers asked for what version I am using. In the response it was discovered there is no way to grab the "version" of what was built. It would be great to inject a build time, and the version of the current git repo in some file somewhere. Might it be a good idea to grab and label all of the projects that make up the release. Support might want this information also. -- 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

14 years, 3 months

4
3
0 / 0

[JBoss JIRA] (AS7-3485) Transient deadlocking in StatefulFailoverTestCase and SingletonServiceTestCase

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-3485: --------------------------------- Summary: Transient deadlocking in StatefulFailoverTestCase and SingletonServiceTestCase Key: AS7-3485 URL: https://issues.jboss.org/browse/AS7-3485 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.0.CR1b Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical Fix For: 7.1.0.Final Attachments: org.jboss.as.test.clustering.unmanaged.ejb3.stateful.StatefulFailoverTestCase-output.txt, org.jboss.as.test.clustering.unmanaged.singleton.SingletonTestCase-output.txt Seems to be a race condition when we try to perform cache operations within a view change event. Logs attached. -- 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

14 years, 3 months

1
2
0 / 0

[JBoss JIRA] (JBRULES-3362) Declared types formatting error not detected at compile time

by James Walker (JIRA)

James Walker created JBRULES-3362: ------------------------------------- Summary: Declared types formatting error not detected at compile time Key: JBRULES-3362 URL: https://issues.jboss.org/browse/JBRULES-3362 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core, drools-eclipse Affects Versions: 5.4.0.Beta1 Reporter: James Walker Assignee: Mark Proctor If you declare a type like this: {noformat} declare Wrapper Text: String #Field name starts with a capital letter - not a java bean! metrics : Metrics end {noformat} It doesn't notice it at compile time or in the eclipse plugin, but errors at run-time. -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3361) Salience format error (Salience - 150) so

by James Walker (JIRA)

James Walker created JBRULES-3361: ------------------------------------- Summary: Salience format error (Salience - 150) so Key: JBRULES-3361 URL: https://issues.jboss.org/browse/JBRULES-3361 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: James Walker Assignee: Mark Proctor -- 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

14 years, 3 months

1
1
0 / 0

[JBoss JIRA] (AS7-3484) Update OSGi Core Framework to 1.1.x

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-3484: ----------------------------------- Summary: Update OSGi Core Framework to 1.1.x Key: AS7-3484 URL: https://issues.jboss.org/browse/AS7-3484 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.0.Final -- 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

14 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 January 2012