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/08/27 13:24:37 UTC
[jira] [Created] (KARAF-838) Simplify the way classloading works in
Cellar
Simplify the way classloading works in Cellar
---------------------------------------------
Key: KARAF-838
URL: https://issues.apache.org/jira/browse/KARAF-838
Project: Karaf
Issue Type: Improvement
Components: cellar-core
Affects Versions: cellar-2.2.1, cellar-2.2.2
Reporter: Ioannis Canellos
Fix For: cellar-3.0.0, cellar-2.2.3
Hazelcast (which is used by cellar) relies on the Thread Context ClassLoader (tccl) in order to serialize and deserialize objects that are being exchanged between nodes.
Cellar currently, sets the bundle class loader to the thread context classloader in order to have objects serialized and deserialized, which is not that bad (as lots of frameworks do so).
When a user builds an application that reuses the Cellar ClusterManager service, will have to do the same. I would like to find a way to avoid that.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-838) Simplify the way classloading works in
Cellar
Posted by "Jean-Baptiste Onofré (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-838:
---------------------------------------
Fix Version/s: (was: cellar-2.2.3)
cellar-2.2.4
> Simplify the way classloading works in Cellar
> ---------------------------------------------
>
> Key: KARAF-838
> URL: https://issues.apache.org/jira/browse/KARAF-838
> Project: Karaf
> Issue Type: Improvement
> Components: cellar-core
> Affects Versions: cellar-2.2.2, cellar-2.2.1
> Reporter: Ioannis Canellos
> Fix For: cellar-3.0.0, cellar-2.2.4
>
>
> Hazelcast (which is used by cellar) relies on the Thread Context ClassLoader (tccl) in order to serialize and deserialize objects that are being exchanged between nodes.
> Cellar currently, sets the bundle class loader to the thread context classloader in order to have objects serialized and deserialized, which is not that bad (as lots of frameworks do so).
> When a user builds an application that reuses the Cellar ClusterManager service, will have to do the same. I would like to find a way to avoid that.
--
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] [Updated] (KARAF-838) Simplify the way classloading works in
Cellar
Posted by "Jean-Baptiste Onofré (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-838:
---------------------------------------
Fix Version/s: (was: cellar-2.2.3)
cellar-2.2.4
> Simplify the way classloading works in Cellar
> ---------------------------------------------
>
> Key: KARAF-838
> URL: https://issues.apache.org/jira/browse/KARAF-838
> Project: Karaf
> Issue Type: Improvement
> Components: cellar-core
> Affects Versions: cellar-2.2.2, cellar-2.2.1
> Reporter: Ioannis Canellos
> Assignee: Jean-Baptiste Onofré
> Fix For: cellar-3.0.0, cellar-2.2.4
>
>
> Hazelcast (which is used by cellar) relies on the Thread Context ClassLoader (tccl) in order to serialize and deserialize objects that are being exchanged between nodes.
> Cellar currently, sets the bundle class loader to the thread context classloader in order to have objects serialized and deserialized, which is not that bad (as lots of frameworks do so).
> When a user builds an application that reuses the Cellar ClusterManager service, will have to do the same. I would like to find a way to avoid that.
--
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] [Resolved] (KARAF-838) Simplify the way classloading works
in Cellar
Posted by "Jean-Baptiste Onofré (Resolved JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved KARAF-838.
----------------------------------------
Resolution: Fixed
> Simplify the way classloading works in Cellar
> ---------------------------------------------
>
> Key: KARAF-838
> URL: https://issues.apache.org/jira/browse/KARAF-838
> Project: Karaf
> Issue Type: Improvement
> Components: cellar-core
> Affects Versions: cellar-2.2.2, cellar-2.2.1
> Reporter: Ioannis Canellos
> Assignee: Jean-Baptiste Onofré
> Fix For: cellar-3.0.0, cellar-2.2.3
>
>
> Hazelcast (which is used by cellar) relies on the Thread Context ClassLoader (tccl) in order to serialize and deserialize objects that are being exchanged between nodes.
> Cellar currently, sets the bundle class loader to the thread context classloader in order to have objects serialized and deserialized, which is not that bad (as lots of frameworks do so).
> When a user builds an application that reuses the Cellar ClusterManager service, will have to do the same. I would like to find a way to avoid that.
--
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-838) Simplify the way classloading works
in Cellar
Posted by "Jean-Baptiste Onofré (Assigned JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-838:
------------------------------------------
Assignee: Jean-Baptiste Onofré
> Simplify the way classloading works in Cellar
> ---------------------------------------------
>
> Key: KARAF-838
> URL: https://issues.apache.org/jira/browse/KARAF-838
> Project: Karaf
> Issue Type: Improvement
> Components: cellar-core
> Affects Versions: cellar-2.2.2, cellar-2.2.1
> Reporter: Ioannis Canellos
> Assignee: Jean-Baptiste Onofré
> Fix For: cellar-3.0.0, cellar-2.2.3
>
>
> Hazelcast (which is used by cellar) relies on the Thread Context ClassLoader (tccl) in order to serialize and deserialize objects that are being exchanged between nodes.
> Cellar currently, sets the bundle class loader to the thread context classloader in order to have objects serialized and deserialized, which is not that bad (as lots of frameworks do so).
> When a user builds an application that reuses the Cellar ClusterManager service, will have to do the same. I would like to find a way to avoid that.
--
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] [Updated] (KARAF-838) Simplify the way classloading works in
Cellar
Posted by "Jean-Baptiste Onofré (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-838:
---------------------------------------
Fix Version/s: (was: cellar-2.2.4)
cellar-2.2.3
> Simplify the way classloading works in Cellar
> ---------------------------------------------
>
> Key: KARAF-838
> URL: https://issues.apache.org/jira/browse/KARAF-838
> Project: Karaf
> Issue Type: Improvement
> Components: cellar-core
> Affects Versions: cellar-2.2.2, cellar-2.2.1
> Reporter: Ioannis Canellos
> Assignee: Jean-Baptiste Onofré
> Fix For: cellar-3.0.0, cellar-2.2.3
>
>
> Hazelcast (which is used by cellar) relies on the Thread Context ClassLoader (tccl) in order to serialize and deserialize objects that are being exchanged between nodes.
> Cellar currently, sets the bundle class loader to the thread context classloader in order to have objects serialized and deserialized, which is not that bad (as lots of frameworks do so).
> When a user builds an application that reuses the Cellar ClusterManager service, will have to do the same. I would like to find a way to avoid that.
--
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] [Commented] (KARAF-838) Simplify the way classloading works
in Cellar
Posted by "Jean-Baptiste Onofré (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193929#comment-13193929 ]
Jean-Baptiste Onofré commented on KARAF-838:
--------------------------------------------
We can still see TCCL in a lot of classes (especially in shell commands).
I leave this Jira opened, in order to check if it's clean or not.
> Simplify the way classloading works in Cellar
> ---------------------------------------------
>
> Key: KARAF-838
> URL: https://issues.apache.org/jira/browse/KARAF-838
> Project: Karaf
> Issue Type: Improvement
> Components: cellar-core
> Affects Versions: cellar-2.2.2, cellar-2.2.1
> Reporter: Ioannis Canellos
> Assignee: Jean-Baptiste Onofré
> Fix For: cellar-3.0.0, cellar-2.2.4
>
>
> Hazelcast (which is used by cellar) relies on the Thread Context ClassLoader (tccl) in order to serialize and deserialize objects that are being exchanged between nodes.
> Cellar currently, sets the bundle class loader to the thread context classloader in order to have objects serialized and deserialized, which is not that bad (as lots of frameworks do so).
> When a user builds an application that reuses the Cellar ClusterManager service, will have to do the same. I would like to find a way to avoid that.
--
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