[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
11 years, 11 months
[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
11 years, 11 months
[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
11 years, 11 months
[JBoss JIRA] (AS7-6405) Resource mapping: Support parameters
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-6405?page=com.atlassian.jira.plugin.s... ]
Heiko Braun edited comment on AS7-6405 at 1/28/13 4:59 AM:
-----------------------------------------------------------
Support for parameters on tuple parts /profile={profile.name} and full tuples /{profile.address}/subsystem=messaging. The later is used to re-use address declaration independent of the server operation mode (standalone, domain)
was (Author: heiko.braun):
Support for parameters on tuple parts (/profile={profile.name}) and full tuples (/{profile.address}/subsystem=messaging). The later is used to re-use address declaration independent of the server operation mode (standalone, domain)
> Resource mapping: Support parameters
> ------------------------------------
>
> Key: AS7-6405
> URL: https://issues.jboss.org/browse/AS7-6405
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Console
> Reporter: Heiko Braun
> Assignee: Heiko Braun
> Fix For: 7.3.0.Alpha1
>
>
--
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
11 years, 11 months
[JBoss JIRA] (AS7-5822) MBUI Prototype
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-5822?page=com.atlassian.jira.plugin.s... ]
Heiko Braun updated AS7-5822:
-----------------------------
Description: Issue for M1 that can be considered a reasonable prototype. The scope is a UI prototype that works on the following subsystems: datasources, messaging, transactions
> MBUI Prototype
> --------------
>
> Key: AS7-5822
> URL: https://issues.jboss.org/browse/AS7-5822
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Console
> Reporter: Harald Pehl
> Assignee: Harald Pehl
> Fix For: 7.3.0.Alpha1
>
>
> Issue for M1 that can be considered a reasonable prototype. The scope is a UI prototype that works on the following subsystems: datasources, messaging, transactions
--
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
11 years, 11 months