Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #319937 +++ An adopter product is getting a class cast exception on a few scenarios where the wrong EMF2DOM Adapter is retrieved.. Exception follows: !ENTRY org.eclipse.wst.sse.core 4 4 2010-06-17 09:17:44.500 !MESSAGE A structured model client, EMF2DOMSSEAdapter(web-app,WebAppImpl) threw following exception during adapter notification (STRUCTURE_CHANGED ) !STACK 0 java.lang.ClassCastException: org.eclipse.jst.javaee.web.internal.impl. ServletImpl incompatible with org.eclipse.jst.j2ee.webapplication.WebTy pe at org.eclipse.jst.j2ee.webapplication.internal. impl.ServletImpl.eSet(ServletImpl.java:49 6) at org.eclipse.emf.ecore.impl.BasicEObjectImpl. eSet(BasicEObjectImpl.java:1081) ; at org.eclipse.wst.common.internal.emf.utilities. ExtendedEcoreUtil.eSetOrAdd(ExtendedEcoreUtil. java:79) at org.eclipse.wst.common.internal.emf.resource. Translator.setMOFValue(Translator.java:62 0) at org.eclipse.wst.common.internal.emf.resource. Translator.setMOFValue(Translator.java:63 5) at org.eclipse.wst.common.internal.emf.resource. EMF2DOMAdapterImpl.primUpdateMOFFeature(E MF2DOMAdapterImpl.java:1497) &nb sp; at org.eclipse.wst.common.internal.emf.resource. EMF2DOMAdapterImpl.updateMOFFeature(EMF2D OMAdapterImpl.java:1840) & nbsp; at org.eclipse.wst.common.internal.emf.resource. EMF2DOMAdapterImpl.primUpdateMOF(EMF2DOMAdapterImpl. java:993) at org.eclipse.wst.common.internal.emf.resource. EMF2DOMAdapterImpl.updateMOF(EMF2DOMAdapterImpl. java:973) at org.eclipse.wst.common.internal.emf.resource. EMF2DOMAdapterImpl.primUpdateMOFMultiFeat ure(EMF2DOMAdapterImpl.java:482) ; at org.eclipse.wst.common.internal.emf.resource. EMF2DOMAdapterImpl.primUpdateMOFMultiFeat ure(EMF2DOMAdapterImpl.java:1553) &nbs p; at org.eclipse.wst.common.internal.emf.resource. EMF2DOMAdapterImpl.updateMOFMultiFeature( EMF2DOMAdapterImpl.java:1767) &n bsp; at org.eclipse.wst.common.internal.emf.resource. EMF2DOMAdapterImpl.updateMOFFeature(EMF2D OMAdapterImpl.java:1822) & nbsp; at org.eclipse.wst.common.internal.emf.resource. EMF2DOMAdapterImpl.primUpdateMOF(EMF2DOMAdapterImpl. java:993) at org.eclipse.wst.common.internal.emf.resource. EMF2DOMAdapterImpl.updateMOF(EMF2DOMAdapterImpl. java:973) at org.eclipse.wst.xml.core.internal.emf2xml. EMF2DOMSSEAdapter.notifyChanged(EMF2DOMSSEAdapter. java:230) at org.eclipse.wst.sse.core.internal.provisional. AbstractNotifier.notify(AbstractNotifier. java:202) at org.eclipse.wst.xml.core.internal.document. XMLModelNotifierImpl.notifyStructureChang
Created attachment 175887 [details] patch for 305P
I approve of this bug.
Moving over to you Nitin, for approval and checkin
Approved, but this business of having more than one object for the same "adapter" type still feels wrong.
Code was checked in on 8/6/10.