| Summary: | org.eclipse.jst.j2ee.application.internal.impl.ApplicationImpl cannot be cast to org.eclipse.jst.javaee.application.Application | ||
|---|---|---|---|
| Product: | [WebTools] WTP Java EE Tools | Reporter: | Kaloyan Raev <kaloyan> |
| Component: | jst.j2ee | Assignee: | Kaloyan Raev <kaloyan> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Chuck Bridgham <cbridgha> |
| Severity: | major | ||
| Priority: | P3 | CC: | ccc, david_williams, luiz.filipe.abrahao |
| Version: | 3.1 | ||
| Target Milestone: | 3.1.2 P | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| URL: | CSN 3306393 2010 | ||
| Whiteboard: | |||
| Bug Depends on: | 263918, 296342 | ||
| Bug Blocks: | |||
|
Description
Kaloyan Raev
I can't say I understand the original bug much, but to be clear, you are asking for a patch build? Also, why is this just showing up now? I assume most workspaces are ok and don't have this problem? Is there some other tool or process that gives rise to this particular type of workspace that is having problems. David, yes I mean we need a patch build. We need it delivered as a zipped feature patch. We don't need it on an update site. I am currently working on providing a patch for the 3.1.2_patches CVS branch. I am not sure why it happens now. This is bug was reported to SAP by customer using one of our products, which is based on WTP 3.1.2. We need to deliver a patch compatible with WTP 3.1.2. The customer says that it is hard to reproduce. It happens after working a while with the tools in the Java EE perspective. But once it happens the workspace needs to be recreated. Simple restart of the IDE does not help. If you look at 296432#c5 , we discovered that it was Maven that was causing that issue. The issue cannot be fixed by a workspace restart - once a project with an EAR 1.3 facet and an EAR 5.0 DD is created, the ClassCastException will occur. WTP supports projects whose facet is greater than or equal to the deployment descriptor version. Having a project whose facet is less than the deployment descriptor version (especially one that crosses the Java EE 1.4/5.0 boundary) will cause problems. Backporting this fix will cause this exception to not appear... but there may still be other problems in this non-supported configuration. Carl, thanks for this clarification. I will hold on for now and will check more thoroughly what happens on the customer's system. I am closing this ticket for now. We have hard time reproducing the problem. I will reopen if there are any news. |