Hi,
The only build errors you should normally see are the vrml/WRL dependent classes
failing to build, which is allowed by default. "couldn't get I/O for" indicates
your server is not running (not even the java part, irrespective of its ability
to run dxexecs). In a non-file:/// configuration it could indicate firewalls in
the way, but on the same machine, it means the server isn't listening on the
port. It sounds as if at least one of the required classes did not build.
Status.html is pretty good last I looked, discounting anachronisms such as
/usr/lpp/dx startserver is now meant to run without options in a normal
installation (as it is modified by configure to be correct for that
installation). Base functionality should be obtainable nothing more elaborate
than
cd /usr/local/dx/java/server/bin && ./startserver
can you
telnet localhost 4655
with the server running?
Then again, if your goal is to get this running, download the jdk 1.1.8 from
www.ibm.com/java, set JAVA_ARCH to linux, make sure THAT javac is in your path,
and rm config.status and config.cache, all prior to configure. Then do a make
clean in uipp/java prior to make and make install. At that point we'll have a
common state to pursue any remaining problems, or a functional base to resolve
the jdk1.3 issues if any.
Pete
Karen Haines wrote:
> Hi David,
>
> > Here's what would help track down some problems. Open your Java Console in
> > Netscape. Hook to toc.html and report back what is being reported. It will
> > give you some more information.
>
> For debugging, I changed the permissions on the all the directories into
> the dx/java/server/bin and the dx/samples/java dirs to 777.
>
> When I bring up the file in netscape I get
> DXClient couldn't get I/O for
>
> How accurate is the information in the Status.html web page?
>
> >
> > What were your build errors? I've built this on multiple platforms and
> > haven't had any build problems for quite a while.
>
> I'll get back to you on this later.
>
> Cheers,
> Karen
