January 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-981) Wrong validator rule "Section: 13.4.2.2 Description: An ActivationSpec class must implement the ActivationSpec interface" in case of @Activation annotation applied

by Vladimir Rastseluev (JIRA)

Vladimir Rastseluev created JBJCA-981: ----------------------------------------- Summary: Wrong validator rule "Section: 13.4.2.2 Description: An ActivationSpec class must implement the ActivationSpec interface" in case of @Activation annotation applied Key: JBJCA-981 URL: https://issues.jboss.org/browse/JBJCA-981 Project: IronJacamar Issue Type: Bug Reporter: Vladimir Rastseluev Assignee: Jesper Pedersen Due to JCA 1.6 spec. page 18-14, The JavaBean is not required to implement the javax.resource.spi.ActivationSpec interface if the JavaBean is annotated with the Activation annotation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (EJBTHREE-2294) Application exception lost if thrown in method annotated with @PostConstruct

by Matti Linnanvuori (JIRA)

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (EJBTHREE-2294) Application exception lost if thrown in method annotated with @PostConstruct

by Matti Linnanvuori (JIRA)

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-979) @ConfigProperty annotation type should be equal both property field type and type of setter method parameter

by Vladimir Rastseluev (JIRA)

[ https://issues.jboss.org/browse/JBJCA-979?page=com.atlassian.jira.plugin.... ] Vladimir Rastseluev updated JBJCA-979: -------------------------------------- Component/s: Common Validator > @ConfigProperty annotation type should be equal both property field type and type of setter method parameter > ------------------------------------------------------------------------------------------------------------ > > Key: JBJCA-979 > URL: https://issues.jboss.org/browse/JBJCA-979 > Project: IronJacamar > Issue Type: Bug > Components: Common, Validator > Affects Versions: 1.0.15.Final, 1.1.0.Beta3 > Reporter: Vladimir Rastseluev > Assignee: Jesper Pedersen > Fix For: 1.0.16.Final, 1.1.0.Beta4 > > > Due to JCA 1.6 spec. page 18-11, > It is an error if the value of the type annotation element specified by the developer in the ConfigProperty annotation, and the type of the field are not equal. > It is an error if the type specified by the developer in the ConfigProperty annotation and the ype of the setter method’s parameter are not equal. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-980) It should be an exception thrown, if administered object class, that implements more than one interface, isn't explicitly marked with adminObjectInterfaces annotation

by Vladimir Rastseluev (JIRA)

Vladimir Rastseluev created JBJCA-980: ----------------------------------------- Summary: It should be an exception thrown, if administered object class, that implements more than one interface, isn't explicitly marked with adminObjectInterfaces annotation Key: JBJCA-980 URL: https://issues.jboss.org/browse/JBJCA-980 Project: IronJacamar Issue Type: Bug Components: Validator Affects Versions: 1.1.0.Beta3, 1.0.15.Final Reporter: Vladimir Rastseluev Assignee: Jesper Pedersen Fix For: 1.0.16.Final, 1.1.0.Beta4 Due to JCA 1.6 spec. page 18-16, If the JavaBean class implements more than one Java interface, the resource adapter provider must explicitly state the interfaces supported by the administered object either through the adminObjectInterfaces annotation element or through the deployment descriptor. It is an error if the resource adapter provider does not use either of the two schemes to specify the Java types of the interfaces supported by the administered object. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6399) HAL: Setup installation process

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6399?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-6399: ---------------------------------- Zip does work if not getting too complex. As an alternative I would suggest http://izpack.org > HAL: Setup installation process > ------------------------------- > > Key: AS7-6399 > URL: https://issues.jboss.org/browse/AS7-6399 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Fix For: 7.3.0.Alpha1 > > > How de we install the HAL deliverables? Are all requirements met for EAP 6.1? Is the mechanism documented and tested? > How do we bundle a HAL release? Options are to provide ZIP which is the outcome of a maven assembly or a custom installer. > How does the actual installation work? Suggestion is to create a unique slot for each HAL release and configure the product to use this slot. Thus the user can go back and forth between different HAL releases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6399) HAL: Setup installation process

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/AS7-6399?page=com.atlassian.jira.plugin.s... ] Harald Pehl updated AS7-6399: ----------------------------- Summary: HAL: Setup installation process (was: HAL: Clarify installation requirements) > HAL: Setup installation process > ------------------------------- > > Key: AS7-6399 > URL: https://issues.jboss.org/browse/AS7-6399 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Fix For: 7.3.0.Alpha1 > > > How de we install the HAL deliverables? Are all requirements met for EAP 6.1? Is the mechanism documented and tested? > How do we bundle a HAL release? Options are to provide ZIP which is the outcome of a maven assembly or a custom installer. > How does the actual installation work? Suggestion is to create a unique slot for each HAL release and configure the product to use this slot. Thus the user can go back and forth between different HAL releases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6399) HAL: Clarify installation requirements

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/AS7-6399?page=com.atlassian.jira.plugin.s... ] Harald Pehl updated AS7-6399: ----------------------------- Description: How de we install the HAL deliverables? Are all requirements met for EAP 6.1? Is the mechanism documented and tested? How do we bundle a HAL release? Options are to provide ZIP which is the outcome of a maven assembly or a custom installer. How does the actual installation work? Suggestion is to create a unique slot for each HAL release and configure the product to use this slot. Thus the user can go back and forth between different HAL releases. was:How de we install the HAL deliverables? Are all requirements met for EAP 6.1? Is the mechanism documented and tested? > HAL: Clarify installation requirements > -------------------------------------- > > Key: AS7-6399 > URL: https://issues.jboss.org/browse/AS7-6399 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Fix For: 7.3.0.Alpha1 > > > How de we install the HAL deliverables? Are all requirements met for EAP 6.1? Is the mechanism documented and tested? > How do we bundle a HAL release? Options are to provide ZIP which is the outcome of a maven assembly or a custom installer. > How does the actual installation work? Suggestion is to create a unique slot for each HAL release and configure the product to use this slot. Thus the user can go back and forth between different HAL releases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-979) @ConfigProperty annotation type should be equal both property field type and type of setter method parameter

by Vladimir Rastseluev (JIRA)

Vladimir Rastseluev created JBJCA-979: ----------------------------------------- Summary: @ConfigProperty annotation type should be equal both property field type and type of setter method parameter Key: JBJCA-979 URL: https://issues.jboss.org/browse/JBJCA-979 Project: IronJacamar Issue Type: Bug Affects Versions: 1.1.0.Beta3, 1.0.15.Final Reporter: Vladimir Rastseluev Assignee: Jesper Pedersen Fix For: 1.0.16.Final, 1.1.0.Beta4 Due to JCA 1.6 spec. page 18-11, It is an error if the value of the type annotation element specified by the developer in the ConfigProperty annotation, and the type of the field are not equal. It is an error if the type specified by the developer in the ConfigProperty annotation and the ype of the setter method’s parameter are not equal. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (EJBTHREE-2237) Application exception lost if thrown in method annotated with @PostConstruct

by Matti Linnanvuori (JIRA)

13 years, 4 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 2013