Community
Participate
Working Groups
Double clicking on a Bugzilla repository task in the Task List doesn't bring up a form, only the browser view. Error 2006-05-29 20:42:03.412 Could not create Bugzilla editor input java.io.IOException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found at org.eclipse.mylar.internal.bugzilla.core.RepositoryReportFactory.populateReport(RepositoryReportFactory.java:161) at org.eclipse.mylar.internal.bugzilla.core.BugzillaRepositoryUtil.getBug(BugzillaRepositoryUtil.java:146) at org.eclipse.mylar.internal.bugzilla.ui.editor.ExistingBugEditorInput.getCurrentBug(ExistingBugEditorInput.java:103) at org.eclipse.mylar.internal.bugzilla.ui.editor.ExistingBugEditorInput.<init>(ExistingBugEditorInput.java:82) at org.eclipse.mylar.internal.bugzilla.ui.tasklist.BugzillaTaskEditorInput.<init>(BugzillaTaskEditorInput.java:42) at org.eclipse.mylar.internal.bugzilla.ui.tasklist.BugzillaReportEditorFactory.createEditorInput(BugzillaReportEditorFactory.java:54) at org.eclipse.mylar.internal.tasklist.ui.editors.MylarTaskEditor.createPages(MylarTaskEditor.java:119) at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:241) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:609) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:384) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:552) at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:283) at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:126) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:269) at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:391) at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1102) at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1051) at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1256) at org.eclipse.ui.internal.PartStack.add(PartStack.java:442) at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:109) at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:60) at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:212) at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:202) at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:758) at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:665) at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:628) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2360) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2295) at org.eclipse.ui.internal.WorkbenchPage.access$9(WorkbenchPage.java:2287) at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2273) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2268) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2241) at org.eclipse.mylar.internal.tasklist.ui.TaskUiUtil.openEditor(TaskUiUtil.java:209) at org.eclipse.mylar.internal.tasklist.ui.TaskUiUtil$2.run(TaskUiUtil.java:198) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:2933) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2716) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334) at org.eclipse.core.launcher.Main.basicRun(Main.java:278) at org.eclipse.core.launcher.Main.run(Main.java:973) at org.eclipse.core.launcher.Main.main(Main.java:948) eclipse.buildId=M20060118-1600 java.version=1.5.0_06 java.vendor=Apple Computer, Inc. BootLoader constants: OS=macosx, ARCH=ppc, WS=carbon, NL=en_US Framework arguments: -keyring /Users/maarten/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws carbon -arch ppc -keyring /Users/maarten/.eclipse_keyring -consoleLog -clean -showlocation
What Eclipse and JDK version are you using?
I found a temporary fix by downloading the latest version from xerces.apache.org and putting that in my default cllasspath. Now everything works smoothly. Is it a library dependency?
This is strange, because that org.apache.xerces claass is supposed to be distributed with JDK 1.5.0_06 which you are using. You have a rather old Eclipse 3.2 milestone and it could be failing to resolve the library dependency correctly. Could you try updating Eclipse and removing that from your default classpath?
I'm using 3.1.2 and according to the eclipse.org site this is the latest build available for Mac OSX. I want to wait a while before ging to 3.2... Version: 3.1.2 Build id: M20060118-1600
I removed the extra xerces again, and it starts failing again. Put it back in, and it works. I placed three jars from the xerces distribution in my path: xml-apis.jar, xercesImpl.jar and resolver.jar It doesn't seem to be in the standard Java 1.5.0 distribution on Mac, there are plenty versions in the eclipse plugin directory however :(
It surprises me that it would be missing from the 1.5 JDK, although some web searching indicated that it may have been misisng from the 1.4 JDK. For now I've added an item to the FAQ, but I'd like to get to the bottom of this. Could you double-check that you don't have the 1.4 JDK loading for some odd reason? See the bug linked from the following for instructions: http://www.eclipse.org/mylar/doc/faq.php#install-macos
I've done the following: $ cd /System/Library/Frameworks/JavaVM.framework/Versions $ ls 1.3 1.4 1.5 A CurrentJDK 1.3.1 1.4.2 1.5.0 Current $ sgi CurrentJDK sgi (thank you barebones software) displays 1.5.0, so it is referencing the right JDK
Thansk Maarten. I guess we'll have to leave this for now and rely on the FAQ entry. If you have any other ideas or notice that an updated Mac JDK does contain Xerces please post here.
Well my fix did turn up another problem. Since I installed the extra xerces, the formatting om XML using oxygen plugin doesn't work anymore. So my fix still has some annoying side effects. Once I resolve that I'll post here. Which of the Mylar plugins exactly rely on Xerces being present?
Hi Mik, please review the notes on the XML processing included with JDK 1.5 below: [...] From: support@oxygenxml.com Subject: Re: Bug report: Oxygen conflicts with Mylar workaround [...] Oxygen as an XML Editor has a stronger dependence on Xerces and it requires the Xerces version that comes with oXygen (which is in fact the latest Xerces2 J release, 2.8.0. If that plugin [Mylar] has a dependence on Xerces then you should just add an entry in its plugin.xml pointing to whatever Xerces jar that needs, thus you allow different plugins to use different versions of Xerces. A note regarding the comments on the bug entry you linked to: there is no Xerces distributed with the 1.5 JDK, Sun JDKs contain an XML Processor and they started with some version of Xerces, but the packages are not org.apache.xerces.* but something like com.sun.org.apache.xerces.* which is a completely different thing if some code has a dependence on Xerces. I think that if you change the plugin.xml of that Mylar plugin then you need to start eclipse with -clean in the command line in order to have it refresh the plugin's information. Best Regards, George --------------------------------------------------------------------- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com bugs@oxygenxml.com wrote: [...] ------------------------ <oXygen/> version: 7.1.0 <oXygen/> distribution: eclipse OS: Mac OSX JVM: 1.5 Bug description: I use the eclipse mylar plugin. The latest update requires the presence of a xerces parser on the path. Xerces is not present by default on MAc OSX so I installed it. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=144287 for more info. Bug steps: Install xerces in /Library/Java/Extensions/ Start up Eclipse with Oxygen Open XML file Press format button The following error appears: Severity Description Resource In Folder Location Creation Time Id 2 org.apache.xerces.parsers.XIncludeAwareParserConfiguration ShortlistViewer.xml fold1wt June 3, 2006 8:58:39 AM 43858 when xerces is removed again this doesn't happen. [...]
As far as I can tell Mylar gets the parser from javax.xml.parsers.SaxParser, and related sax classes from org.xml.sax.., both of which are in rt.jar on Windows. Could you please check your rt.jar on Max and verify that these are missing?
On the Mac javax.xml.parsers.SaxParser, and related sax classes from org.xml.sax.. are in the file classes.jar and are present. So it must be something else. Out of curiosity I removed all the files in my Extensions directory including a xalan xslt tranformer and the problem disappeared for now.
Ohhh, so perhaps it was picking up a wrong version, that would make sense. Post if you learn more, for now I'll assume that was the case.
Reopening to mark as resolved as per message from webmaster: http://dev.eclipse.org/mhonarc/lists/eclipse.org-committers/msg00778.html.
Marking resolved.
