Details

    • Type: Feature Request
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.0.0.Final
    • Fix Version/s: Future
    • Labels:
      None
    • Environment:
      Upgrading to Seam 3
    • Estimated Difficulty:
      Low

      Description

      Migrating Seam 2 to Seam 3 is very hard to find a replacement for Seam 2's EntityHome. Also it looks that EntityHome is very important for Seam persist.

        Gliffy Diagrams

          Activity

          Hide
          lightguard Jason Porter added a comment -

          We're still debating the best way to accomplish this on the mailing list.

          Show
          lightguard Jason Porter added a comment - We're still debating the best way to accomplish this on the mailing list.
          Show
          blabno Bernard Labno added a comment - I've ported seam2 stuff to seam3. Check this out: http://it-crowd.com.pl/svn/seam3-persistence-framework/trunk/ http://artifactory.it-crowd.com.pl/libs-release-local/pl/com/it-crowd/seam3-persistence-framework/
          Hide
          lightguard Jason Porter added a comment -

          Thanks, we'll take a look, however, with nearly all those who have commented on http://seamframework.org/Community/TheNextFewSeamReleases wanting us to focus on DeltaSpike and having a good migration I think that is the way we will go.

          Show
          lightguard Jason Porter added a comment - Thanks, we'll take a look, however, with nearly all those who have commented on http://seamframework.org/Community/TheNextFewSeamReleases wanting us to focus on DeltaSpike and having a good migration I think that is the way we will go.
          Hide
          lightguard Jason Porter added a comment -

          There are a lot of people looking for this, we may pull it in. Bernard, would you mind getting a pull request ready?

          Show
          lightguard Jason Porter added a comment - There are a lot of people looking for this, we may pull it in. Bernard, would you mind getting a pull request ready?
          Hide
          blabno Bernard Labno added a comment - - edited

          Jason, should this go into api or impl? IMHO it should be a separate lib because it has dependency on javax.el:el-api and javax.faces:jsf-api and seam-persistence, so it's more like module integrator.

          Show
          blabno Bernard Labno added a comment - - edited Jason, should this go into api or impl? IMHO it should be a separate lib because it has dependency on javax.el:el-api and javax.faces:jsf-api and seam-persistence, so it's more like module integrator.
          Hide
          lightguard Jason Porter added a comment -

          Good point. A separate module works. Once you have it all ready as a module, I'll create a space for it on GitHub and add you to the team for it.

          Show
          lightguard Jason Porter added a comment - Good point. A separate module works. Once you have it all ready as a module, I'll create a space for it on GitHub and add you to the team for it.

            People

            • Assignee:
              Unassigned
              Reporter:
              gus888 Gus Gu
            • Votes:
              12 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:

                Development