[JBoss JIRA] (JBIDE-11584) JBOSS BIRT Integration compatibility issue with Hibernate 3.6+
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-11584?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-11584:
------------------------------------------
[~jeffmaury] JBoss BIRT Integration (https://github.com/jbosstools/jbosstools-birt) was deprecated, not actively developed since 4y, shouldn't we close this as WONTDO?
> JBOSS BIRT Integration compatibility issue with Hibernate 3.6+
> --------------------------------------------------------------
>
> Key: JBIDE-11584
> URL: https://issues.jboss.org/browse/JBIDE-11584
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: birt
> Environment: JBoss BIRT Integration version 1.2.0.v20111025-0413-H201-Final
> JBoss BIRT Integration version 1.3.0.v20120413-0659-H849-Beta3
> JBoss Hibernate version 3.6.10.Final
> BIRT Runtime version 3.7.1
> Spring version 3.1.0.RELEASE
> Reporter: Tomas Vala
> Assignee: Snjezana Peco
> Priority: Major
> Labels: birt, oda
> Fix For: 3.3.x
>
>
> BIRT report design utilizing Hibernate DataSource/DataSet with query parameter(s) will trigger below listed error and fail.
> This is believed to be consequence of this incompatible change in Hibernate 3.6, see http://opensource.atlassian.com/projects/hibernate/browse/HHH-5138
> Outcome of several test runs:
> {noformat}
> Hibernate 3.5.6 + BIRT Report w/o query parameter = OK
> Hibernate 3.5.6 + BIRT Report with query parameter = OK
> Hibernate 3.6.7 + BIRT Report w/o query parameter = OK
> Hibernate 3.6.7 + BIRT Report with query parameter = ERROR
> Hibernate 3.6.10 + BIRT Report w/o query parameter = OK
> Hibernate 3.6.10 + BIRT Report with query parameter = ERROR
> {noformat}
> Tested with both stable and development versions of JBoss BIRT Integration jar (1.2.0, 1.3.0) - doesn't seem to have any impact on outcome.
> {noformat}
> 19.4.2012 12:15:33 org.eclipse.birt.report.engine.api.impl.RunAndRenderTask doRun
> SEVERE: Error happened while running the report.
> java.lang.NoSuchFieldError: STRING
> at org.jboss.tools.birt.oda.impl.Parameter.<clinit>(Parameter.java:26)
> at org.jboss.tools.birt.oda.impl.HibernateOdaQuery.setString(HibernateOdaQuery.java:220)
> at org.eclipse.datatools.connectivity.oda.consumer.helper.OdaQuery.setString(OdaQuery.java:738)
> at org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.doSetString(PreparedStatement.java:4310)
> at org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.setString(PreparedStatement.java:3919)
> at org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.setParameterValue(PreparedStatement.java:3134)
> at org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.setParameterValue(PreparedStatement.java:3070)
> at org.eclipse.birt.data.engine.executor.DataSourceQuery.setInputParameterBinding(DataSourceQuery.java:1124)
> at org.eclipse.birt.data.engine.executor.DataSourceQuery.addParameterDefns(DataSourceQuery.java:572)
> at org.eclipse.birt.data.engine.executor.DataSourceQuery.prepare(DataSourceQuery.java:290)
> at org.eclipse.birt.data.engine.impl.PreparedOdaDSQuery$OdaDSQueryExecutor.prepareOdiQuery(PreparedOdaDSQuery.java:455)
> at org.eclipse.birt.data.engine.impl.QueryExecutor.prepareExecution(QueryExecutor.java:341)
> at org.eclipse.birt.data.engine.impl.PreparedQuery.doPrepare(PreparedQuery.java:455)
> at org.eclipse.birt.data.engine.impl.PreparedDataSourceQuery.produceQueryResults(PreparedDataSourceQuery.java:190)
> at org.eclipse.birt.data.engine.impl.PreparedDataSourceQuery.execute(PreparedDataSourceQuery.java:178)
> at org.eclipse.birt.data.engine.impl.PreparedOdaDSQuery.execute(PreparedOdaDSQuery.java:145)
> at org.eclipse.birt.report.data.adapter.impl.DataRequestSessionImpl.execute(DataRequestSessionImpl.java:620)
> at org.eclipse.birt.report.engine.data.dte.DteDataEngine.doExecuteQuery(DteDataEngine.java:152)
> at org.eclipse.birt.report.engine.data.dte.AbstractDataEngine.execute(AbstractDataEngine.java:267)
> at org.eclipse.birt.report.engine.executor.ExecutionContext.executeQuery(ExecutionContext.java:1905)
> at org.eclipse.birt.report.engine.executor.QueryItemExecutor.executeQuery(QueryItemExecutor.java:80)
> at org.eclipse.birt.report.engine.executor.DataItemExecutor.execute(DataItemExecutor.java:75)
> at org.eclipse.birt.report.engine.internal.executor.dup.SuppressDuplicateItemExecutor.execute(SuppressDuplicateItemExecutor.java:43)
> at org.eclipse.birt.report.engine.internal.executor.wrap.WrappedReportItemExecutor.execute(WrappedReportItemExecutor.java:46)
> at org.eclipse.birt.report.engine.internal.executor.l18n.LocalizedReportItemExecutor.execute(LocalizedReportItemExecutor.java:34)
> at org.eclipse.birt.report.engine.layout.html.HTMLBlockStackingLM.layoutNodes(HTMLBlockStackingLM.java:65)
> at org.eclipse.birt.report.engine.layout.html.HTMLStackingLM.layoutChildren(HTMLStackingLM.java:26)
> at org.eclipse.birt.report.engine.layout.html.HTMLAbstractLM.layout(HTMLAbstractLM.java:140)
> at org.eclipse.birt.report.engine.layout.html.HTMLInlineStackingLM.resumeLayout(HTMLInlineStackingLM.java:111)
> at org.eclipse.birt.report.engine.layout.html.HTMLInlineStackingLM.layoutNodes(HTMLInlineStackingLM.java:160)
> at org.eclipse.birt.report.engine.layout.html.HTMLStackingLM.layoutChildren(HTMLStackingLM.java:26)
> at org.eclipse.birt.report.engine.layout.html.HTMLAbstractLM.layout(HTMLAbstractLM.java:140)
> at org.eclipse.birt.report.engine.layout.html.HTMLBlockStackingLM.layoutNodes(HTMLBlockStackingLM.java:70)
> at org.eclipse.birt.report.engine.layout.html.HTMLStackingLM.layoutChildren(HTMLStackingLM.java:26)
> at org.eclipse.birt.report.engine.layout.html.HTMLTableLM.layoutChildren(HTMLTableLM.java:132)
> at org.eclipse.birt.report.engine.layout.html.HTMLAbstractLM.layout(HTMLAbstractLM.java:140)
> at org.eclipse.birt.report.engine.layout.html.HTMLBlockStackingLM.layoutNodes(HTMLBlockStackingLM.java:70)
> at org.eclipse.birt.report.engine.layout.html.HTMLPageLM.layout(HTMLPageLM.java:92)
> at org.eclipse.birt.report.engine.layout.html.HTMLReportLayoutEngine.layout(HTMLReportLayoutEngine.java:100)
> at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.doRun(RunAndRenderTask.java:180)
> at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run(RunAndRenderTask.java:77)
> {noformat}
> An example of simple JPQL query featuring problematic parameter:
> {noformat}
> SELECT
> id,
> attribute1,
> attribute2
> FROM
> MyEntity my
> WHERE
> id = ?
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-11584) JBOSS BIRT Integration compatibility issue with Hibernate 3.6+
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-11584?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-11584 at 7/2/19 4:05 PM:
------------------------------------------------------------------
[~jeffmaury] JBoss BIRT Integration (https://github.com/jbosstools/jbosstools-birt) was deprecated, not actively developed since 4y, shouldn't we close this 7y+ old issue as WONTDO?
was (Author: adietish):
[~jeffmaury] JBoss BIRT Integration (https://github.com/jbosstools/jbosstools-birt) was deprecated, not actively developed since 4y, shouldn't we close this as WONTDO?
> JBOSS BIRT Integration compatibility issue with Hibernate 3.6+
> --------------------------------------------------------------
>
> Key: JBIDE-11584
> URL: https://issues.jboss.org/browse/JBIDE-11584
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: birt
> Environment: JBoss BIRT Integration version 1.2.0.v20111025-0413-H201-Final
> JBoss BIRT Integration version 1.3.0.v20120413-0659-H849-Beta3
> JBoss Hibernate version 3.6.10.Final
> BIRT Runtime version 3.7.1
> Spring version 3.1.0.RELEASE
> Reporter: Tomas Vala
> Assignee: Snjezana Peco
> Priority: Major
> Labels: birt, oda
> Fix For: 3.3.x
>
>
> BIRT report design utilizing Hibernate DataSource/DataSet with query parameter(s) will trigger below listed error and fail.
> This is believed to be consequence of this incompatible change in Hibernate 3.6, see http://opensource.atlassian.com/projects/hibernate/browse/HHH-5138
> Outcome of several test runs:
> {noformat}
> Hibernate 3.5.6 + BIRT Report w/o query parameter = OK
> Hibernate 3.5.6 + BIRT Report with query parameter = OK
> Hibernate 3.6.7 + BIRT Report w/o query parameter = OK
> Hibernate 3.6.7 + BIRT Report with query parameter = ERROR
> Hibernate 3.6.10 + BIRT Report w/o query parameter = OK
> Hibernate 3.6.10 + BIRT Report with query parameter = ERROR
> {noformat}
> Tested with both stable and development versions of JBoss BIRT Integration jar (1.2.0, 1.3.0) - doesn't seem to have any impact on outcome.
> {noformat}
> 19.4.2012 12:15:33 org.eclipse.birt.report.engine.api.impl.RunAndRenderTask doRun
> SEVERE: Error happened while running the report.
> java.lang.NoSuchFieldError: STRING
> at org.jboss.tools.birt.oda.impl.Parameter.<clinit>(Parameter.java:26)
> at org.jboss.tools.birt.oda.impl.HibernateOdaQuery.setString(HibernateOdaQuery.java:220)
> at org.eclipse.datatools.connectivity.oda.consumer.helper.OdaQuery.setString(OdaQuery.java:738)
> at org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.doSetString(PreparedStatement.java:4310)
> at org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.setString(PreparedStatement.java:3919)
> at org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.setParameterValue(PreparedStatement.java:3134)
> at org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.setParameterValue(PreparedStatement.java:3070)
> at org.eclipse.birt.data.engine.executor.DataSourceQuery.setInputParameterBinding(DataSourceQuery.java:1124)
> at org.eclipse.birt.data.engine.executor.DataSourceQuery.addParameterDefns(DataSourceQuery.java:572)
> at org.eclipse.birt.data.engine.executor.DataSourceQuery.prepare(DataSourceQuery.java:290)
> at org.eclipse.birt.data.engine.impl.PreparedOdaDSQuery$OdaDSQueryExecutor.prepareOdiQuery(PreparedOdaDSQuery.java:455)
> at org.eclipse.birt.data.engine.impl.QueryExecutor.prepareExecution(QueryExecutor.java:341)
> at org.eclipse.birt.data.engine.impl.PreparedQuery.doPrepare(PreparedQuery.java:455)
> at org.eclipse.birt.data.engine.impl.PreparedDataSourceQuery.produceQueryResults(PreparedDataSourceQuery.java:190)
> at org.eclipse.birt.data.engine.impl.PreparedDataSourceQuery.execute(PreparedDataSourceQuery.java:178)
> at org.eclipse.birt.data.engine.impl.PreparedOdaDSQuery.execute(PreparedOdaDSQuery.java:145)
> at org.eclipse.birt.report.data.adapter.impl.DataRequestSessionImpl.execute(DataRequestSessionImpl.java:620)
> at org.eclipse.birt.report.engine.data.dte.DteDataEngine.doExecuteQuery(DteDataEngine.java:152)
> at org.eclipse.birt.report.engine.data.dte.AbstractDataEngine.execute(AbstractDataEngine.java:267)
> at org.eclipse.birt.report.engine.executor.ExecutionContext.executeQuery(ExecutionContext.java:1905)
> at org.eclipse.birt.report.engine.executor.QueryItemExecutor.executeQuery(QueryItemExecutor.java:80)
> at org.eclipse.birt.report.engine.executor.DataItemExecutor.execute(DataItemExecutor.java:75)
> at org.eclipse.birt.report.engine.internal.executor.dup.SuppressDuplicateItemExecutor.execute(SuppressDuplicateItemExecutor.java:43)
> at org.eclipse.birt.report.engine.internal.executor.wrap.WrappedReportItemExecutor.execute(WrappedReportItemExecutor.java:46)
> at org.eclipse.birt.report.engine.internal.executor.l18n.LocalizedReportItemExecutor.execute(LocalizedReportItemExecutor.java:34)
> at org.eclipse.birt.report.engine.layout.html.HTMLBlockStackingLM.layoutNodes(HTMLBlockStackingLM.java:65)
> at org.eclipse.birt.report.engine.layout.html.HTMLStackingLM.layoutChildren(HTMLStackingLM.java:26)
> at org.eclipse.birt.report.engine.layout.html.HTMLAbstractLM.layout(HTMLAbstractLM.java:140)
> at org.eclipse.birt.report.engine.layout.html.HTMLInlineStackingLM.resumeLayout(HTMLInlineStackingLM.java:111)
> at org.eclipse.birt.report.engine.layout.html.HTMLInlineStackingLM.layoutNodes(HTMLInlineStackingLM.java:160)
> at org.eclipse.birt.report.engine.layout.html.HTMLStackingLM.layoutChildren(HTMLStackingLM.java:26)
> at org.eclipse.birt.report.engine.layout.html.HTMLAbstractLM.layout(HTMLAbstractLM.java:140)
> at org.eclipse.birt.report.engine.layout.html.HTMLBlockStackingLM.layoutNodes(HTMLBlockStackingLM.java:70)
> at org.eclipse.birt.report.engine.layout.html.HTMLStackingLM.layoutChildren(HTMLStackingLM.java:26)
> at org.eclipse.birt.report.engine.layout.html.HTMLTableLM.layoutChildren(HTMLTableLM.java:132)
> at org.eclipse.birt.report.engine.layout.html.HTMLAbstractLM.layout(HTMLAbstractLM.java:140)
> at org.eclipse.birt.report.engine.layout.html.HTMLBlockStackingLM.layoutNodes(HTMLBlockStackingLM.java:70)
> at org.eclipse.birt.report.engine.layout.html.HTMLPageLM.layout(HTMLPageLM.java:92)
> at org.eclipse.birt.report.engine.layout.html.HTMLReportLayoutEngine.layout(HTMLReportLayoutEngine.java:100)
> at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.doRun(RunAndRenderTask.java:180)
> at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run(RunAndRenderTask.java:77)
> {noformat}
> An example of simple JPQL query featuring problematic parameter:
> {noformat}
> SELECT
> id,
> attribute1,
> attribute2
> FROM
> MyEntity my
> WHERE
> id = ?
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-11606) Mavenize JBoss Tools Birt releases
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-11606?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-11606:
------------------------------------------
[~jeffmaury] JBoss BIRT Integration (https://github.com/jbosstools/jbosstools-birt) was deprecated, not actively developed since 4y, shouldn't we close this 7y+ old issue as WONTDO?
> Mavenize JBoss Tools Birt releases
> ----------------------------------
>
> Key: JBIDE-11606
> URL: https://issues.jboss.org/browse/JBIDE-11606
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: birt
> Reporter: Tomas Vala
> Priority: Minor
> Labels: jboss, maven
> Fix For: 4.0.x
>
>
> Hello,
> please consider making JBoss Tools releases available through maven repository.
> For reference: Eclipse is aiming to officialy provide maven feed for BIRT Runtime (Business Intelligence and Reporting Tools) from Juno release on (2012/6). It would be nice and practical if at least portion of JBoss Tools, JBoss BIRT Integration ODA plugin would follow this trend.
> {noformat}
> Personal opinion based on recent experience:
> I consider current distribution channels and methods to be somewhat lacking compared to nowadays possibilities. Weird artificial dependencies of JBoss BIRT Integration Eclipse feature, direct download links for individual jars are rather difficult to find on the web site.
> {noformat}
> Tomas
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-12597) JBOSS BIRT Integration compatibility issue with Hibernate 4.0+
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-12597?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-12597:
------------------------------------------
[~jeffmaury] JBoss BIRT Integration (https://github.com/jbosstools/jbosstools-birt) was deprecated, not actively developed since 4y, shouldn't we close this as WONTDO?
> JBOSS BIRT Integration compatibility issue with Hibernate 4.0+
> ---------------------------------------------------------------
>
> Key: JBIDE-12597
> URL: https://issues.jboss.org/browse/JBIDE-12597
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: birt
> Affects Versions: 4.0.x
> Environment: JBoss BIRT Integration version 1.4.0.Alpha2-v20120910-1613-B34
> JBoss Hibernate version 4.1.7
> BIRT runtime version 3.7.1
> Reporter: Tomas Vala
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: birt, oda
> Fix For: 4.0.x
>
>
> Hello,
> this is a follow up to previous still unresolved report JBIDE-11584. Now with Hibernate release 4.x the JBoss BIRT ODA plugin is broken even more than before. It doesn't work at all and even doesn't compile against Hibernate 4.x due to backward incompatible changes made to Hibernate API.
> Have you abandoned this project altogether (without announcing it in advance) or is there at least maintenance release in the works aimed for near future? Current situation is not good.
> Thanks,
> Tomas
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-3113) Consolidation/clean up of preference pages
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-3113?page=com.atlassian.jira.plugin... ]
André Dietisheim resolved JBIDE-3113.
-------------------------------------
Resolution: Won't Do
> Consolidation/clean up of preference pages
> ------------------------------------------
>
> Key: JBIDE-3113
> URL: https://issues.jboss.org/browse/JBIDE-3113
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common, drools, jbpm
> Affects Versions: 3.0.0.cr1
> Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk
> Reporter: John Graham
> Assignee: Kris Verlaenen
> Priority: Critical
> Labels: usability
> Fix For: 4.12.0.Final
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> JBT currently has three preference page categories:
> 1. Drools
> 2. JBoss jBPM
> 3. JBoss Tools
> The first two should be listed as subsections of the JBoss Tools category. Alternatively, I suggest that the top level category should just be JBoss:
> - JBoss
> -- Drools
> -- jBPM
> Also, the JBoss Tools and JBoss jBPM top level pages in each of these categories do not expose preferences, but rather the default buttons or simply a label ("JBoss Tools"). These top level pages should show overall JBT preferences. See the Java preferences or other examples in the Eclipse platform for this idea. (Also note that the DTP 1.6.x way of doing this is wrong... ;) )
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-3113) Consolidation/clean up of preference pages
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-3113?page=com.atlassian.jira.plugin... ]
André Dietisheim commented on JBIDE-3113:
-----------------------------------------
Drools was deprecated, I'll thus resolve this as WONTDO.
> Consolidation/clean up of preference pages
> ------------------------------------------
>
> Key: JBIDE-3113
> URL: https://issues.jboss.org/browse/JBIDE-3113
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common, drools, jbpm
> Affects Versions: 3.0.0.cr1
> Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk
> Reporter: John Graham
> Assignee: Kris Verlaenen
> Priority: Critical
> Labels: usability
> Fix For: 4.12.0.Final
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> JBT currently has three preference page categories:
> 1. Drools
> 2. JBoss jBPM
> 3. JBoss Tools
> The first two should be listed as subsections of the JBoss Tools category. Alternatively, I suggest that the top level category should just be JBoss:
> - JBoss
> -- Drools
> -- jBPM
> Also, the JBoss Tools and JBoss jBPM top level pages in each of these categories do not expose preferences, but rather the default buttons or simply a label ("JBoss Tools"). These top level pages should show overall JBT preferences. See the Java preferences or other examples in the Eclipse platform for this idea. (Also note that the DTP 1.6.x way of doing this is wrong... ;) )
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-6608) Ability to remove drools nature from project
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-6608?page=com.atlassian.jira.plugin... ]
André Dietisheim resolved JBIDE-6608.
-------------------------------------
Resolution: Won't Do
> Ability to remove drools nature from project
> --------------------------------------------
>
> Key: JBIDE-6608
> URL: https://issues.jboss.org/browse/JBIDE-6608
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: drools
> Affects Versions: 3.1.0.GA
> Reporter: Libor Zoubek
> Priority: Major
> Fix For: 4.12.0.Final, 3.3.x
>
>
> Regarding to http://community.jboss.org/message/552490 at this time, there is no possibility to remove drools "nature" (as it is probably not the nature in sense of eclipse nature)
> We should be able to remove drools from project. Menu item 'Convert to drools project' should be called 'Add drools nature' and when a project has a drools nature it should be called 'Remove drools nature'.
> Maybe it would be good, not to have 'Convert to drools project' menu item in main context menu, but move it into 'Configure' submenu
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months