stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Isuru Haththotuwa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (STRATOS-391) Change artifacts stored in SM registry to non-binary format.
Date Wed, 29 Jan 2014 12:14:13 GMT

    [ https://issues.apache.org/jira/browse/STRATOS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885285#comment-13885285
] 

Isuru Haththotuwa commented on STRATOS-391:
-------------------------------------------

Hi Ramith,

Thank you for opening the jira. We already identified this issue prior to the registry migration,
but did not have the time to do the required changes at that time. We can achieve it using
properties in registry (name-value pairs). Basically what we need to do is to introduce a
middle layer in accessing the registry to do the conversion from and to the relevant object.
We will do this in a future milestone asap.

> Change artifacts stored in SM registry to non-binary format.
> ------------------------------------------------------------
>
>                 Key: STRATOS-391
>                 URL: https://issues.apache.org/jira/browse/STRATOS-391
>             Project: Stratos
>          Issue Type: Bug
>          Components: Stratos Manager
>    Affects Versions: 4.0.0 M6
>            Reporter: Ramith Jayasinghe
>
> It seems $subject. This could lead to a situation where if the class content of is changed,
its not possible to de-serialize object that are serialize registry.
> (Think about a situation where User runs Stratos for a while and want to version upgrade
of the binaries and with the version upgrade comes changed class definitions which are used
serialize objects ... a nightmare!)



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message