You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Ioannis Canellos (JIRA)" <ji...@apache.org> on 2011/09/06 09:01:12 UTC

[jira] [Created] (KARAF-850) Cellar should provide full access to hazelcast configuration

Cellar should provide full access to hazelcast configuration
------------------------------------------------------------

                 Key: KARAF-850
                 URL: https://issues.apache.org/jira/browse/KARAF-850
             Project: Karaf
          Issue Type: New Feature
          Components: cellar-hazelcast
    Affects Versions: cellar-2.2.1, cellar-2.2.2
            Reporter: Ioannis Canellos
             Fix For: cellar-3.0.0, cellar-2.2.3


Hazelcast is configured using an xml configuration file, which is embeded inside the hazelcast bundle. It allows the user to provide a custom xml file. 
Cellar on the other hand builds the configuration on top of the default configuration (overides it). It should provide means to the user to provide his own configuration file.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (KARAF-850) Cellar should provide full access to hazelcast configuration

Posted by "Ioannis Canellos (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ioannis Canellos resolved KARAF-850.
------------------------------------

    Resolution: Fixed

Committed on trunk and merged to 2.2.x branch.
                
> Cellar should provide full access to hazelcast configuration
> ------------------------------------------------------------
>
>                 Key: KARAF-850
>                 URL: https://issues.apache.org/jira/browse/KARAF-850
>             Project: Karaf
>          Issue Type: New Feature
>          Components: cellar-hazelcast
>    Affects Versions: cellar-2.2.2, cellar-2.2.1
>            Reporter: Ioannis Canellos
>            Assignee: Ioannis Canellos
>             Fix For: cellar-3.0.0, cellar-2.2.3
>
>
> Hazelcast is configured using an xml configuration file, which is embeded inside the hazelcast bundle. It allows the user to provide a custom xml file. 
> Cellar on the other hand builds the configuration on top of the default configuration (overides it). It should provide means to the user to provide his own configuration file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (KARAF-850) Cellar should provide full access to hazelcast configuration

Posted by "Ioannis Canellos (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ioannis Canellos reassigned KARAF-850:
--------------------------------------

    Assignee: Ioannis Canellos
    
> Cellar should provide full access to hazelcast configuration
> ------------------------------------------------------------
>
>                 Key: KARAF-850
>                 URL: https://issues.apache.org/jira/browse/KARAF-850
>             Project: Karaf
>          Issue Type: New Feature
>          Components: cellar-hazelcast
>    Affects Versions: cellar-2.2.2, cellar-2.2.1
>            Reporter: Ioannis Canellos
>            Assignee: Ioannis Canellos
>             Fix For: cellar-3.0.0, cellar-2.2.3
>
>
> Hazelcast is configured using an xml configuration file, which is embeded inside the hazelcast bundle. It allows the user to provide a custom xml file. 
> Cellar on the other hand builds the configuration on top of the default configuration (overides it). It should provide means to the user to provide his own configuration file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira