This week's book giveaway is in the Jobs Discussion forum.
We're giving away four copies of Java Interview Guide and have Anthony DePalma on-line!
See this thread for details.
The moose likes Websphere and the fly likes WSAD 5.1.1 - Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "WSAD 5.1.1 - "EAR Validation failed"" Watch "WSAD 5.1.1 - "EAR Validation failed"" New topic

WSAD 5.1.1 - "EAR Validation failed"

Sean Sullivan
Ranch Hand

Joined: Sep 09, 2001
Posts: 427
I am using Websphere Studio Application Developer 5.1.1
on Windows 2000.
I have two projects in my workspace:
Foo (a Dynamic web application project)
FooEAR (an Enterprise application project)
I want to rebuild FooEAR using the "Rebuild project" menu option.
When I execute a rebuild, Websphere Studio's Tasks window
displays this error message:
CHKJ1000E: EAR Validation failed:
What could cause this error?
Sean Sullivan
Ranch Hand

Joined: Sep 09, 2001
Posts: 427
Note: these two projects were imported using WSAD's File --> Import
On the Import dialog, I selected "Existing Project Into Workspace"
Sean Sullivan
Ranch Hand

Joined: Sep 09, 2001
Posts: 427
The "Project Rebuild" is logging an error message into
the workspace's .log file
This is what I see in the .log file:
!ENTRY org.eclipse.jdt.ui 4 10001 Mar 25, 2004 11:39:44.161
!MESSAGE Internal Error
Java Model Exception: Java Model Status [Foo does not exist.]
at java.lang.Throwable.<init>(
at java.lang.Throwable.<init>(
at org.eclipse.core.runtime.CoreException.<init>(
at org.eclipse.jdt.core.JavaModelException.<init>(
at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(
at org.eclipse.jdt.internal.core.JavaProject.openWhenClosed(
at org.eclipse.jdt.internal.core.JavaElement.openHierarchy(
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(
at org.eclipse.jdt.internal.core.JavaElement.getChildren(
at org.eclipse.jdt.internal.core.JavaProject.getPackageFragmentRoots(
at org.eclipse.jdt.ui.actions.OrganizeImportsAction.hasSourceFolders(
at org.eclipse.jdt.ui.actions.OrganizeImportsAction.isEnabled(
at org.eclipse.jdt.ui.actions.OrganizeImportsAction.selectionChanged(
at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchSelectionChanged(
at org.eclipse.jdt.ui.actions.SelectionDispatchAction.selectionChanged(
at org.eclipse.jface.viewers.Viewer$
at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(
at org.eclipse.jface.viewers.StructuredViewer.updateSelection(
at org.eclipse.jface.viewers.StructuredViewer.setSelection(
at org.eclipse.jface.viewers.Viewer.setSelection(
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$4.handleInvalidSelection(
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(
at org.eclipse.jface.viewers.AbstractTreeViewer.remove(
at org.eclipse.jface.viewers.AbstractTreeViewer.remove(
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider$
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider$
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(
at org.eclipse.swt.widgets.Display.runAsyncMessages(
at org.eclipse.swt.widgets.Display.readAndDispatch(
at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(
at org.eclipse.jdt.internal.ui.reorg.DeleteResourcesAction.deleteProjects(
at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleKeyEvent(
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$7.keyReleased(
at org.eclipse.swt.widgets.TypedListener.handleEvent(
at org.eclipse.swt.widgets.EventTable.sendEvent(
at org.eclipse.swt.widgets.Widget.sendEvent(
at org.eclipse.swt.widgets.Display.runDeferredEvents(
at org.eclipse.swt.widgets.Display.readAndDispatch(
at org.eclipse.ui.internal.Workbench.runEventLoop(
at java.lang.reflect.AccessibleObject.invokeL(
at java.lang.reflect.Method.invoke(
at org.eclipse.core.launcher.Main.basicRun(
at org.eclipse.core.launcher.Main.main(
!ENTRY org.eclipse.jdt.core 4 969 Mar 25, 2004 11:39:44.240
!MESSAGE Foo does not exist.
Sean Sullivan
Ranch Hand

Joined: Sep 09, 2001
Posts: 427
I have a theory. I suspect that WSAD is failing due to
the .modulemaps file
The .modulemaps file maps from the EAR project to any
web module projects.
My .modulesmaps file contains this entry:
<module xmi:type="application:WebModule" href="META-INF/application.xml#WebModule_1070235942812"/>
I suspect that this entry is bogus and/or erroneous.
Jeanne Boyarsky
author & internet detective

Joined: May 26, 2003
Posts: 33132

In the J2EE view, you can see what modules WSAD thinks are associated with your EAR. You can also try deleting and readding the association this way.

[OCA 8 book] [Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Sean Sullivan
Ranch Hand

Joined: Sep 09, 2001
Posts: 427
> When I execute a rebuild, Websphere Studio's Tasks
> window
> displays this error message:
> CHKJ1000E: EAR Validation failed:
This is a bug in WSAD 5.1.1
This bug is fixed in WebSphere Studio Application Developer v5.1.1 Interim Fix 002
You can download the fix at
The bug occurs if your Web project contains a file that has no extension.
For example, a file named "README" would cause the EAR validation error message.
Midhila Menon

Joined: Aug 10, 2009
Posts: 1

Could anyone tell me how to fix this issue of CHKJ1000E: EAR Validation failed:

Also how to fix the new build given by IBM for this fix

I agree. Here's the link:
subject: WSAD 5.1.1 - "EAR Validation failed"
It's not a secret anymore!