1 Reply Latest reply on Aug 28, 2006 4:31 AM by Maurice Zeijen

    About Deploy-unit to develop a big project by Seam

    keisuke Newbie

      For example, it supposes that X-system has the following structure.

      X-system

      Login, Estimation, Reservation, Acceptance of the Order, Sales

      And, JBOSS-SEAM Project has the following structure.


      X.EAR

      X.JAR
      Login.Class
      Estimation.Class
      Reservation.Class
      Order.Class
      Sales.Class

      X.WAR
      Login.Jsp
      Estimation.Jsp
      Reservation.Jsp
      Order.Jsp
      Sales.Jsp


      When false is in the Estimation-Class, the Estimation-Class is modified.

      Then the Deploy-unit changes to X.EAR. And Login, Reservation, Order, Stocking and Sales Classes that without false are not deployed, service is stopped.

      Is there the method to avoid stopping of a service?

      I considered two kinds of methods. But these methods are not better solutions.



      1. It supposes that the Estimation, the Reservation, and others were changed into the separate Deploy-unit.

      Ex. Login.ear, Estimation.ear, Reservation.ear, Order.ear, Sales.ear

      Then, the Class information of Estimation cannot be taken over to Reservation. And the Class information of Reservation cannot be taken over to Order?.

      These problems occur.

      Can @In-Annotation be used in the separate Deploy-unit?

      Moreover, when the Common-Class is created, there is no good method to refer to the information from each Deploy-unit.



      2. X.ear, X.jar, X.war were deployed per folder. And the Class-file of contents was replaced.

      Then Jsp in war was changed. However the Class-file was not changed.