Tapestry 5
  1. Tapestry 5
  2. 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

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.0
    • Fix Version/s: 5.1.0.0
    • Component/s: tapestry-hibernate
    • Labels:
      None

      Description

      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.

        Activity

        Hide
        Massimo Lusetti added a comment -

        That's GREAT!

        Show
        Massimo Lusetti added a comment - That's GREAT!
        Hide
        Howard M. Lewis Ship added a comment -

        I considered renaming tapestry-hibernate to tapestry-hibernate-ui, but decided that would be more disruptive. It's slightly odd that tapestry-hibernate-core and tapestry-hibernate use some overlapping package names, but again, this was to promote backwards compatibility with no disruption.

        Show
        Howard M. Lewis Ship added a comment - I considered renaming tapestry-hibernate to tapestry-hibernate-ui, but decided that would be more disruptive. It's slightly odd that tapestry-hibernate-core and tapestry-hibernate use some overlapping package names, but again, this was to promote backwards compatibility with no disruption.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development