| Summary: | Web Deployment Assembly with User Library Reference leads to exception during war creation | ||
|---|---|---|---|
| Product: | [WebTools] WTP Java EE Tools | Reporter: | Nils <eclipse-bugzilla> |
| Component: | jst.j2ee | Assignee: | jst.j2ee <jst.j2ee-inbox> |
| Status: | NEW --- | QA Contact: | Chuck Bridgham <cbridgha> |
| Severity: | normal | ||
| Priority: | P3 | CC: | admin, jesse.mleziva, mikioma |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Nils
(In reply to comment #0) First time I installed Helios, I used to have this problem as well... but now it seems to work. I don't remember if I've updated Helios or not... maybe it's been fixed... Good luck! I have recently had the same problem with Helios SR 2. I am simply doing the other user's step 4: 4. on web project select Export -> War File Below is my stack trace. Thanks, -Jesse Error Mon May 23 23:38:19 CDT 2011 Extended Operation failure: org.eclipse.jst.j2ee.internal.archive.operations.JavaEEComponentExportOperation org.eclipse.core.commands.ExecutionException: Error exporting/home/jesse/Desktop/isbamic.war at org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.execute(ComponentExportOperation.java:136) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:385) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:410) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:360) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:247) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:219) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:207) at org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelWizard$1CatchThrowableRunnableWithProgress.run(DataModelWizard.java:225) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Caused by: org.eclipse.jst.jee.archive.ArchiveSaveFailureException: java.lang.NullPointerException at org.eclipse.jst.j2ee.internal.archive.operations.FlatComponentArchiver.saveArchive(FlatComponentArchiver.java:117) at org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.export(ComponentExportOperation.java:178) at org.eclipse.jst.j2ee.internal.archive.operations.ComponentExportOperation.execute(ComponentExportOperation.java:134) ... 10 more Caused by: java.lang.NullPointerException at org.eclipse.wst.common.componentcore.internal.flat.FlatFolder.getAdapter(FlatFolder.java:103) at org.eclipse.jst.j2ee.internal.archive.operations.FlatComponentArchiver.addZipEntry(FlatComponentArchiver.java:225) at org.eclipse.jst.j2ee.internal.archive.operations.FlatComponentArchiver.saveFlatResources(FlatComponentArchiver.java:154) at org.eclipse.jst.j2ee.internal.archive.operations.FlatComponentArchiver.saveFlatResources(FlatComponentArchiver.java:156) at org.eclipse.jst.j2ee.internal.archive.operations.FlatComponentArchiver.saveArchive(FlatComponentArchiver.java:106) ... 12 more eclipse.buildId=M20110210-1200 java.version=1.6.0_25 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product I just experienced this issue myself and was able to discover why it happened to me. I had a User library where I updated some of the jar files. I did the update by simply replacing the files in their directories with the newer versions. I had Eclipse open when I did this. Some of my projects that referenced this library started showing this error. I did not connect the two since they happened several days apart. Once I closed Eclipse and reopened, I got some build path errors that I tracked to the change. Once I removed and readded the updated jars, the error went away. Just wanted to let you know that changing jars in a User library outside of Eclipse while Eclipse is open can lead to this error. |