EGL Development User Group

I'm not sure what I did, but all of a sudden I am getting the error shown below (from .metadata/.log).

!ENTRY org.eclipse.core.jobs 4 2 2015-07-23 15:24:34.098
!MESSAGE An internal error occurred during: "Loading descriptor for myEGLproject.".
!STACK 0
java.lang.ClassCastException: org.eclipse.jst.j2ee.webapplication.internal.impl.WebAppImpl incompatible with org.eclipse.jst.javaee.web.WebApp
    at org.eclipse.jst.jee.ui.internal.navigator.Web25ContentProvider.getNewContentProviderInstance(Unknown Source)
    at org.eclipse.jst.jee.ui.internal.navigator.LoadingJeeDDJob.run(Unknown Source)
    at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)

Does anyone know how I can fix this? 0.o

TIA

Walt

Walt,

Did you do anything or did the workbench crash prior to this error starting?  For example, you created a new project?  Or tried to change compiler levels for the project? 

Does it happen on startup?

I googled the "An internal error occurred during: "Loading descriptor for " and there were a couple of references related to "dynamic Web Projects" having an issue including maybe that the project no longer has a web.xml file.

Others were that some necessary plugins were not loaded correctly.  For this, one thing to try is change the startup properties in the shortcut by adding a -clean to the end of the command string.  This will force all the plugins to be recached.  Sometimes something gets corrupted.

I did a google on the ClassCastException and it seems to have something to do with incompatible facets/versions... See this link and a possible way to fix it (not specific to EGL).

http://www-01.ibm.com/support/docview.wss?uid=swg21474288

Mark

Mark,

Nothing unusual happened prior to this. I am continuing to work on my proof of concept project for work.

I was working on creating an 'external type' in a source file so that I could begin calling my service program procedures.

I tried doing the 'clean' yesterday but it did not work; I tried it again just now with the same results.

The web.xml file is still there.

Yes, this error appears in the log on startup. Then when I go into myEGLproject (iEGL) I get the following dialog box.

RBD has always complained about the incompatible facets regarding the related myEGLProjectEAR project, because it is setup to run on WAS and I have the myEGLProject project running on Tomcat 7.0. I have never been able to resolve that issue because RBD won't let me deploy the myEGLProjectEAR project to Tomcat 7.0. However, it has never thrown an error like I'm seeing now, and hasn't been a problem.

I will look at that link, but I am way beyond my depth here. I'm still trying to learn this new world of EGL, SOA, linking, etc, etc, etc.

Thanks for the help Mark.

Walt

Walt,

Thanks for the info. 

Just to be clear, when I say a -clean, I am not talking about "projects->Clean", I mean on the RBD startup (see screen shot).  

On the EAR, Tomcat does not use one, so you cannot deploy..  An EAR is a WAS only artifact in J2EE.  I  Tomcat only uses web projects and you deploy it.  

As a couple of questions/experiments:

- Can you incrementally "close" your web/EAR projects and restart to find which project is having the issue.   "Close Project" is on the context menu when you select a project.  You can then "open" it later to work with it.

- Are your only projects a RUI project which you then deploy into a Web project?

- Are you developing the services in the RUI project?

- If you are "developing" in the RUI project and then deploying to a web project.... can you create a new web project that is only associated with Tomcat (and no EAR).

- If none of the above works, can you create a new workspace and new RUI and subsequent/Web project specific to Tomcat.

Mark

Yep, that's the 'clean' I did; I've been using eclipse for many years so I *do* know that tip. 0-)

The projects I setup are modeled directly from Joe Pluta's book. So, I have an iRUI project which has all the handlers, and code to talk to the iEGL project; and, I have the iEGL project which has the code to talk to the as400.

I have not learned yet how to deploy to a web project; I have only been running this on my pc as a local Tomcat server for testing. I haven't even gotten to the point of being able (or knowing how) to deploy it to a real web server. I did manage to get Tomcat 7.0 up and running on our as400 though. 0-) 

We can get rid of the EAR since I can't use it, as we will definitely be using Tomcat on our as400. Do I just close it to get rid of it? Or do I delete it?

I will close it per your directions, and restart RBD to see if the error goes away in the meantime.

Edit: I followed the directions from the previous link you provided and that resolved the issue. The versions did not match between the two xml files that are mentioned in that article. I'd still like to get rid of that EAR though since don't need it. Thank you for your help!

Whoops, I spoke too soon.

I wasn't seeing the error in RBD after doing the previous steps because I was going into the project via Enterprise Explorer instead of Project Explorer. 

The error dialog box popped up again as soon as I switched back to the Project Explorer view. I restarted RBD and sure enough, I still see the error in the log. 0-/

Walt...

If you want, maybe we could do a webcast where you show me your screen and we can see if we can get this cleaned up.

If you do, contact me at evansm@us.ibm.com

Mark

As I have no clue how to resolve this....that would be fantastic!

Walt

Jeff and Mark,

You guys rock!

Thanks for all your help.

Walt

@markevans 5c01ba43-4f0f-42d9-8c50-ff9ba92b68b7 @MarkEvans 2fe2b0b8-d6f9-4556-8a78-fbed3df52a4b @Walt1968 6e6fe39e-6931-469f-aeb2-fac755d52ee3 @Jeff.Douglas 4b30a907-b629-433a-9e23-733a79e5a761​​​​

What was the solution to this problem?

Thank you.

If I found the right email, the solution was this (where iEGL was their project name)

In looking at the project you sent.  Somehow, the metadata within the web.xml file was reset (or never right in the first place).

Anyway, the second line (the <web-app line) in the file should have the following (they are wrapping here).

<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" version="3.0">
    <display-name>iEGL</display-name>

Instead of:

<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" version="2.4" id="WebApp_ID">
    <display-name>iEGL</display-name>

After this change is made, you should go to the web.xml and choose "open with -> Web Application 3.0 Deployment Descriptor Editor".

Then restart RBD.  If things are right, you should see the "Deployment Descriptor: iEGL" right below the project name after you restart Rbd.   Its icon should have the little 3.0 in it.   

The root of the issue is the web.xml or the editors think they should be 3.0, but it is somehow reverting back to 2.4. 

Hope it helps.

This was driving me crazy! Thanks!