tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (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
Date Mon, 01 Dec 2008 16:17:44 GMT

     [ https://issues.apache.org/jira/browse/TAP5-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship reassigned TAP5-392:
-----------------------------------------

    Assignee: Howard M. Lewis Ship

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


Mime
View raw message