May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9321) Upgrade to Hibernate 3.6.4

by Scott Marlow (JIRA)

Upgrade to Hibernate 3.6.4 --------------------------- Key: JBAS-9321 URL: https://issues.jboss.org/browse/JBAS-9321 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (AS7-914) Expose Ws endpoint in standalone mode

by Heiko Braun (JIRA)

Expose Ws endpoint in standalone mode ------------------------------------- Key: AS7-914 URL: https://issues.jboss.org/browse/AS7-914 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8775) Too aggressive annotation scanning of classes by WarAnnotationMetaDataDeployer leads to incorrect metadata being created

by jaikiran pai (JIRA)

Too aggressive annotation scanning of classes by WarAnnotationMetaDataDeployer leads to incorrect metadata being created ------------------------------------------------------------------------------------------------------------------------- Key: JBAS-8775 URL: https://issues.jboss.org/browse/JBAS-8775 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Reporter: jaikiran pai The WarAnnotationMetaDataDeployer scans all the classes for Java EE resource injection annotations. The spec specifies only a certain "type" of classes in a web-app which are eligible for resource injection. Annotation scanning of unwanted classes in the web-app leads to an incorrect Environment metadata being created for JBossWebMetaData. (More details to follow in subsequent replies and forum posts, after the holidays :) ) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2229) Multiple timer instances get created for persistent auto timers

by jaikiran pai (JIRA)

Multiple timer instances get created for persistent auto timers --------------------------------------------------------------- Key: EJBTHREE-2229 URL: https://issues.jboss.org/browse/EJBTHREE-2229 Project: EJB 3.0 Issue Type: Bug Components: timerservice-mk2 Affects Versions: depchain-1.0.0-alpha-43 Reporter: jaikiran pai Assignee: jaikiran pai Creation/re-creation of persistent auto-timers needs to be revisited to avoid creating multiple instances of already existing auto timers. See the following forum threads for potential problems: http://community.jboss.org/message/579043#579043 http://community.jboss.org/message/562006#562006 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8683) CDI Extensions not discovered in EAR structure

by Heiko Braun (JIRA)

CDI Extensions not discovered in EAR structure ---------------------------------------------- Key: JBAS-8683 URL: https://jira.jboss.org/browse/JBAS-8683 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Weld/CDI Affects Versions: 6.0.0.CR1 Reporter: Heiko Braun Assignee: Marius Bogoevici A web application contains a CDI extension shipped within WEB-INF/lib. If this web application is packaged in an EAR, the extension will not be discovered and executed. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

12
27
0 / 0

[JBoss JIRA] Created: (AS7-856) Replace -DskipTests=true with -DallTests

by Thomas Diesler (JIRA)

Replace -DskipTests=true with -DallTests ---------------------------------------- Key: AS7-856 URL: https://issues.jboss.org/browse/AS7-856 Project: Application Server 7 Issue Type: Task Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.0.0.CR1 Using skipTests as a flag has a negative side effect such that you cannot do > mvn -Dtest=SomeTestCase test in an integration module any more. Instead you have to do > mvn -DskipTests=false -Dtest=SomeTestCase test This is non-intuitive and non-standard. Instead I propose to use an alternate switch like 'allTests' to turn on profiles which run the complete set of tests. IMHO its ok to exclude entire (testsuite) modules from the build (i.e. not to compile the tests) because compilation errors show up in the IDE and Hudson anyway. I propose 1) By default, all normal modules and testsuite/smoke will be built in the standard way (i.e. failing tests will fail the build) 2) By adding -DskipTests=true tests that would normally be executed are skipped 3) By adding -DallTests all modules that contain tests will be executed. In Hudson you could add -fae which fails the build at the end - so catch all failing tests in a single run It boils down to whether you want to compile tests that you don't want to execute. IMHO that's not necessary in day to day work - Hudson can catch this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (AS7-891) Failed to enable datasource ("generate more then one cf")

by Heiko Braun (JIRA)

Failed to enable datasource ("generate more then one cf") --------------------------------------------------------- Key: AS7-891 URL: https://issues.jboss.org/browse/AS7-891 Project: Application Server 7 Issue Type: Bug Components: JCA Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.0.0.CR1 18:40:07,600 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.data-source.java:/H2DS: org.jboss.msc.service.StartException in service jboss.data-source.java:/H2DS: Error during the deployment of java:/H2DS at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:113) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:680) [:1.6.0_24] Caused by: org.jboss.msc.service.StartException in anonymous service: unable to start the ds because it generate more than one cf at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:108) ... 4 more 18:40:07,603 INFO [org.jboss.as.server] (MSC service thread 1-2) Service status report Services which failed to start: service jboss.data-source.java:/H2DS: org.jboss.msc.service.StartException in service jboss.data-source.java:/H2DS: Error during the deployment of java:/H2DS -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (AS7-819) Fix or remove @Ignore in ServerInModuleStartupTestCase

by Thomas Diesler (JIRA)

Fix or remove @Ignore in ServerInModuleStartupTestCase ------------------------------------------------------ Key: AS7-819 URL: https://issues.jboss.org/browse/AS7-819 Project: Application Server 7 Issue Type: Sub-task Reporter: Thomas Diesler Assignee: Kabir Khan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBVFS-155) Add utility to generate a virtual jar/zip file input stream from a VFS directory

by John Bailey (JIRA)

Add utility to generate a virtual jar/zip file input stream from a VFS directory -------------------------------------------------------------------------------- Key: JBVFS-155 URL: https://jira.jboss.org/jira/browse/JBVFS-155 Project: JBoss VFS Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0.CR5 Reporter: John Bailey Assignee: John Bailey Fix For: 3.0.0.CR6 This should allow someone with a VFS directory to get an InputStream that will produce a stream of bytes according to the zip specification. This should only be used by 3rd party frameworks that require an actual input stream to an archive for integration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBVFS-169) Fix VirtualFile::toURL

by Ales Justin (JIRA)

Fix VirtualFile::toURL ---------------------- Key: JBVFS-169 URL: https://issues.jboss.org/browse/JBVFS-169 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.0.CR5 Reporter: Ales Justin Assignee: Ales Justin Fix For: 3.0.0.CR6 Current VirtualFile::toURL fails on paths with spaces. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
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 May 2011