[
https://issues.apache.org/jira/browse/TUSCANY-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469563
]
Frank Budinsky commented on TUSCANY-1086:
-----------------------------------------
Hasan,
Thanks for doing this.
I would say that we don't strictly need a scoped output stream, becasue the
objects being serialized know their scope (types). It's only during deserialize
(input stream) that we need to provide it with the location of the types. That
said, I do think it would still be good to be symetrical and add two methods to
SDOUtil:
SDOUtil.createObjectInputStream(HelperContext scope);
and
SDOUtil.createObjectOutputStream(HelperContext scope);
The second could just return an ordinary ObjectOutputStream. (maybe in the
future it might do something special??).
Frank.
> Scope defined java serialiazation/deserialization of SDO
> --------------------------------------------------------
>
> Key: TUSCANY-1086
> URL: https://issues.apache.org/jira/browse/TUSCANY-1086
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SDO Implementation
> Affects Versions: Java-M2
> Environment: All
> Reporter: Hasan Muhammad
>
> Need to have a scope defined java serialization/deserialization of SDO's.
> Currently it can be done only in the Global/default scope. Have to fix this
> by using helperContext as the scope for creating ObjectInputStream and
> ObjectOutputStream.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
