[JBoss JIRA] (JBIDE-24141) Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-24141?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24141:
-------------------------------
Fix Version/s: 4.12.0.Final
(was: 4.13.x)
> Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component
> ------------------------------------------------------------
>
> Key: JBIDE-24141
> URL: https://issues.jboss.org/browse/JBIDE-24141
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: webservices
> Affects Versions: 4.4.4.AM2, 4.5.0.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: testfailure
> Fix For: 4.12.0.Final
>
>
> *2 Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component:*
> https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
> [Search for Test Failure JIRAs in JBIDE 4.4.4.AM2 for webservices component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...]
> -----
> {code}
> All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.15 sec 2
> {code}
> {code}
> Failed
> org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication
> Failing for the past 2 builds (Since Unstable#74 )
> Took 0.15 sec.
> add description
> Error Message
> Expected: <6>
> but: was <10>
> Stacktrace
> java.lang.AssertionError:
> Expected: <6>
> but: was <10>
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.junit.Assert.assertThat(Assert.java:956)
> at org.junit.Assert.assertThat(Assert.java:923)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication(JaxrsMetamodelChangedProcessorTestCase.java:358)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-24141) Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-24141?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-24141.
------------------------------
Resolution: Done
> Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component
> ------------------------------------------------------------
>
> Key: JBIDE-24141
> URL: https://issues.jboss.org/browse/JBIDE-24141
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: webservices
> Affects Versions: 4.4.4.AM2, 4.5.0.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: testfailure
> Fix For: 4.12.0.Final
>
>
> *2 Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component:*
> https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
> [Search for Test Failure JIRAs in JBIDE 4.4.4.AM2 for webservices component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...]
> -----
> {code}
> All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.15 sec 2
> {code}
> {code}
> Failed
> org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication
> Failing for the past 2 builds (Since Unstable#74 )
> Took 0.15 sec.
> add description
> Error Message
> Expected: <6>
> but: was <10>
> Stacktrace
> java.lang.AssertionError:
> Expected: <6>
> but: was <10>
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.junit.Assert.assertThat(Assert.java:956)
> at org.junit.Assert.assertThat(Assert.java:923)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication(JaxrsMetamodelChangedProcessorTestCase.java:358)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-11172) Database Development: Postgres 9.1 tables are not listed
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-11172?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-11172 at 7/3/19 4:56 AM:
------------------------------------------------------------------
[~jeffmaury] I didnt see any bug in Eclipse that would tell us that this was fixed.
[~koen.aers] is this still a valid issue?
was (Author: adietish):
[~koen.aers] is this still a valid issue?
> Database Development: Postgres 9.1 tables are not listed
> --------------------------------------------------------
>
> Key: JBIDE-11172
> URL: https://issues.jboss.org/browse/JBIDE-11172
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, upstream
> Environment: Mac OS X Lion
> Reporter: Burrsitis Sutter
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.13.x
>
> Attachments: Screen Shot 2012-03-05 at 7.52.01 PM.png, Screen Shot 2012-03-05 at 7.55.21 PM.png, Screen Shot 2012-03-05 at 8.00.22 PM.png, Screen Shot 2012-03-05 at 8.00.38 PM.png, pagila-ds.xml, postgresql-9.1-901.jdbc4.jar
>
>
> Postgres 9.1 - connection to a pagila database schema does not return a list of tables in the database explorer, nor in the Hibernate configuration. See attached screenshots.
--
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 Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-12597?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-12597.
------------------------------
Resolution: Won't Do
> 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
>
> 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-9950) birt: ajax rendering does not work
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-9950?page=com.atlassian.jira.plugin... ]
Jeff MAURY closed JBIDE-9950.
-----------------------------
Resolution: Won't Do
> birt: ajax rendering does not work
> ----------------------------------
>
> Key: JBIDE-9950
> URL: https://issues.jboss.org/browse/JBIDE-9950
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: birt
> Affects Versions: 3.3.0.M3
> Reporter: u j
> Assignee: Snjezana Peco
> Priority: Major
>
> When ajax-rendering a b:birt component in a JSF application (not Seam), the parameters b:param are not sent to Birt, so you get
> 10:33:54,187 SEVERE [org.jboss.tools.birt] (ajp-127.0.0.1-127.0.0.1-8009-1) the value of parameter estabId is invalid: org.eclipse.birt.core.exception.CoreException: Can not convert the value of to Integer type.
> at org.eclipse.birt.core.data.DataTypeUtil.toInteger(DataTypeUtil.java:276) [org.eclipse.birt.runtime_3.7.1.v20110913-1734.jar:]
> at org.jboss.tools.birt.servlet.JBossBirtServlet.stringToObject(JBossBirtServlet.java:183) [jboss-birt-servlet.jar:]
> at org.jboss.tools.birt.servlet.JBossBirtServlet.evaluateParameterValues(JBossBirtServlet.java:142) [jboss-birt-servlet.jar:]
> at org.jboss.tools.birt.servlet.JBossBirtServlet.doGet(JBossBirtServlet.java:108) [jboss-birt-servlet.jar:]
> at org.jboss.tools.birt.servlet.JBossBirtServlet.doPost(JBossBirtServlet.java:123) [jboss-birt-servlet.jar:]
> This happens e.g. in a popup or a collapsiblePanel (RichFaces).
--
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 Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-11584?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-11584.
------------------------------
Resolution: Won't Do
> 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
>
> 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