The issue is similiar to CR 6939778 (which is marked fix in 6u20),
but this issue is reproduced with 6u20, so either this is a new
but related problem, or the fix for CR 6939778 is not complete.
There is no standalone reproducible testcase, but the developer
has reproduced the issue.
Here's a description from developer:
"Mixed code warning is displayed when a signed jar is used and the app uses getResource to display an image stored on the server. I have looked at the Forms code and it does appear that we are doing something similar to what is described in the previous forum posting I mentioned:
http://forums.sun.com/thread.jspa?threadID=5438123
I/we are hoping that this is not considered "expected" behavior especially where it concerns loading image files.
I have reproduced this issue with Oracle Forms and have also, possibly identified a work-around. It appears that the warning is *not* presented if a fully qualified URL is provided when calling the image (resource). In other words, if a relative virtual path or assumed/inherited path is used the warning IS presented. So for example this would fail:
/myimages/myPicture.gif
But this would *not* fail:
http://server:port/myimages/myPicture.gif
For Oracle Forms, although the work-around does fix the problem, it is not acceptable as a permanent fix."
but this issue is reproduced with 6u20, so either this is a new
but related problem, or the fix for CR 6939778 is not complete.
There is no standalone reproducible testcase, but the developer
has reproduced the issue.
Here's a description from developer:
"Mixed code warning is displayed when a signed jar is used and the app uses getResource to display an image stored on the server. I have looked at the Forms code and it does appear that we are doing something similar to what is described in the previous forum posting I mentioned:
http://forums.sun.com/thread.jspa?threadID=5438123
I/we are hoping that this is not considered "expected" behavior especially where it concerns loading image files.
I have reproduced this issue with Oracle Forms and have also, possibly identified a work-around. It appears that the warning is *not* presented if a fully qualified URL is provided when calling the image (resource). In other words, if a relative virtual path or assumed/inherited path is used the warning IS presented. So for example this would fail:
/myimages/myPicture.gif
But this would *not* fail:
http://server:port/myimages/myPicture.gif
For Oracle Forms, although the work-around does fix the problem, it is not acceptable as a permanent fix."