1 Reply Latest reply on Jul 5, 2002 12:01 PM by crackers

    Java standard extensions bug

    mr_dronski

      Hmm, I didn't find a forum to submit the bugs, so hope this one would be quite suitable. If not, plz forward the message where appropriate.

      JBoss v3.0.0 / integrated Tomcat 4.0.3
      JDK 1.3.1_01
      Win2K Pro

      I'm using unpacked ear deployment (war + ejb)
      I put some libs in ear root/lib directory.
      I specify in Manifest.mf file of ejb file the Class-Path parameter. The problem is with this parameter.

      1st version:
      ==========================
      Manifest-Version: 1.0
      Created-By: 1.3.1 (Sun Microsystems Inc.)
      Class-Path: lib/rsspars.jar
      Class-Path: lib/stock-common.jar
      Class-Path: lib/xerces2.jar

      2nd version:
      ==========================
      Manifest-Version: 1.0
      Created-By: 1.3.1 (Sun Microsystems Inc.)
      Class-Path: lib/rsspars.jar lib/stock-common.jar lib/xerces2.jar

      The problem is the 1st version DOESN'T work. Though it should, according to sun documentation. When I specify it all on one line, it's ok.

        • 1. Re: Java standard extensions bug
          crackers

          Yeah, this is a bug in the JDK - and it's been opened for over 2 years, last I looked. Apparently the Sun engineers haven't deemed it a high priority. Go over to the Java bug list and register a "vote" to have it fixed.

          I think this one is pretty freakin' important to J2EE!