4 Replies Latest reply on Apr 12, 2002 2:19 PM by jtulley

    jboss beta cmp 2.0 docs

    nickbuus

      When I use the jboss 3.0 alpha release, my jar files that has been build using the cmp 2.0 docs works fine but they generate errors in the beta release.

      Does anyone know when the cmp2.0 docs will be updated to jboss 3.0 beta?

      Could someone tell me exactly what has changed??

      Thanks

      Nick

        • 1. Re: jboss beta cmp 2.0 docs
          ninki

          Nick,
          You're not the only one. I had problems deploying my jar on the alpha, switched to the beta hoping for a better error message (Dodgy relationships were the problem - and no the beta is not much better at describing the problem).

          However, I could not fix the problem in beta, although it worked in the alpha.

          Guess it has something to do CMR fields and relationships.
          Ciao,
          Jonathan

          • 2. Re: jboss beta cmp 2.0 docs
            mcauleyt

            One recommendation I would have is to make sure you are verifying all of your xml files against the newest .dtd files.

            I did this for jbosscmp-jdbc.xml using the dtd from the CVS version of beta2 and it helped a lot.

            Otherwise... post your error messages here and someone might be help to point u in the right direction.

            Tim

            • 3. Re: jboss beta cmp 2.0 docs
              nickbuus

              Okey thanks for your replies, but where do I get these .dtd files?

              Nick

              • 4. Re: jboss beta cmp 2.0 docs
                jtulley

                http://www.jboss.org/j2ee/dtd/jbosscmp-jdbc_3_0.dtd

                The way that I found this is I looked in the source code, in jboss-all/server/src/resources/org/jboss/metadata. Here you will find all DTD's that JBoss uses, and many of them have a reference back to the URL where they can be found on the net. (JBoss first tries to look locally for the DTD though when deploying your EJB, to these DTDs bundled in JBoss)