July 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-612) Hibernate Configurations view doesn't reflect the changes in mappings sources

by Denis Golovin (JIRA)

Hibernate Configurations view doesn't reflect the changes in mappings sources ----------------------------------------------------------------------------- Key: JBIDE-612 URL: http://jira.jboss.com/jira/browse/JBIDE-612 Project: JBoss Tools Issue Type: Bug Components: Hibernate Reporter: Denis Golovin Assigned To: Denis Golovin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6378) Missing feature details in datatools.connectivity.feature

by Nick Boldt (JIRA)

Missing feature details in datatools.connectivity.feature --------------------------------------------------------- Key: JBIDE-6378 URL: https://jira.jboss.org/browse/JBIDE-6378 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Reporter: Nick Boldt Attachments: Screenshot-6.png Installing from jbosstools-tdesigner-Update-H10-2010-05-24_21-20-59.zip, I see featureName and description instead of an actual feature name and descriptive text. Please update your feature.xml / feature.properties and make sure BOTH are added to the list of files built/exported via your build.properties file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6521) Revise jBPM 3 Deployment Mechanism

by Koen Aers (JIRA)

Revise jBPM 3 Deployment Mechanism ---------------------------------- Key: JBIDE-6521 URL: https://jira.jboss.org/browse/JBIDE-6521 Project: Tools (JBoss Tools) Issue Type: Task Components: jbpm Affects Versions: 3.1.1 Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.1.2, 3.2.0.M1 This issue incorporates several other issues. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBDS-1210) generate update site and zip

by Nick Boldt (JIRA)

generate update site and zip ---------------------------- Key: JBDS-1210 URL: https://jira.jboss.org/jira/browse/JBDS-1210 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Reporter: Nick Boldt Assignee: Nick Boldt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-6578) BIRT report (Hibernate ODA) with DataSet on same DataSource crash

by Martin Frey (JIRA)

BIRT report (Hibernate ODA) with DataSet on same DataSource crash ----------------------------------------------------------------- Key: JBIDE-6578 URL: https://jira.jboss.org/browse/JBIDE-6578 Project: Tools (JBoss Tools) Issue Type: Bug Components: birt Affects Versions: 3.0.3.GA Environment: JBoss AS 4.2.2.GA Seam 2.2.0.GA Eclipse 3.4 Reporter: Martin Frey Assignee: Snjezana Peco I've created a BIRT report using the Hibernate Datasource and two Datasets. If i connect both Datasets to the Datasource the second query will fail. This happens also in the Preview of the ReportDesigner. After looking a little into it i saw that the SessionFactory in the ServerOdaFactory is null during the second HibernateOdaQuery.parseQuery() call. -> session = getSessionFactory().openSession(); throws NullPointer If i use multiple DataSources (one per DataSet) the problem goes away. If i can provide any more information just let me know. 15:06:09,937 ERROR [STDERR] 05.07.2010 15:06:09 org.eclipse.birt.data.engine.odaconsumer.Connection prepareOdaQuery SCHWERWIEGEND: Cannot prepare statement. org.eclipse.datatools.connectivity.oda.OdaException at org.jboss.tools.birt.oda.impl.AbstractOdaFactory.parseQuery(AbstractOdaFactory.java:114) at org.jboss.tools.birt.oda.impl.AbstractOdaFactory.prepare(AbstractOdaFactory.java:51) at org.jboss.tools.birt.oda.impl.HibernateOdaQuery.prepare(HibernateOdaQuery.java:45) at org.eclipse.datatools.connectivity.oda.consumer.helper.OdaQuery.doPrepare(OdaQuery.java:210) at org.eclipse.datatools.connectivity.oda.consumer.helper.OdaQuery.prepare(OdaQuery.java:167) at org.eclipse.birt.data.engine.odaconsumer.Connection.prepareOdaQuery(Connection.java:222) at org.eclipse.birt.data.engine.odaconsumer.Connection.prepareStatement(Connection.java:159) at org.eclipse.birt.data.engine.executor.DataSource.prepareStatement(DataSource.java:309) at org.eclipse.birt.data.engine.executor.DataSourceQuery.prepare(DataSourceQuery.java:261) at org.eclipse.birt.data.engine.impl.PreparedOdaDSQuery$OdaDSQueryExecutor.prepareOdiQuery(PreparedOdaDSQuery.java:345) at org.eclipse.birt.data.engine.impl.QueryExecutor.prepareExecution(QueryExecutor.java:331) at org.eclipse.birt.data.engine.impl.PreparedQuery.doPrepare(PreparedQuery.java:498) at org.eclipse.birt.data.engine.impl.PreparedDataSourceQuery.produceQueryResults(PreparedDataSourceQuery.java:189) at org.eclipse.birt.data.engine.impl.PreparedDataSourceQuery.execute(PreparedDataSourceQuery.java:177) at org.eclipse.birt.data.engine.impl.PreparedOdaDSQuery.execute(PreparedOdaDSQuery.java:143) at org.eclipse.birt.report.data.adapter.impl.DataRequestSessionImpl.execute(DataRequestSessionImpl.java:482) at org.eclipse.birt.report.engine.data.dte.DteDataEngine.doExecuteQuery(DteDataEngine.java:115) at org.eclipse.birt.report.engine.data.dte.AbstractDataEngine.execute(AbstractDataEngine.java:253) at org.eclipse.birt.report.engine.executor.ExecutionContext.executeQuery(ExecutionContext.java:1755) at org.eclipse.birt.report.engine.executor.QueryItemExecutor.executeQuery(QueryItemExecutor.java:77) at org.eclipse.birt.report.engine.executor.TableItemExecutor.execute(TableItemExecutor.java:62) at org.eclipse.birt.report.engine.internal.executor.dup.SuppressDuplicateItemExecutor.execute(SuppressDuplicateItemExecutor.java:42) at org.eclipse.birt.report.engine.internal.executor.wrap.WrappedReportItemExecutor.execute(WrappedReportItemExecutor.java:45) at org.eclipse.birt.report.engine.internal.executor.l18n.LocalizedReportItemExecutor.execute(LocalizedReportItemExecutor.java:33) at org.eclipse.birt.report.engine.layout.html.HTMLBlockStackingLM.layoutNodes(HTMLBlockStackingLM.java:63) at org.eclipse.birt.report.engine.layout.html.HTMLPageLM.layout(HTMLPageLM.java:90) at org.eclipse.birt.report.engine.layout.html.HTMLReportLayoutEngine.layout(HTMLReportLayoutEngine.java:101) at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.doRun(RunAndRenderTask.java:151) at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run(RunAndRenderTask.java:72) at org.eclipse.birt.report.service.ReportEngineService.runAndRenderReport(ReportEngineService.java:877) at org.eclipse.birt.report.service.BirtViewerReportService.runAndRenderReport(BirtViewerReportService.java:938) at org.eclipse.birt.report.service.actionhandler.BirtRunAndRenderActionHandler.__execute(BirtRunAndRenderActionHandler.java:76) at org.eclipse.birt.report.service.actionhandler.AbstractBaseActionHandler.execute(AbstractBaseActionHandler.java:90) at org.eclipse.birt.report.presentation.aggregation.layout.RunFragment.doService(RunFragment.java:120) at org.eclipse.birt.report.presentation.aggregation.layout.FramesetFragment.service(FramesetFragment.java:86) at org.eclipse.birt.report.servlet.ViewerServlet.__doGet(ViewerServlet.java:181) at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet.doGet(BirtSoapMessageDispatcherServlet.java:160) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet.service(BirtSoapMessageDispatcherServlet.java:122) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.eclipse.birt.report.filter.ViewerFilter.doFilter(ViewerFilter.java:68) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6572) seam tests missing maven metadata

by Nick Boldt (JIRA)

seam tests missing maven metadata --------------------------------- Key: JBIDE-6572 URL: https://jira.jboss.org/browse/JBIDE-6572 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.M1 Reporter: Nick Boldt Assignee: Denis Golovin Priority: Optional Been seeing some new warnings in the log for seam tests: [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.seam.tests:org.jboss.tools.seam.core.test:eclipse-test-plugin:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-antrun-plugin is missing. @ [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.seam.tests:org.jboss.tools.seam201GA.core.test:eclipse-test-plugin:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-antrun-plugin is missing. @ [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.seam.tests:org.jboss.tools.seam202SP1.core.test:eclipse-test-plugin:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-antrun-plugin is missing. @ [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.seam.tests:org.jboss.tools.seam203CR1.core.test:eclipse-test-plugin:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-antrun-plugin is missing. @ [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.seam.tests:org.jboss.tools.seam121EAP.core.test:eclipse-test-plugin:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-antrun-plugin is missing. @ [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.tests:org.jboss.tools.seamfp.core.test:eclipse-test-plugin:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-antrun-plugin is missing. @ [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.seam.tests:org.jboss.tools.seam.ui.test:eclipse-test-plugin:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-antrun-plugin is missing. @ [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.seam.tests:org.jboss.tools.seam201GA.ui.test:eclipse-test-plugin:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-antrun-plugin is missing. @ [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.seam.tests:org.jboss.tools.seam202SP1.ui.test:eclipse-test-plugin:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-antrun-plugin is missing. @ [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.seam.tests:org.jboss.tools.seam203CR1.ui.test:eclipse-test-plugin:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-antrun-plugin is missing. @ [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.tests:org.jboss.tools.seam211GA.ui.test:eclipse-test-plugin:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-antrun-plugin is missing. @ [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.seam.tests:org.jboss.tools.seam220CR1.ui.test:eclipse-test-plugin:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-antrun-plugin is missing. @ [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.tests:org.jboss.tools.seam220GA.ui.test:eclipse-test-plugin:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-antrun-plugin is missing. @ [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.seam.tests:org.jboss.tools.seam121EAP.ui.test:eclipse-test-plugin:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-antrun-plugin is missing. @ [WARNING] [WARNING] Some problems were encountered while building the effective model for org.jboss.tools.seam.tests:org.jboss.tools.seamfp.ui.test:eclipse-test-plugin:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-antrun-plugin is missing. @ [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2.0.M1/134/console -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6381) increment .tags files to correct levels for JBT 3.2.0.M1 and JBDS 4.0.0.M1

by Nick Boldt (JIRA)

increment .tags files to correct levels for JBT 3.2.0.M1 and JBDS 4.0.0.M1 -------------------------------------------------------------------------- Key: JBIDE-6381 URL: https://jira.jboss.org/browse/JBIDE-6381 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.M1 Reporter: Nick Boldt Assignee: Nick Boldt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5805) Highlight matching brackets in HQL Editor

by Krasimir Goutcev (JIRA)

Highlight matching brackets in HQL Editor ----------------------------------------- Key: JBIDE-5805 URL: https://jira.jboss.org/jira/browse/JBIDE-5805 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Reporter: Krasimir Goutcev Why don't we have Highlight matching brackets? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6559) NIGHTLY (6/29/2010): JBoss AS Plugin Has strange artifacts showing up in it

by Lincoln Baxter III (JIRA)

NIGHTLY (6/29/2010): JBoss AS Plugin Has strange artifacts showing up in it --------------------------------------------------------------------------- Key: JBIDE-6559 URL: https://jira.jboss.org/browse/JBIDE-6559 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Lincoln Baxter III Assignee: Rob Stryker Attachments: screenshot2.png Using eclipse 3.6 clean install and nightly jboss AS 6 install - attaching screenshot -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6332) "Path for project must have only one segment" when working with Project Archive

by Shu-Wei Tan (JIRA)

"Path for project must have only one segment" when working with Project Archive ------------------------------------------------------------------------------- Key: JBIDE-6332 URL: https://jira.jboss.org/browse/JBIDE-6332 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.1.0.GA Environment: XP SP3, JBoss 5.1.0 GA, Eclipse Galileo, Seam 2.2.0, JBoss Tools 3.1.0 Reporter: Shu-Wei Tan Assignee: Rob Stryker I have my workspace here: e:\test and I have a Seam project here: e:\test\sub\Proj e:\test\sub\Proj-ear e:\test\sub\Proj-ejb e:\test\sub\Proj-test When I create a Project Archive using the default values, everything I try to work with the archive I get this error: "Path for project must have only one segment" If my project lives directly in the test folder then it works without errors -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2010