[ 
https://issues.apache.org/jira/browse/PIVOT-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875510#action_12875510
 ] 

Appddevvv commented on PIVOT-513:
---------------------------------

In order to use other frameworks for managing instance creation, you have to 
intercept the instance creation.  So with the change you can use a spring 
context (or anything else for that matter) to create the instance. This allows 
you to inject data access classes or other elements, etc. right into the 
controller as needed depending on how you are implementing your classes. Pivot 
has a small injector using match-by-name so imagine being able to tap into 
something a bit more if you need to. The pivot injection should still be there 
of course.  I wrote a spring serializer subclass and have a context created 
when some components are instantiated that contain a significant amount of 
configuration e.g. injecting a variety of data classes and other things into a 
component derived from a tree view automatically.

The create method for the serializer allows you to maintain your subclass 
version as the serializer as you recurse.

> 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.6
>
>         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.

Reply via email to