facebook

opening XML document in spring beans

  1. MyEclipse Archived
  2.  > 
  3. Bugs
Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #261865 Reply

    Unable to create this part due to an internal error. Reason for the failure: An unexpected exception was thrown.

    java.lang.NullPointerException
    at org.eclipse.wst.sse.ui.StructuredTextEditor.update(StructuredTextEditor.java:3047)
    at org.eclipse.wst.xml.ui.internal.tabletree.XMLMultiPageEditorPart.addSourcePage(XMLMultiPageEditorPart.java:338)
    at org.eclipse.wst.xml.ui.internal.tabletree.XMLMultiPageEditorPart.createPages(XMLMultiPageEditorPart.java:505)
    at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:276)
    at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:596)
    at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
    at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
    at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:290)
    at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:140)
    at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268)
    at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
    at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:394)
    at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1144)
    at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1097)
    at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1311)
    at org.eclipse.ui.internal.PartStack.add(PartStack.java:455)
    at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:102)
    at org.eclipse.ui.internal.PartStack.add(PartStack.java:441)
    at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:111)
    at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:60)
    at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217)
    at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207)
    at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:820)
    at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:719)
    at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:680)
    at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2593)
    at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2528)
    at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2520)
    at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2505)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
    at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2500)
    at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:288)
    at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:280)
    at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:184)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
    at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
    at org.eclipse.core.launcher.Main.run(Main.java:977)
    at org.eclipse.core.launcher.Main.main(Main.java:952)
    I have tried -clean option checked types option
    the message is unsupported content type
    I have XML buddy installed this happens with most xml editors including the myeclipse xml editor only xml buddy seems to work

    #261915 Reply

    Riyad Kalla
    Member

    Yes, XML Buddy wreaks havoc on our editors. I don’t know of a workaround except removing XML Buddy, I’m sorry.

    #261998 Reply

    How do I remove xmlbuddy do I just disable it in product configuration?

    #262000 Reply

    XML Buddy does not even seem to be listed in the product features or history. I have downloaded 5.1 I presume that I can have 2 versions of my eclipseide and switch between them till I get the new one configured taht way I like. As there does not seem to be away to reslove this issue or work around except Not using certain editors.

    #262025 Reply

    Riyad Kalla
    Member

    Find4u,
    I think XMLBuddy installs under the Eclipse/plugins dir, so you’ll have to expand the Eclipse node under Help > Software Updates > Manage COnfiguration to see it. Also, you can have two copies of Eclipse/MyEclipse installed certainly.

    I would suggest grabbing our All In One installer for a perfect setup of MyEclipse all ready to go (you don’t even need a JDK or Eclipse 3.2.1, it’s all included). Once you’ve done that, all you have to do is point it at your old workspace and bammo, you are all set. All your preferences and projects are there, no tweaking required or reconfiguration.

    #262125 Reply

    Riyad,
    Thanks I did a reinstall, not the all in one, seems to be fine, svn missing but will add later, I will not use XML buddy on this version!
    Thanks

    Richard
    PS Do you have any idea when myeclipseide will support Spring 2? Thanks again

    #262142 Reply

    Riyad Kalla
    Member

    Richard,
    Our plan for Spring 2 is probably our next release, but I would point out that you can update the Spring libraries from 1.2 to 2.0 any time you like either adjusting your project classpath directly or by going to Window > Prefs > MYEclipse > Project Capabilities > Spring. Since 2.0 is backward compatable most things should work, but we haven’t done a lot of testing of our wizards and such, so if anything breaks you may need to roll back, or rely on a more manual mode of development.

    BTW thank you for following up with your findings of XML Buddy. We have a pending request in (via another user) with the XML Buddy developer to see why it’s munging up our editors, no word back yet though.

    #262530 Reply

    Thanks for info re spring 2, Once uninstalled XMLBuddy worked fine, was a little difficult to find XMLBuddy to ininstall had to delte jars etc.
    One more little thing is a Junit4 runner availiable?
    Thanks
    Richard

    #262535 Reply

    Riyad Kalla
    Member

    Richard,
    I believe this was added to Eclipse 3.2, so if you are using MyEclipse 5.1, which is based on Eclipse 3.2.1, you are free to run JUnit 4 test cases (IIRC I ran through a few projects that were using JUnit 4 and all the @Test annotations and it worked fine)

Viewing 9 posts - 1 through 9 (of 9 total)
Reply To: opening XML document in spring beans

You must be logged in to post in the forum log in