RE: xmlBlaster 0.7.9 does not compile

["Douglas Dickinson" <ddd at taralnetworks.com>]

Reason for the problems/confusion revealed:

It turns out that a while back (without my <grumble/> knowlege), 
one of our developers installed the Java Media Framework 
extensions into our /tools/java/sun-jdk1.3.0 dir.  

That was why we had non-standard stuff in our 
	$JAVA_HOME/jre/lib/ext
Which is loaded by the VM immediately after the bootclasspath
(rt.jar, i18n.jar), and over-rides anything that appears in the
rest of your classpath.  :-P

Until minutes ago I had no idea that our /tools/java/sun-jdk1.3.0
install had been poluted with non-standard stuff.

Sorry for the confusion.
I'm once again a happy camper!

All the best,
DouglasDD
--
  Douglas D. Dickinson  =^..^=  ddd at taralnetworks.com

-----Original Message-----
From: owner-xmlblaster at xmlBlaster.org
[mailto:owner-xmlblaster at xmlBlaster.org]On Behalf Of Douglas Dickinson
Sent: Friday, May 04, 2001 9:58 AM
To: xmlblaster at xmlBlaster.org
Subject: RE: xmlBlaster 0.7.9 does not compile


Thanks to Marcel for pointing us in the right direction,
we got to the root of this issue.

Unsetting the CLASSPATH then setting up the xmlBlaster environment
before compiling running had no effect (same issues)

ddd at moria 1000 ~ $ unset CLASSPATH
ddd at moria 1001 ~ $ export XMLBLASTER_HOME=/home/ddd/xmlBlaster
ddd at moria 1002 ~ $ export JUTIL_HOME=$XMLBLASTER_HOME
ddd at moria 1003 ~ $ cd $XMLBLASTER_HOME
ddd at moria 1004 ~/xmlBlaster $ source .bashrc
...
ddd at moria 1005 ~/xmlBlaster $ javap javax.xml.parsers.SAXParser | grep
getXMLReader

found nothing!

ddd at moria 1006 ~/xmlBlaster $ mv $JAVA_HOME/jre/lib/ext/*
/tmp/disabled-jars/
ddd at moria 1007 ~/xmlBlaster $ javap javax.xml.parsers.SAXParser | grep
getXMLReader
    public abstract org.xml.sax.XMLReader getXMLReader() throws
org.xml.sax.SAXException;

found it!


Damn, I guess that I should have been suspiscious after manually
downloading and adding jaxp-1.1 to the front of the CLASSPATH did
not change anything.

I'm not sure what the best way to work around this on permanent basis is.
We do a lot of java development, so permanently removing stuff from the
standard JDK 1.3 installation is not a viable solution.

For `javac` the following is ok:
	javac -extdirs $XMLBLASTER_HOME/lib:$JAVA_HOME/jre/lib/ext ...
this could be worked into the ant/build files.

But, for `java` there is only the non-portable options:
	java -Xbootclasspath:...
	java -Xbootclasspath/p:...

Suggestions?

All the best,
DouglasDD
--
  Douglas D. Dickinson  =^..^=  ddd at taralnetworks.com

-----Original Message-----
From: owner-xmlblaster at xmlBlaster.org
[mailto:owner-xmlblaster at xmlBlaster.org]On Behalf Of Marcel Ruff
Sent: Thursday, May 03, 2001 4:55 PM
To: xmlblaster at xmlBlaster.org
Cc: Douglas Dickinson
Subject: Re: xmlBlaster 0.7.9 does not compile


Douglas Dickinson wrote:
>
> Some more investigation from the stack traces in my previous
> message reveal that org.xmlBlaster.util.SaxHandlerBase.java,
> at line 88 in method parse(), is calling a method of
> javax.xml.parsers.SAXParser that DOES NOT EXIST!!
> (getXMLReader())
>
> javax.xml.parsers.SAXParser comes from jaxp.jar

Hi Douglas,

with my CLASSPATH i get following result:

javap javax.xml.parsers.SAXParser
  ...
  Compiled from SAXParser.java
  public abstract class javax.xml.parsers.SAXParser extends
java.lang.Object {
  ...
  public abstract org.xml.sax.XMLReader getXMLReader() throws
org.xml.sax.SAXException;
  ...

The returned SAXParser from SAXParserFactory.newSAXParser()
returns a valid implementation of getXMLReader().

Are you sure your CLASSPATH is correct (no other jaxp/parser in front
of the one delivered with xmlBlaster) ?
This looks like a CLASSPATH problem.
Have you hanging around some other jaxp/parser in $JAVA_HOME/jre/lib
or $JAVA_HOME/jre/lib/ext ??

To compile this should work (even with an empty CLASSPATH
 'unset CLASSPATH'):

  cd $XMLBLASTER_HOME
  build.sh all

I am running Linux and JDK 1.3 as well.

Hope it helps,
best regards,

Marcel