[
https://issues.apache.org/jira/browse/PIVOT-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877799#action_12877799
]
Appddevvv commented on PIVOT-513:
---------------------------------
I actually do not use it for my spring-based extension to the serializer,
however, I was thinking about it and envisioned that others could use it as
I could also have used if I had decided to build my spring serializer
extension differently e.g. create the actual definition of the object using
bean definitions then create the context. In that case, one would want the
id to be consistent.
So I did not have an immediate use case for it but thought that others
could. It also possible that we should pass a resources map to the create
instance method because it could contain initialization data, however, my
thinking there was that pivot level initialization should use its normal
process.
> allow instance creation customization when reading WTKX files by creating an
> instance creation factory method inside the serializer class
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PIVOT-513
> URL: https://issues.apache.org/jira/browse/PIVOT-513
> Project: Pivot
> Issue Type: Improvement
> Components: wtk
> Reporter: Appddevvv
> Priority: Minor
> Fix For: 1.5.1
>
> Attachments: serializer.patch
>
>
> In order to allow instance creation customization, change the serialization
> class by:
> a) Creating a protected instance creation method in the WTKXSerializer class.
> b) Change a private constructor to protected.
> c) Allow the creation of custom serialization instances when recursing into
> the tree by creating a protected serialization creation method.
> No client visible APIs are changed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
