Conf:

win XP
ibm jdk 1.3
cocobase 4 (install_cocobase4_0315.class)

Issue:

When you try to import an xmi file, the following error appears:

Error Parsing XMI file!
java.lang.ClassNotFoundException: com.sun.xml.parser.Parser

-----------------------------------------------------------
i have checked, the following class is in parser.jar in the lib directory however i cant find anywhere in the cocoadmin.bat or sub call a reference to parser.jar in the classpath.

Best regards

Hmm...

It's also in the xml.jar, which is included. It sounds like
you may have run out of CLASSPATH space. It's limited to 512
characters in java, and that's the most likely cause of this.
If you've installed CocoBase into a very long directory path
you may be just running out of classpath space... Or if you
have too long of classpath before launching cocoadmin then
you might either be encountering an error or a truncation
behavior.

THOUGHT Support

I have installed cocobase in his default directory ( c:\thought\cocobase4 )

and my CLASSPATH is totally empty before starting the coco admin java program.

An echo of the %CLASSPATH% just before starting cocoadmin gives:

beansrc;..\classes11;..\classes;..\lib\xml.jar;..\idb3_12\Classes\idb.jar;..\lib\RmiJdbc.jar;.;;.;..\lib\jndi.jar;..\lib\ejb.jar;C:\Program Files\java13\lib\tools.jar;..\lib\providerutil.jar;..\lib\jta101.jar;..\lib\jndi.jar;..\lib\rmiregistry.jar;;..\hsql143\demo\hsql.jar;..\jakarta-ant-1.4\lib\ant.jar

-----------------------------------------------------------
Note: before upgrading to the latest cocobase 4 release, it worked well, i am having issue importing xmi stuff since i am using cocobase4_0315.

Oky found the issue

the IBM jdk 1.3 comes with xerces.jar which makes conflicts with xml.jar i believe ( i cant start Orion application server neither if this file exist)

So you have to delete JAVAHOME\jre\lib\ext\xerces.jar and everything works fine after.

That sounds like an XML library compatibility issue then,
do you have any other XML libraries in your classpath?

THOUGHT Support

Ah yes, that makes sense. This is one of the thorny issues of
XML currently. While there's a supposed standard, the
implementations actually interfere with each other in the
real world... It's a very tough issue to debug as well, we're
happy you found the problem! We're using the Sun parser
currently (the non Xerces version), which probably is
incompatible with some files in Xerces...

This is one of the reasons we use the xml.jar 'locally'
instead of recommending that the developers install it into
the jre lib extension directory. Many vendors like IBM often
try to make it convenient for the developer by pre-installing
libraries such as this, but it seems more problematic than
helpful in most cases we've seen...

Anyway - great news and if you need anything else just let
us know!

THOUGHT Support

How about the programmer guide vol 2 ? ;)
Oky that was easy ;)

The volume 2 is coming... The documentation folks are working
feverishly... We don't generally make draft documentation
available however because many engineers simply complain about
the draft nature of it...

You're better off waiting for the official release, and if you
have any questions not answered in PGV1 or on this forum, just
post or email us and we'll be happy to answer them...

THOUGHT Support