6 Replies Latest reply on Oct 24, 2002 1:33 PM by Scott Williams

    Insert on PostCreate

    F Zemen Newbie

      I saw this on the to do list and referred here in the Forums. Any chance on getting an ETA for this feature?

      The DBAs absolutely WANT to enforce foreign key constraints, and thus I can't insert a row (Oracle8i) with a CMR relationship that gets set in the ejbPostCreate.

      Unrelated awesome news: We just kicked out Weblogic (been with them for 2 years) and are doing our rebuild on JBoss 3.0!

        • 1. Re: Insert on PostCreate
          Tung Dang Novice

          >Unrelated awesome news: We just kicked out Weblogic
          >(been with them for 2 years) and are doing our rebuild
          > on JBoss 3.0!

          Why that's? Could you please tell me more your experiences with Weblogic?

          Regards.

          • 2. Re: Insert on PostCreate
            F Zemen Newbie

            Cost of licenses, cost of service/maintenance, actual support obtained, quality of technology, ease of use.

            Thanks

            • 3. Re: Insert on PostCreate
              Dain Sundstrom Master

              ETA: Don't know. It is not the higest priortiy. It is planed for 4.0 and 3.2 will be going beta in a week or so.

              • 4. Re: Insert on PostCreate
                F Zemen Newbie

                Thanks for the heads up.

                I think I'm going to try to convince the DBA's to use Oracle deferred constraints.

                I was also wondering if anyone reading this has tried the following (temporary) workaround:

                Provide a CMP field for the foreign key that would always match the value CMR relationship (our Value Object pattern allows us to do this without exposing it in the local interface). Set the foreign key through CMP in ejbCreate, and let CMR maintain its relationship as normal in ejbPostCreate.


                • 5. Re: Insert on PostCreate
                  Dain Sundstrom Master

                  > I think I'm going to try to convince the DBA's to use
                  > Oracle deferred constraints.

                  Good luck on that. I have been told that deferred constraints basically lock up all of oracle, and it is easier to get the DBS to drop the not-null constraint.

                  > I was also wondering if anyone reading this has tried
                  > the following (temporary) workaround:
                  >
                  > Provide a CMP field for the foreign key that would
                  > always match the value CMR relationship (our Value
                  > Object pattern allows us to do this without exposing
                  > it in the local interface). Set the foreign key
                  > through CMP in ejbCreate, and let CMR maintain its
                  > relationship as normal in ejbPostCreate.

                  It has been tried, but it does not work without modifying the JBoss soruce code. You end up with duplicate column names in the update statement.

                  • 6. Re: Insert on PostCreate
                    Scott Williams Newbie

                    This would be a big help to us. Right now we are using deferred constraints. Weblogic has a delay until postcreate option. It would be great if JBoss supported something like this.

                    this issue might ultimately prevent us from using CMP, so it is a top priority for us.