You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2008/12/01 20:31:44 UTC
[jira] Closed: (TAP5-392) tapestry-hibernate should be split into
two parts: tapestry-hibernate-core and tapestry-hibernate, with
tapestry-hibernate-core being usable outside of a Tapestry web application
[ https://issues.apache.org/jira/browse/TAP5-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-392.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.1.0.0
> tapestry-hibernate should be split into two parts: tapestry-hibernate-core and tapestry-hibernate, with tapestry-hibernate-core being usable outside of a Tapestry web application
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-392
> URL: https://issues.apache.org/jira/browse/TAP5-392
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-hibernate
> Affects Versions: 5.1.0.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.1.0.0
>
>
> People often want to use the facilities of tapestry-hibernate in a batch/non-web application. It's currently a bit difficult, but could easily be simplified by splitting tapestry-hibernate in two.
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org