[
https://issues.apache.org/jira/browse/OPENJPA-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564456#action_12564456
]
Patrick Linskey commented on OPENJPA-477:
-----------------------------------------
That makes sense. Not having access to the code in question, I don't have much
input about alternate approaches.
It was more the runtime behavior that I was interested in anyways.
Regarding the project as a whole: what are your plans for it, source-code-wise?
It sounds like a lot of the work that you're doing could be reused for some of
the SQL caching and manual-SQL-specification issues that have been bouncing
around over the last months. I'd love to figure out some way to take advantage
of the work you guys are doing to achieve some of these alternate goals.
> making StoreManager more flexible and extensible.
> -------------------------------------------------
>
> Key: OPENJPA-477
> URL: https://issues.apache.org/jira/browse/OPENJPA-477
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 1.0.2
> Reporter: Daniel Lee
> Fix For: 1.1.0
>
> Attachments: OPENJPA-477-trunk612523.patch, OPENJPA-477.613332.patch
>
>
> The OpenJPA StoreManager needs some modifications to make it more flexible
> and extensible. For example, some private methods and attributes need to
> made either public or protected. The attached patch identifies the areas
> that have been identified thus far. Please let me know if there are any
> concerns. Many thanks in advance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
