1 Reply Latest reply on Aug 14, 2003 6:05 PM by Jon Barnett

    Inconsistency amog JBOSS versions.

    spoox2@hotmail.com Newbie

      Hi!,
      I tried deploying the practice EJB's from a tutorial across several JBOSS server versions. JBoss 3.0 deploys w/o errors but the JBoss3.2.1 and JBoss4.0 have problems, rather errors as in saying that the ejb-jar.xml should follow a standard schema or !DOCTYPE. Is this normal or am i making a mistake. If there is a standard DOCTYPE, can someone tell me what it is please. Any help would be appreciated. Thanx.
      Rishi..

        • 1. Re: Inconsistency amog JBOSS versions.
          Jon Barnett Master

          JBoss 3.2.x and higher have tighter compliance requirements for XML. You can turn off this behaviour by turning off the strict verifier in the main conf/jboss-service.xml. However, it is prefereable to specify the correct DTDs for your deployment descriptors, in-line with proper XML formation requirements.

          For the standard ejb-jar.xml, you either specify:
          <?xml version="1.0"?>
          <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_2_0.dtd">
          or
          <?xml version="1.0"?>
          <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd">

          This will depend on the EJB compliance you are seeking - particularly important for entity beans.

          Similarly, for jboss.xml, you should specify:
          <?xml version="1.0"?>
          <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS//EN" "http://www.jboss.org/j2ee/dtd/jboss.dtd">

          For web.xml:
          <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">

          So check the DTD specs for your deployment descriptors and insert the appropriate references to the templates into your deployment descriptors.