Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
2 replies Latest Post - ‏2010-10-02T23:06:10Z by Dave.Yorn
rcbell
rcbell
1 Post
ACCEPTED ANSWER

Pinned topic have set jdk to 1.4, still getting 1.3-type validation errors

‏2005-01-14T05:05:34Z |
Hi,
I'm using WSAD 5.1.2 to build a portal project based on java 1.4.2. Using suggestions in this forum I've set my compiler compliance level to 1.4, and added my installed 1.4.2 JDK to the list of installed JREs. I have java code that references javax.crypto, and the validation is failing because it cannot resolve this and other 1.4-only references. IOW, it seems like the compiler is still using 1.3 compliance. Did I miss something? or could this be a bug in WSAD?

Thanks for any help!
Craig
Updated on 2010-10-02T23:06:10Z at 2010-10-02T23:06:10Z by Dave.Yorn
  • SystemAdmin
    SystemAdmin
    6042 Posts
    ACCEPTED ANSWER

    Re: have set jdk to 1.4, still getting 1.3-type validation errors

    ‏2005-03-14T09:01:44Z  in response to rcbell
    You need to enable Server Targetting in the Options -> J2EE panel. Then right-click on your project and select WAS v5.1 as the target server.

    Without this, WSAD still generates JDK1.3 warnings for backward compatibility.
  • Dave.Yorn
    Dave.Yorn
    1 Post
    ACCEPTED ANSWER

    Re: have set jdk to 1.4, still getting 1.3-type validation errors

    ‏2010-10-02T23:06:10Z  in response to rcbell
    rcbell wrote:
    Hi,
    I'm using WSAD 5.1.2 to build a portal project based on java 1.4.2. Using suggestions in this forum I've set my compiler compliance level to 1.4, and added my installed 1.4.2 JDK to the list of installed JREs. I have java code that references javax.crypto, and the files validation is failing because it cannot resolve this and other 1.4-only references. IOW, it seems like the compiler is still using 1.3 compliance. Did I miss something? or could this be a bug in WSAD?

    Thanks for any help!
    Craig

    You may tell the developing team, Maybe it's a bug.