April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2920) Build: Rewrite assemblies to deal with split-up, include javadocs and are run by simply doing "mvn -Dfull install" (no need for javadocs:javadocs or assembly:assembly goals)

by Geoffrey De Smet (JIRA)

Build: Rewrite assemblies to deal with split-up, include javadocs and are run by simply doing "mvn -Dfull install" (no need for javadocs:javadocs or assembly:assembly goals) ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2920 URL: https://issues.jboss.org/browse/JBRULES-2920 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Blocker Fix For: 5.2.0.M2 -Dfull install builds assemblies groupId's should be corrected javadocs can be done in a normal "-Dfull install", see modeshape or ask john casey when rdy, send a mail to dpalmer to poke him to look at the newest assemblies -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBLOGGING-62) Contribute to SLF4J API

by Hendy Irawan (JIRA)

Contribute to SLF4J API ----------------------- Key: JBLOGGING-62 URL: https://issues.jboss.org/browse/JBLOGGING-62 Project: JBoss Logging Issue Type: Enhancement Security Level: Public (Everyone can see) Components: jboss-logging-spi Affects Versions: 3.0.0.Beta4-jboss-logging Reporter: Hendy Irawan Assignee: David Lloyd I do see merits in JBoss Logging when compared to SLF4J. However I would love the JBoss Logging team to contribute directly and influence the direction of SLF4J (the API, not implementation) than to create a competing API (of which there are overlap, and JBoss Logging adds some powerful features to the API, like internationalization and more). JBoss Logging can still retain its own logging implementation, much like the way Logback is the implementation of SLF4J API. My suggestion is that the JBoss should submit API improvements to SLF4J, so that on the API level it everybody can use the same rich API that JBoss Logging provided in SLF4J. This would benefit both JBoss and SLF4J communities. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-9305) ARQ tests using ArchiveDeployer may hang in deployment API

by Thomas Diesler (JIRA)

ARQ tests using ArchiveDeployer may hang in deployment API ---------------------------------------------------------- Key: JBAS-9305 URL: https://issues.jboss.org/browse/JBAS-9305 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-9088) Prevent concurrent conflicting write requests to the management model

by Brian Stansberry (JIRA)

Prevent concurrent conflicting write requests to the management model --------------------------------------------------------------------- Key: JBAS-9088 URL: https://issues.jboss.org/browse/JBAS-9088 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management, EJB2 Reporter: Brian Stansberry Fix For: 7.0.0.Beta3 The way the ModelControllers works makes it easy to support concurrent reads or reads occurring concurrently with writes. Reads get their own copy of the model; writes aren't reflected in the underlying model until the operation handler returns. But we need proper support for dealing with concurrent writes. Currently if two write execute concurrently, the "last one wins" i.e. its updated model gets written into the actual model, perhaps overwriting the changes made by earlier updates. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-9178) Ability to specify config file from the command line

by Brian Stansberry (JIRA)

Ability to specify config file from the command line ---------------------------------------------------- Key: JBAS-9178 URL: https://issues.jboss.org/browse/JBAS-9178 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta4 The standalone server and ProcessController/HostController main methods should take a switch specifying the name of the config file to use (files, in the case of ProcessController/HostController), with "standalone.xml", "host.xml" and "domain.xml" being the default. This allows things like devs having different standalone mode profiles configured and switching between them, multiple host configs in a production distribution with environment variables on different hosts causing the right one to be used, etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
6
0 / 0

[JBoss JIRA] Assigned: (JBRULES-2961) Invalid org.drools.eclipse plugin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2961?page=com.atlassian.jira.plug... ] Nick Boldt reassigned JBRULES-2961: ----------------------------------- Assignee: Geoffrey De Smet (was: Nick Boldt) Assigning to Geoffrey as he handles builds for Drools now. > Invalid org.drools.eclipse plugin > --------------------------------- > > Key: JBRULES-2961 > URL: https://issues.jboss.org/browse/JBRULES-2961 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-eclipse > Affects Versions: 5.2.0.M2 > Environment: 3.2_stable_branch.2011-04-15_00-38-24-H707 > Reporter: Snjezana Peco > Assignee: Geoffrey De Smet > > The org.drools.eclipse_5.2.0.201104120641 plugin isn't built correctly. It is about 57 mb big (org.drools.eclipse_5.2.0.v20110116-0638-H14 is about 8MB) and includes all required eclipse plugins in the lib directory. > It doesn't export the org.drools.eclipse.util package. See JBIDE-8730. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBRULES-2961) Invalid org.drools.eclipse plugin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2961?page=com.atlassian.jira.plug... ] Nick Boldt moved JBIDE-8740 to JBRULES-2961: -------------------------------------------- Project: Drools (was: Tools (JBoss Tools)) Key: JBRULES-2961 (was: JBIDE-8740) Affects Version/s: 5.2.0.M2 (was: 3.2.1) Component/s: drools-eclipse (was: Build/Releng) Security: Public > Invalid org.drools.eclipse plugin > --------------------------------- > > Key: JBRULES-2961 > URL: https://issues.jboss.org/browse/JBRULES-2961 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-eclipse > Affects Versions: 5.2.0.M2 > Environment: 3.2_stable_branch.2011-04-15_00-38-24-H707 > Reporter: Snjezana Peco > Assignee: Nick Boldt > > The org.drools.eclipse_5.2.0.201104120641 plugin isn't built correctly. It is about 57 mb big (org.drools.eclipse_5.2.0.v20110116-0638-H14 is about 8MB) and includes all required eclipse plugins in the lib directory. > It doesn't export the org.drools.eclipse.util package. See JBIDE-8730. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9282) transactional entity manager can close persistence context when invoked outside of a transaction (since there is no state kept)

by Scott Marlow (JIRA)

transactional entity manager can close persistence context when invoked outside of a transaction (since there is no state kept) ------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-9282 URL: https://issues.jboss.org/browse/JBAS-9282 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.0.Beta3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1166) jta-data-source / non-jta-data-source

by Jesper Pedersen (JIRA)

jta-data-source / non-jta-data-source ------------------------------------- Key: EJBTHREE-1166 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1166 Project: EJB 3.0 Issue Type: Bug Environment: JBoss AS: SVN / trunk (rev 68402) jboss-ejb3-cache version="0.11.1" jboss/jboss-ejb3-ext-api version="0.1.2.Beta1" jboss/jboss-ejb3-impl version="0.1.2.Beta1" Reporter: Jesper Pedersen I get the following: persistence.units:ear=rasp-sender.ear,unitName=e-akten-test -> java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named: e-akten-test persistence.units:ear=rasp-sender.ear,unitName=e-akten -> java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a jta-data-source for a JTA enabled persistence context named: e-akten The EJB3 persistence spec section 6.2.1.5 states: "In Java EE environments, the jta-data-source and non-jta-data-source elements are used to specify the global JNDI name of the JTA and/or non-JTA data source to be used by the persistence provider. If neither is speciﬁed, the deployer must specify a JTA data source at deployment or a JTA data source must be provided by the container, and a JTA EntityManagerFactory will be created to cor- respond to it." I'm counting on the last case -- data source must be provided by container + entity manager. Hope this helps ! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBJCA-551) Thread pools not stopped

by Jesper Pedersen (JIRA)

Thread pools not stopped ------------------------ Key: JBJCA-551 URL: https://issues.jboss.org/browse/JBJCA-551 Project: IronJacamar Issue Type: Bug Components: Standalone Affects Versions: 1.0.0.Beta5 Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta6 The thread pools in standalone/embedded mode aren't shutdown'ed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
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 April 2011