March 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBOSGI-42) Provide IzPack based Installer

by Thomas Diesler (JIRA)

Provide IzPack based Installer ------------------------------ Key: JBOSGI-42 URL: https://jira.jboss.org/jira/browse/JBOSGI-42 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Affects Versions: JBossOSGi 1.0.0 Alpha3 Reporter: Thomas Diesler Assignee: Thomas Diesler Document this in the wiki -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-43) Hudson QA as integral part of each project release

by Thomas Diesler (JIRA)

Hudson QA as integral part of each project release -------------------------------------------------- Key: JBOSGI-43 URL: https://jira.jboss.org/jira/browse/JBOSGI-43 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Affects Versions: JBossOSGi 1.0.0 Alpha3 Reporter: Thomas Diesler Assignee: Thomas Diesler Document this in the wiki -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2341) Make header urls relative by default

by Mike Millson (JIRA)

Make header urls relative by default ------------------------------------ Key: JBPORTAL-2341 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2341 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.6 Final Reporter: Mike Millson Absolute URLs can cause issues when fronting portal with Apache. For example, the absolute URL will have port 8080 in it instead of the Apache 80 port. It can be argued that relative URLs are better for the default. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-76) Succuesful testsuite run

by Jesper Pedersen (JIRA)

Succuesful testsuite run ------------------------ Key: JBJCA-76 URL: https://jira.jboss.org/jira/browse/JBJCA-76 Project: JBoss JCA Issue Type: Task Components: Common, Core, Deployer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Blocker Fix For: 1.0.Beta1 Although a full passing testsuite run should be a focus point for the alpha releases, the beta phase and candidate release phase must have a full parsing testsuite for each release. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2004) 5.0.0.CR1 Build Failure

by Garrett Conaty (JIRA)

5.0.0.CR1 Build Failure ----------------------- Key: JBRULES-2004 URL: https://jira.jboss.org/jira/browse/JBRULES-2004 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Environment: OS X, JDK 6 Reporter: Garrett Conaty Assignee: Mark Proctor BatchMessageHelperProviderImpl.java fails to compile. It imports sun.text.CompactShortArray.Iterator, an internal Sun class which doesn't appear to be present in JDK 6 on OS X. Looks to be an unused import though. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBJCA-30) Allow flushing of connection pool on fatal connection events

by Jesper Pedersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBJCA-30?page=com.atlassian.jira.plugi... ] Jesper Pedersen updated JBJCA-30: --------------------------------- Priority: Critical (was: Major) > Allow flushing of connection pool on fatal connection events > ------------------------------------------------------------ > > Key: JBJCA-30 > URL: https://jira.jboss.org/jira/browse/JBJCA-30 > Project: JBoss JCA > Issue Type: Feature Request > Components: Core > Reporter: Chris Bredesen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.CR1 > > > As an alternative to validating connections (either on borrow or in the background), we could implement a feature similar to WebSphere's purge policy. The idea is that we can assume in certain cases that a single fatal exception means every connection in the pool will subsequently throw fatal exceptions. Such is the case in situations where the connected database has been restarted. Rather than implementing a purge policy per se, we would implement an "on fatal behavior". The behavior could define one of three actions to be taken when a fatal exception is encountered: > 1. Destroy single connection (equivalent to WAS policy of "single connection") > 2. Initiate validation run > 3. Flush entire pool (equivalent to WAS policy of "whole pool") > Note that all of the above (indeed this entire feature) requires the use of an ExceptionSorter. > In terms of implementation, I see two possibilities: > 1. Implement this feature as an MBean, which means we'd need some way of registering connection event listeners outside JCA. > 2. Implement this feature as part of the JCA adapter which I think makes more sense, but is more impactful. > Regarding #1, if it's possible to simply add a way to register connection event listeners from outside the adapter, that could become its own feature request and this feature simply turns into an MBean that can be implemented separately. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBJCA-30) Allow flushing of connection pool on fatal connection events

by Jesper Pedersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBJCA-30?page=com.atlassian.jira.plugi... ] Jesper Pedersen updated JBJCA-30: --------------------------------- Fix Version/s: 1.0.CR1 > Allow flushing of connection pool on fatal connection events > ------------------------------------------------------------ > > Key: JBJCA-30 > URL: https://jira.jboss.org/jira/browse/JBJCA-30 > Project: JBoss JCA > Issue Type: Feature Request > Components: Core > Reporter: Chris Bredesen > Assignee: Jesper Pedersen > Fix For: 1.0.CR1 > > > As an alternative to validating connections (either on borrow or in the background), we could implement a feature similar to WebSphere's purge policy. The idea is that we can assume in certain cases that a single fatal exception means every connection in the pool will subsequently throw fatal exceptions. Such is the case in situations where the connected database has been restarted. Rather than implementing a purge policy per se, we would implement an "on fatal behavior". The behavior could define one of three actions to be taken when a fatal exception is encountered: > 1. Destroy single connection (equivalent to WAS policy of "single connection") > 2. Initiate validation run > 3. Flush entire pool (equivalent to WAS policy of "whole pool") > Note that all of the above (indeed this entire feature) requires the use of an ExceptionSorter. > In terms of implementation, I see two possibilities: > 1. Implement this feature as an MBean, which means we'd need some way of registering connection event listeners outside JCA. > 2. Implement this feature as part of the JCA adapter which I think makes more sense, but is more impactful. > Regarding #1, if it's possible to simply add a way to register connection event listeners from outside the adapter, that could become its own feature request and this feature simply turns into an MBean that can be implemented separately. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (EJBTHREE-508) @GeneratedValue does not work with composite primary key

by Emmanuel Bernard (JIRA)

[ https://jira.jboss.org/jira/browse/EJBTHREE-508?page=com.atlassian.jira.p... ] Emmanuel Bernard commented on EJBTHREE-508: ------------------------------------------- Hi Can you provide a patch + test case? > @GeneratedValue does not work with composite primary key > -------------------------------------------------------- > > Key: EJBTHREE-508 > URL: https://jira.jboss.org/jira/browse/EJBTHREE-508 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC6 - PFD > Reporter: Holger Johanndeiter > Assignee: Emmanuel Bernard > Attachments: User.java, UserPK.java > > > I have an entity with a primary key class (@IdClass annotation) where i want the id to be auto-generated. (see forum post) > That does not happen though, no ids are generated, the only id i get is 0. (leads to one database entry where the id is 0, after that errors of course). > Database is Hypersonic SQL. > The entity works perfectly fine without @IdClass annotation. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-74) Transaction API 1.0.1.GA

by Jesper Pedersen (JIRA)

Transaction API 1.0.1.GA ------------------------ Key: JBJCA-74 URL: https://jira.jboss.org/jira/browse/JBJCA-74 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0 Alpha1 Standalone + Test -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-75) Trove 2.1.1

by Jesper Pedersen (JIRA)

Trove 2.1.1 ----------- Key: JBJCA-75 URL: https://jira.jboss.org/jira/browse/JBJCA-75 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0 Alpha1 Stanalone + Test -- 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, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2009