3 Replies Latest reply on May 29, 2007 11:52 AM by gavin.king

    Development cycle (best practices?)

    laixer

      What's the best way to develop a Seam application?

      Right now I have JBoss AS pointing to my development directory.
      However, every time I redeploy I have to deal with the session data. Proxy objects are stored in the session, but they are not valid on redeploy so I get an error with that. If I reload, it will work again.

      I would love to know what other people do.
      Anybody develop outside an application server?

        • 1. Re: Development cycle (best practices?)
          timony

          Hi, I thing everyone except you develop outside the JBoss AS :-) The correct aproach would be, that you let the tool create the Eclipse project anywhere you want and just deploy the application by generated build.xml ant script into the JBoss AS deploy dir.

          try (from the command line)
          seam setup
          seam new-project
          seam generate-entities (optional, if you want to generate the reference
          application from the existing database)

          Tomas

          • 2. Re: Development cycle (best practices?)
            laixer

            Thanks for you reply, but why would I want to redeploy an EAR every time for development purposes? That's what I do for production, but for development it's a lot easier to use an exploded EAR. Please correct me if I missed the point.

            When I said developing outside an AS, I meant using something like the jboss embedded EJB container to develop/test the beans and then adding the views.

            • 3. Re: Development cycle (best practices?)
              gavin.king

              seam-gen uses an exploded directory deployment. Try it out.