indent-number error

newbie321
edited February 11, 2022 in Analytics #1
<div>Hi, </div>
<div> </div>
<div>I keep hitting the 'indent-number' error when trying to define more columns in the pojo-based dataset.    One can say that this is an eclipse problem, which it sure looks like it since the trace points to 'org.apache.xalan.processor.TransformerFactoryImpl.setAttribute(TransformerFactoryImpl.java:485)' but since it is caused through BIRT, I figured I'd post here to see if anyone knows how to solve this problem.  </div>
<div> </div>
<div>So the behaviour is as follows: When adding columns to a newly created pojo-based dataset, I can add as many columns as I want.  Now, when I want to update the dataset (ie add more columns or delete some) I get this error thrown when I press OK button.    I am including the error below.  </div>
<div> </div>
<div>Any suggestions?</div>
<div>Thanks! </div>
<div> </div>
<div>
<pre class="_prettyXprint">
eclipse.buildId=4.5.1.M20150904-0015
java.version=1.7.0_79
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.java.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.java.product

org.eclipse.ui
Error
Mon Oct 26 17:20:58 CDT 2015
Unhandled event loop exception

java.lang.IllegalArgumentException: Not supported: indent-number
at org.apache.xalan.processor.TransformerFactoryImpl.setAttribute(TransformerFactoryImpl.java:485)
at org.eclipse.birt.data.oda.pojo.util.PojoQueryWriter.write(PojoQueryWriter.java:70)
at org.eclipse.birt.data.oda.pojo.ui.util.Utils.savePojoQuery(Utils.java:609)
at org.eclipse.birt.data.oda.pojo.ui.impl.dialogs.ColumnMappingWizardPage.collectDataSetDesign(ColumnMappingWizardPage.java:190)
at org.eclipse.datatools.connectivity.oda.design.internal.ui.DataSetWizardPageCore.finishDataSetDesign(DataSetWizardPageCore.java:395)
at org.eclipse.datatools.connectivity.oda.design.internal.ui.DataSetWizardBase.collectDataSetDesignFromPage(DataSetWizardBase.java:365)
at org.eclipse.datatools.connectivity.oda.design.internal.ui.DataSetWizardBase.finishDataSetDesign(DataSetWizardBase.java:387)
at org.eclipse.datatools.connectivity.oda.design.internal.ui.DataSetWizardBase.getResponseSession(DataSetWizardBase.java:123)
at org.eclipse.datatools.connectivity.oda.design.internal.designsession.DataSetDesignSessionBase.finishDataSetDesign(DataSetDesignSessionBase.java:442)
at org.eclipse.datatools.connectivity.oda.design.internal.designsession.DataSetDesignSessionBase.flush(DataSetDesignSessionBase.java:237)
at org.eclipse.datatools.connectivity.oda.design.ui.designsession.DataSetDesignSession.flush(DataSetDesignSession.java:136)
at org.eclipse.birt.report.designer.data.ui.dataset.PropertyPageWrapper.canLeave(PropertyPageWrapper.java:126)
at org.eclipse.birt.report.designer.data.ui.dataset.PropertyPageWrapper.performOk(PropertyPageWrapper.java:101)
at org.eclipse.birt.report.designer.data.ui.property.AbstractPropertyDialog.okPressed(AbstractPropertyDialog.java:790)
at org.eclipse.birt.report.designer.data.ui.property.AbstractPropertyDialog.okPressed(AbstractPropertyDialog.java:765)
at org.eclipse.birt.report.designer.data.ui.dataset.DataSetEditor.okPressed(DataSetEditor.java:683)
at org.eclipse.birt.report.designer.data.ui.property.AbstractPropertyDialog.buttonPressed(AbstractPropertyDialog.java:650)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
at org.eclipse.jface.window.Window.open(Window.java:803)
at org.eclipse.birt.report.designer.ui.dialogs.BaseDialog.open(BaseDialog.java:117)
at org.eclipse.birt.report.designer.data.ui.providers.EditableDataSetNodeProvider.performEdit(EditableDataSetNodeProvider.java:102)
at org.eclipse.birt.report.designer.internal.ui.views.DefaultNodeProvider.performRequest(DefaultNodeProvider.java:472)
at org.eclipse.birt.report.designer.internal.ui.views.actions.EditAction.doAction(EditAction.java:85)
at org.eclipse.birt.report.designer.internal.ui.views.actions.AbstractElementAction.run(AbstractElementAction.java:70)
at org.eclipse.birt.report.designer.internal.ui.views.RenameListener.doubleClick(RenameListener.java:214)
at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:832)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:829)
at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1470)
at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1263)
at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:252)
at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:249)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:311)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
</pre>
</div>
<p> </p>

Comments

  • i am facing same issue. have you got any solution?

  • Warning No formatter is installed for the format ipb
  • newbie321
    edited June 25, 2019 #4

    @jfranken,
    is this an eclipse bug or a birt plugin bug?

  • The "product" on the bug ticket says BIRT. It sounds like the source of the bug is in the Apache Xalan plugin used by BIRT.

    Warning No formatter is installed for the format ipb
  • newbie321
    edited June 25, 2019 #6

    @jfranken
    I sort of don't want to say what I should not be saying, but...

    ... the bug has been since at least 2015. Nobody resolved it. Does that mean that BIRT (open source version) is effectively a dead project since no people appear to work on it?

  • There have been several product releases since the bug was reported, and 97 code commits in the last year according the the Eclipse website. I have never worked on the project, but it sounds like this issue might involve a third party.

    Warning No formatter is installed for the format ipb
  • I forgot to mention the latest developments with OpenText's commercial version of BIRT/iHub. A new version was released about a week ago- Magellan BI & Reporting 16.6. The main item I wanted to point out is that the product is being re-branded as Magellan BI & Reporting, but it is the same basic product with some new features (enhanced dashboard filtering, built-in support for Treemap and Histogram visualizations, Apache Nifi support, etc). The BIRT reporting features have also been integrated with Magellan's text mining and AI capabilities.

    I'm not in marketing and I'm still learning about the new release, but since the question was asked about what is happening with the product, I thought I'd take the opportunity to promote a little. :)

    Warning No formatter is installed for the format ipb
  • @jfranken said:
    I forgot to mention the latest developments with OpenText's commercial version of BIRT/iHub. A new version was released about a week ago- Magellan BI & Reporting 16.6. The main item I wanted to point out is that the product is being re-branded as Magellan BI & Reporting, but it is the same basic product with some new features (enhanced dashboard filtering, built-in support for Treemap and Histogram visualizations, Apache Nifi support, etc). The BIRT reporting features have also been integrated with Magellan's text mining and AI capabilities.

    I'm not in marketing and I'm still learning about the new release, but since the question was asked about what is happening with the product, I thought I'd take the opportunity to promote a little. :)

    Thanks so much for the update on this. This is very timely and appropriate. I was actually pondering where openText stands with its birt products. Your update sheds light on that. This is very good news that OpenText is still pursuing the BIRT venue and is improving it.
    Thanks so much for an update!