RAD v7.0 Duplicate entry issue possibly caused by .runtime or.classpath files - Websphere

This is a discussion on RAD v7.0 Duplicate entry issue possibly caused by .runtime or.classpath files - Websphere ; We have migrated from RAD v6.0 and WAS v5.1 to RAD v7.0 and WAS v6.1 (with much pain). Our RAD v7.0 projects WEB, EJB and APPLICATION all contain .runtime files that still point to WAS 5.1: and the .classpath file ...

+ Reply to Thread
Results 1 to 8 of 8

Thread: RAD v7.0 Duplicate entry issue possibly caused by .runtime or.classpath files

  1. RAD v7.0 Duplicate entry issue possibly caused by .runtime or.classpath files

    We have migrated from RAD v6.0 and WAS v5.1 to RAD v7.0 and WAS v6.1 (with much pain).
    Our RAD v7.0 projects WEB, EJB and APPLICATION all contain .runtime files that still point to WAS 5.1:

    and the .classpath file contain old WAS v5.1 references as well as the now WAS v6.1 ones:













    We are getting errors of "build path contains duplicate entry".

    The only way to stop the errors is to alter any line in the .classpath file (in any legal way) and rebuild.

    The questions boil down to:
    1) should we have these lines in both files referring to WAS 5.1?
    2) is the .runtime file still being used by RAD v7.0?


    Many thanks in advance....

  2. Re: RAD v7.0 Duplicate entry issue possibly caused by .runtime or.classpath files

    Hello,

    Did you find a solution to the below issues?
    I'm also getting a build path contains duplicate entry: '.....' for project '.....'.
    Although, when I look in the .classpath file for this project, I cannot see any duplicate entries here for the entry that is mentioned in the error message.

    When running the application on the local server within the workspace I'm also getting an error: "Error 500: SRVE0203E: Servlet [action]: org.apache.struts.action.ActionServlet was found, but is missing another required class. SRVE0206E: This error typically implies that the servlet was originally compiled with classes which cannot be located by the server. SRVE0187E: Check your classpath to ensure that all classes required by the servlet are present.SRVE0210I: This problem can be debugged by recompiling the servlet using only the classes in the application's runtime classpath SRVE0234I"

    I've attached all shared libraries to the application as I did in WAS5.1. Does WAS6.1 build the classpath differently? Or can this be caused by the entry of the was.base.v51 in the .classpath file?


  3. Re: RAD v7.0 Duplicate entry issue possibly caused by .runtime or .classpath files


    ha scritto nel messaggio
    news:300649456.1183700037745.JavaMail.wassrvr@ltsg was009.sby.ibm.com...
    > Hello,
    >
    > Did you find a solution to the below issues?
    > I'm also getting a build path contains duplicate entry: '.....' for
    > project '.....'.
    > Although, when I look in the .classpath file for this project, I cannot
    > see any duplicate entries here for the entry >that is mentioned in the
    > error message.


    HI, I'm getting crazy with this issue... we have a similar one. Sometimes,
    for example, when we close and reopen RAD 7.0, project which were compiled
    and correctly validated before closing RAD are not valid any more. Sometimes
    RAD 7.0 can't find javax.ejb.* or any other "system" classes without ANY
    change to project dependencies....

    And we're getting a lot confused about setting dependencies between
    projects.....

    Regards,
    Scorpio.




  4. Re: RAD v7.0 Duplicate entry issue possibly caused by .runtime or.classpath files

    It turns out we get the error after doing any kind of debugging within RAD.
    It seems that extra references are added the "EAR libraries" entry under Java Build Path | Libraries in our web application project properties.

    It looks like that a timely upgrade to RAD v7.0.0.3 may have solved the problem.

  5. Re: RAD v7.0 Duplicate entry issue possibly caused by .runtime or .classpath files

    On Jul 9, 9:51 am, wrote:
    > It turns out we get the error after doing any kind of debugging within RAD.
    > It seems that extra references are added the "EAR libraries" entry under Java Build Path | Libraries in our web application project properties.
    >
    > It looks like that a timely upgrade to RAD v7.0.0.3 may have solved the problem.


    Hi,

    I am using v7.0.0.3.

    To be sure that I have a clean workspace under RAD7, I created a new
    workspace from scratch and imported all my application sources. It
    seems the .runtime file is no longer necessary, since RAD7 didn't
    create it. Also, now all references to the base_v51 were gone from the
    classpath (except for some Environment setting in Windows, which was
    added to the Java Classpath when I started the server, so I removed
    that as well).

    Still I'm running into issues that other required classes cannot be
    found.
    I'm using Struts in my application and set it up as an external user
    library (removed the one that was created by RAD7 in WEB-INF\lib,
    since that was also causing compilation errors). But now I'm getting
    errors : "Failed to parse Tag Library".

    It seems RAD7 is treating the setup of shared libraries somewhat
    different than RAD6.

    What's the use of the EAR Libraries that RAD7 creates for each
    project? What does it refer to?


  6. Re: RAD v7.0 Duplicate entry issue possibly caused by .runtime or.classpath files

    7.0.0.3 does not solve the problem. From their readme.txt

    Error "Unnecessary classpath entries duplicating MANIFEST.MF entries" in J2EE project

    When working with J2EE projects, you might see an error message "Unnecessary classpath entries duplicating MANIFEST.MF entries" in the Problems view.; These errors might prevent you from being able to deploy the application to the sever.

    Cause:

    The project contains a .classpath entry which is unnecessary because the class path information is computed dynamically from the META-INF/MANIFEST.MF file (which is the method that is used at runtime). The result is an error message reporting that the .classpath entry is unnecessary.

    Workaround:

    To fix this error, either remove the .classpath entry manually or right-click on the error and select Quickfix to have the .classpath entry automatically removed. If there are many errors of this type in the project, they can all be fixed simultaneously:

    1. Right-click one of the errors,
    2. Select Quickfix.
    3. In the Quickfix dialog, select Find similar problems.



  7. Re: RAD v7.0 Duplicate entry issue possibly caused by .runtime or.classpath files

    In my attempt to continue to find information on this topic, I found this to be very helpful:

    http://www.ibm.com/developerworks/fo...=169793&cat=24



  8. Re: RAD v7.0 Duplicate entry issue possibly caused by .runtime or.classpath files

    Hi....

    I have created a project in RAD 6 with websphere6.0.
    Now i want to migrate the project to RAD 7. If i import the project means it give error and not able to add the project in server.
    please help me..........

    Thanks,
    Jayaprakash.R

+ Reply to Thread