[
https://issues.apache.org/jira/browse/TAPESTRY-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Adams reassigned TAPESTRY-1576:
-----------------------------------
Assignee: Dan Adams
> Getting access to the created configuration
> -------------------------------------------
>
> Key: TAPESTRY-1576
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1576
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-hibernate
> Affects Versions: 5.0.5
> Reporter: Dan Adams
> Assignee: Dan Adams
> Attachments: patch-r547489-get-configuration.txt
>
>
> I want to create a maven plugin that will load up an ioc registry, take the
> configuration that includes all of the contributed entities, and then write
> the configuration out to a file. This is so that other tools, such as the
> hibernate tools we use to create the tables from the hibernate config, can
> create the tables for all the entities both from the application and
> contributions. Otherwise I'd have to somehow get a list of the entities that
> have been contributed (which I could do with a debugger don't I don't know
> any other way) and create one myself. But I'd much rather have a tool do it
> for me.
> One way we could do this would be to simply store the configuration in
> HibernateSessionSourceImpl and then add an accessor for it in
> HibernateSessionSource. If we wanted to be really safe that the object would
> be immutable we could wrap it in a decorator that would throw
> UnsupportedOperationExceptions in all of the methods that change state.
> I'd be willing to go ahead and create a patch for this if the approach is
> accepted. Just let me know.
--
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]
