March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9028) JARs with OSGi metadata cannot be used by EE

by David Lloyd (JIRA)

JARs with OSGi metadata cannot be used by EE -------------------------------------------- Key: JBAS-9028 URL: https://issues.jboss.org/browse/JBAS-9028 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Lloyd Priority: Critical Fix For: 7.0.0.Beta3 If a JAR such as a JDBC driver or other service provider (like MSC ServiceActivation) is deployed, and that JAR happens to have OSGi metadata on it, the deployment is invisible to, or incompatible with, most of the other deployers which actually enable these services, usually on behalf of one or more subsystems. We need OSGi JARs to coexist on at least some level. A first step might be to have OSGi's modularization process use the same attachment set so that modules and resource roots can reliably be found in the DU attachments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

6
10
0 / 0

[JBoss JIRA] (JBRULES-3421) FireAllRulesCommand NPE when outIdentifier != null

by Mike Melton (JIRA)

Mike Melton created JBRULES-3421: ------------------------------------ Summary: FireAllRulesCommand NPE when outIdentifier != null Key: JBRULES-3421 URL: https://issues.jboss.org/browse/JBRULES-3421 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.4.0.Beta1, 5.3.1.Final Reporter: Mike Melton Assignee: Mark Proctor Priority: Minor See mailing list post for full details: http://drools.46999.n3.nabble.com/rules-users-NPE-in-FireAllRulesCommand-... The short version is that if you execute a BatchExecutionCommand containing a FireAllRulesCommand which itself has a non-null outIdentifier, a NPE is thrown due to the expression "(ExecutionResultImpl) ((KnowledgeCommandContext) context).getExecutionResults()" returning null. This is because the context object which is passed into the execute method contains a null results object. I have written unit tests demonstrating the problem and have coded a fix which differs from my suggestion in the mailing list post in that it is confined to FireAllRulesCommand.java (i.e., it doesn't touch StatelessKnowledgeSessionImpl.java). I will attach a basic unit test to this issue and submit a pull request with both more thorough tests and the fix. -- 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, 1 month

2
5
0 / 0

[JBoss JIRA] (AS7-3287) Admin console: deploying a datasource should trigger 'server reload is required'

by Jan Martiska (JIRA)

Jan Martiska created AS7-3287: --------------------------------- Summary: Admin console: deploying a datasource should trigger 'server reload is required' Key: AS7-3287 URL: https://issues.jboss.org/browse/AS7-3287 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Heiko Braun Deploying a datasource should trigger 'server reload is required' message and require a server reload. It is necessary for example for the datasource to appear in the JNDI naming list. Editing an existing datasource triggers this, but creation does not. -- 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, 1 month

5
10
0 / 0

[JBoss JIRA] (AS7-4130) AS 7 quickstart: Wicket + JPA

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-4130: --------------------------------- Summary: AS 7 quickstart: Wicket + JPA Key: AS7-4130 URL: https://issues.jboss.org/browse/AS7-4130 Project: Application Server 7 Issue Type: Feature Request 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

14 years, 1 month

1
6
0 / 0

[JBoss JIRA] (JBRULES-3426) Refactor threads usage in drools using a centralized and pluggable ExecutorService

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3426: ------------------------------------ Summary: Refactor threads usage in drools using a centralized and pluggable ExecutorService Key: JBRULES-3426 URL: https://issues.jboss.org/browse/JBRULES-3426 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBEE-73) Create a uber-jar for the JBoss JavaEE APIs

by Aslak Knutsen (JIRA)

Create a uber-jar for the JBoss JavaEE APIs ------------------------------------------- Key: JBEE-73 URL: https://issues.jboss.org/browse/JBEE-73 Project: JBoss JavaEE APIs Issue Type: Feature Request Components: javaee_6.0_spec Affects Versions: 1.0.0.Final-javaee_6.0 Reporter: Aslak Knutsen Assignee: Shelly McGowan My Windows users are having problems.. Windows has a limitation on how long the ClassPath can be, when you start to include libraries like, jbossas-client(249 deps) and jboss-javaee-6.0 (x) windows refuse to execute the java process. http://community.jboss.org/message/586381#586381 Would it be possible to release a uber-jar v. of the jboss-javaee-6.0 pom? Basically merge it into one artifact. Most users don't care about the individual specs, they use EE. And as long as the pom is there as well, they have both options. <dependency> <groupId>org.jboss.spec</groupId> <artifactId>jboss-javaee-6.0-all</artifactId> <-- using a different artifact id is probably easier to setup --> <version>1.0.0.Final</version> <type>jar</type> <-- a single jar --> </dependency> http://maven.apache.org/plugins/maven-shade-plugin/ ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

8
10
0 / 0

[JBoss JIRA] (AS7-4208) Inconsistent behaviour when dealing with resteasy scanning context params

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-4208: ----------------------------------- Summary: Inconsistent behaviour when dealing with resteasy scanning context params Key: AS7-4208 URL: https://issues.jboss.org/browse/AS7-4208 Project: Application Server 7 Issue Type: Bug Components: REST Affects Versions: 7.1.1.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.1.2.Final Some of the early code uses these parameters to set scanning info, while a later dup prints a log message saying they have been ignored. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] (JBEE-96) Configure each spec to be an OSGi bundle

by Paul Gier (Created) (JIRA)

Configure each spec to be an OSGi bundle ---------------------------------------- Key: JBEE-96 URL: https://issues.jboss.org/browse/JBEE-96 Project: JBoss JavaEE Spec APIs Issue Type: Enhancement Components: general Reporter: Paul Gier Assignee: Paul Gier Fix For: JavaEE 6 Spec APIs 1.0.0 All the specs builds should be configured to produce a jar that is a valid OSGi bundle. -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] (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 closed JBEE-86. ------------------------- Resolution: Done License file has been added to each spec jars META-INF directory. > Add LICENSE.txt to binary's META-INF > ------------------------------------ > > Key: JBEE-86 > URL: https://issues.jboss.org/browse/JBEE-86 > Project: JBoss JavaEE Spec APIs > Issue Type: Task > Components: general > Environment: jboss-transaction-api-1.0.1.GA.jar > Reporter: Pete Muir > Assignee: Paul Gier > Fix For: JavaEE 6 Spec APIs 3.0.0 > > > 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. 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, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4191) System hang on statement: TransactionManagerDelegate delegate = (TransactionManagerDelegate) initCtx.lookup("java:jboss/TransactionManager");

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-4191?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-4191. --------------------------------- Resolution: Out of Date Given how long ago this was filed and the lack of info on how to reproduce I am marking this as out of date. > System hang on statement: TransactionManagerDelegate delegate = (TransactionManagerDelegate) initCtx.lookup("java:jboss/TransactionManager"); > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: AS7-4191 > URL: https://issues.jboss.org/browse/AS7-4191 > Project: Application Server 7 > Issue Type: Bug > Environment: jboss-as-7.0.0.Final > Java(TM) SE Runtime Environment (build 1.6.0_26-b03) > Linux omega 2.6.32-33-generic-pae #70-Ubuntu SMP Thu Jul 7 22:51:12 UTC 2011 i686 GNU/Linux > Reporter: JEE 4 Hire > > import com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate; > System hang on statement: TransactionManagerDelegate delegate = (TransactionManagerDelegate) initCtx.lookup("java:jboss/TransactionManager"); -- 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, 1 month

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 March 2012