Skip to main content

Java3D + Newer Eclipse Version -> Access restriction

3 replies [Last post]
chaose71
Offline
Joined: 2008-04-15
Points: 0

Current eclipse versions dont go well with java3d. Programs that worked fine before now produce 100s of strange errors, e.g. "Access restriction: The type SimpleUniverse is not accessible due to restriction on required library C:\Program Files\Java\jre6\lib\ext\j3dutils.jar" etc. Java3D is installed correctly and everything was (and is) working perfectly well with older eclipse versions.
I googled for a solution and found out that switching
Windows -> Preferences -> Java -> Compiler -> Errors/Warnings -> Deprecated and restricted API -> Forbidden reference (access rules): -> change to warning / ignore indeed elminated the error(s).
Can anyone explain me what is going on here? Why is Java3D "Deprecated and restricted"? Is the default setting of eclipse correct or oversuspicious? Did I miss anything else? Will the next java3d / eclipse version be fix this? Do I have to fix this? Questions over Questions ...
ChaosE71

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
interactivemesh
Offline
Joined: 2006-06-07
Points: 0
marcelnagm
Offline
Joined: 2010-06-02
Points: 0

i think if you subimt the bug to the eclipse team they will know that have a
bug
;)

2010/10/27

> Hello,
>
> current eclipse versions dont go well with java3d. Programs that worked
> fine before now produce 100s of strange errors, e.g.
>
> "Access restriction: The type SimpleUniverse is not accessible due to
> restriction on required library C:\Program
> Files\Java\jre6\lib\ext\j3dutils.jar"
>
> etc. Java3D is installed correctly and everything was (and is) working
> perfectly well with older eclipse versions. I googled for a solution and
> found out that switching
>
> Windows -> Preferences -> Java -> Compiler -> Errors/Warnings -> Deprecated
> and trstricted API -> Forbidden reference (access rules): -> change to
> warning / ignore
>
> indeed elminated the error(s).
>
> Can anyone explain me what is going on here? Is the default setting of
> eclipse correct or oversuspicious? Did I miss anything else? Will the next
> java3d / eclipse version be fix this? Do I have to fix this? Questions over
> Questions ...
>
> ChaosE71
> [Message sent by forum member 'chaose71']
>
> http://forums.java.net/jive/thread.jspa?messageID=486356
>

chaose71
Offline
Joined: 2008-04-15
Points: 0

*bump* Anyone got an idea? I'd really hope this does not mean that Java3D is not developed anymore ...
Thanks in advance,
ChaosE71