Community
Participate
Working Groups
I have no JSPs in my projects but, from time to time, I see the following in the .log file: !ENTRY org.eclipse.jst.jsp.core 4 4 2005-07-20 11:33:38.112 !MESSAGE NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces. !STACK 0 org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces. at org.apache.xerces.dom.ElementNSImpl.setName(Unknown Source) at org.apache.xerces.dom.ElementNSImpl.<init>(Unknown Source) at org.apache.xerces.dom.CoreDocumentImpl.createElementNS(Unknown Source) at org.apache.xerces.dom.DOMImplementationImpl.createDocument(Unknown Source) at org.eclipse.jst.jsp.core.internal.util.DocumentProvider.getNewDocument (DocumentProvider.java:252) at org.eclipse.jst.jsp.core.internal.util.DocumentProvider.load (DocumentProvider.java:387) at org.eclipse.jst.jsp.core.internal.util.DocumentProvider.getDocument (DocumentProvider.java:126) at org.eclipse.jst.jsp.core.internal.contentmodel.ProjectDescription.updateServlet s(ProjectDescription.java:286) at org.eclipse.jst.jsp.core.internal.contentmodel.ProjectDescription$DeltaVisitor. visit(ProjectDescription.java:89) at org.eclipse.core.internal.events.ResourceDelta.accept (ResourceDelta.java:68) at org.eclipse.core.internal.events.ResourceDelta.accept (ResourceDelta.java:77) at org.eclipse.core.internal.events.ResourceDelta.accept (ResourceDelta.java:77) at org.eclipse.core.internal.events.ResourceDelta.accept (ResourceDelta.java:77) at org.eclipse.core.internal.events.ResourceDelta.accept (ResourceDelta.java:49) at org.eclipse.jst.jsp.core.internal.contentmodel.TaglibIndex$ResourceChangeListen er.resourceChanged(TaglibIndex.java:217) at org.eclipse.core.internal.events.NotificationManager$2.run (NotificationManager.java:276) at org.eclipse.core.internal.runtime.InternalPlatform.run (InternalPlatform.java(Inlined Compiled Code)) at org.eclipse.core.runtime.Platform.run(Platform.java(Compiled Code)) at org.eclipse.core.internal.events.NotificationManager.notify (NotificationManager.java:270) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges (NotificationManager.java:144) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange (Workspace.java:180) at org.eclipse.core.internal.resources.Workspace.endOperation (Workspace.java:914) at org.eclipse.core.internal.resources.Workspace.run (Workspace.java:1728) at org.eclipse.core.internal.events.NotificationManager$NotifyJob.run (NotificationManager.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76) Could it be because we're updating J2EE deployment descriptors on a secondary thread?
Nitin ... I think Yen is correct, and the web.xml file is out of synch when we call webxmlContents = ((IFile) webxml).getContents(true); So, we get what ever its contents is at the moment (but does not change the synch state of web.xml). Should we use webxmlContents = ((IFile) webxml).getContents(false); instead, and just silently do nothing if out of synch exception thrown? (since presumably we would be called later, once in synch again?). This also *might* be related to Bug 104533.
While a bad problem, given this doesn't "block use" any fix at this level is too risky to make at this point for 0.7 ... so, we'll attend to this bug next release. If you disagree or believe there is something "blocking" here I am not seeing, please comment.
Fixed in HEAD.
This is part of a mass update to close out all stale WTP defects already verified by the reporter but awaiting closure by the assignee. If you feel this defect was closed inappropriately, please reopen. Thanks, John Lanuti
*** Bug 103781 has been marked as a duplicate of this bug. ***
