JBuilder 9 + j3d sdk

Thread view:

m. roberts - 19 Dec 2003 02:53 GMT

Hi,

I just downloaded JBuilder 9 from borland and am trying to develop a
little with the java 3d sdk.

The j3d jars are in the JBuilder's /jre/lib/ext directory (the JRE
which *is* set as the IDE's JDK) and when i type my import statements
the "auto completion" feature even picks up and allows me to
dynamically select the com.sun.j3d.util packages, and any other j3d
packages i would need, but at when I try to compile I get a "package
com.sun.j3d.* does not exist" error.

I do not know what is misconfigured...is there something special you
have to do to get JBuilder to include these jars at compile time other
than a standard import statement?

Reply to this Message

guz guz - 19 Dec 2003 11:29 GMT

Il /19 dic 2003/, *m. roberts* ha scritto:

> Hi,
>
[quoted text clipped - 11 lines]
> you have to do to get JBuilder to include these jars at compile
> time other than a standard import statement?

I am using java3d and jbuilder 8 successfully, all i have done in
order to use j3d was :

tools , configure library, then in the class section add all j3d jars.

then in your project :

properties, required libraries , select j3d libs previously added

hope this helps

Reply to this Message

m. roberts - 20 Dec 2003 19:28 GMT

> I am using java3d and jbuilder 8 successfully, all i have done in
> order to use j3d was :
[quoted text clipped - 4 lines]
>
> properties, required libraries , select j3d libs previously added

Hmm, I have done this -- the compiler still will not recognize any
import statement packages...all the files seem to be in the right
place...its very strange and frustrating...

Reply to this Message

m. roberts - 20 Dec 2003 19:33 GMT

and NetBeans will not recognize the packages either ... re-install of
the J3d JDK does not fix...any other places to look for problems?

Reply to this Message

m. roberts - 20 Dec 2003 20:07 GMT

----
a complete removal and re-install of the SDKs resolved it...

Reply to this Message

guz guz - 21 Dec 2003 11:25 GMT

Il /20 dic 2003/, *m. roberts* ha scritto:

> ----
> a complete removal and re-install of the SDKs resolved it...

Im glad you finally solved it !

Reply to this Message