February 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-4297) Error while performing background reading of database schema

by Krasimir Goutcev (JIRA)

Error while performing background reading of database schema ------------------------------------------------------------ Key: JBIDE-4297 URL: https://jira.jboss.org/jira/browse/JBIDE-4297 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Environment: JBT nightly build 3.1.0.Alpha1/200905091201 eclipse.buildId=N20090426-1232 java.version=1.5.0_15 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=bg_BG Command-line arguments: -os win32 -ws win32 -arch x86 -clean Reporter: Krasimir Goutcev 1.Open some ....hbm.xml file 2.Click on table="|" or <column name="|".../> and try CA org.hibernate.cfg.JDBCBinderException: Duplicate class name 'AllFileGroups' generated for 'org.hibernate.mapping.Table(SYS._ALL_FILE_GROUPS)'. Same name where generated for 'org.hibernate.mapping.Table(SYS._ALL_FILE_GROUPS)' at org.hibernate.cfg.JDBCBinder.createPersistentClasses(JDBCBinder.java:172) at org.hibernate.cfg.JDBCBinder.readFromDatabase(JDBCBinder.java:95) at org.hibernate.cfg.JDBCMetaDataConfiguration.readFromJDBC(JDBCMetaDataConfiguration.java:42) at org.hibernate.eclipse.nature.HibernateNature$ReadDatabaseMetaData$1.execute(HibernateNature.java:158) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:64) at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:95) at org.hibernate.eclipse.nature.HibernateNature$ReadDatabaseMetaData.run(HibernateNature.java:156) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- 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

15 years

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-7562) "Use generation in external process" is not workable in case "Schema Documentation (.html)" use for Seam 2.2 Booking example

by Vitali Yemialyanchyk (JIRA)

"Use generation in external process" is not workable in case "Schema Documentation (.html)" use for Seam 2.2 Booking example ---------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-7562 URL: https://jira.jboss.org/browse/JBIDE-7562 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Hibernate Affects Versions: 3.2.0.Beta2 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Fix For: 3.2.0.CR1 1) new Project example -> Seam 2.2 Booking example -> http://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/seam-examples/... 2) add hibernate-tools-core.jar into booking22-ejb libs; 3) create Hibernate Code gen configuration with "Schema Documentation (.html)" exporter selected based on "booking22-ejb" Hibernate Console Configuration; 4) in case "Use generation in external process" checked Hibernate Code gen does not work to find what is an error: 5) export Hibernate Code gen configuration to ant script; 6) run this ant script with -verbose argument - result stacktrace: >>> Apache Ant version 1.7.1 compiled on June 27 2008 Buildfile: C:\Users\vitali.ELTEGRA\workspace8\booking22\src\zzz.xml parsing buildfile C:\Users\vitali.ELTEGRA\workspace8\booking22\src\zzz.xml with URI = file:/C:/Users/vitali.ELTEGRA/workspace8/booking22/src/zzz.xml Project base dir set to: C:\Users\vitali.ELTEGRA\workspace8\booking22\src [antlib:org.apache.tools.ant] Could not load definitions from resource org/apache/tools/ant/antlib.xml. It could not be found. Build sequence for target(s) `hibernateAntCodeGeneration' is [hibernateAntCodeGeneration] Complete build sequence is [hibernateAntCodeGeneration, ] hibernateAntCodeGeneration: [hibernatetool] Executing Hibernate Tool with a JPA Configuration [hibernatetool] 1. task: hbm2doc (Generates html schema documentation) [hibernatetool] SLF4J: Class path contains multiple SLF4J bindings. [hibernatetool] SLF4J: Found binding in [jar:file:/D:/Bin/jbdevstudio_beta1/jboss-eap/jboss-as/client/slf4j-jboss-logging.jar!/org/slf4j/impl/StaticLoggerBinder.class] [hibernatetool] SLF4J: Found binding in [jar:file:/D:/Bin/jbdevstudio_beta1/jboss-eap/jboss-as/client/slf4j-jboss-logging.jar!/org/slf4j/impl/StaticLoggerBinder.class] [hibernatetool] SLF4J: Found binding in [jar:file:/D:/Bin/jbdevstudio_beta1/jboss-eap/jboss-as/common/lib/slf4j-jboss-logging.jar!/org/slf4j/impl/StaticLoggerBinder.class] [hibernatetool] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. [hibernatetool] An exception occurred while running exporter #2:hbm2doc (Generates html schema documentation) [hibernatetool] To get the full stack trace run ant with -verbose [hibernatetool] org.hibernate.HibernateException: Could not instantiate TransactionManagerLookup '' BUILD FAILED C:\Users\vitali.ELTEGRA\workspace8\booking22\src\zzz.xml:285: org.hibernate.HibernateException: Could not instantiate TransactionManagerLookup '' at org.hibernate.tool.ant.HibernateToolTask.reportException(HibernateToolTask.java:226) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:189) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) 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.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.eclipse.ant.internal.launching.remote.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32) at org.apache.tools.ant.Project.executeTargets(Project.java:1189) at org.eclipse.ant.internal.launching.remote.InternalAntRunner.run(InternalAntRunner.java:423) at org.eclipse.ant.internal.launching.remote.InternalAntRunner.main(InternalAntRunner.java:137) Caused by: org.hibernate.HibernateException: Could not instantiate TransactionManagerLookup '' at org.hibernate.transaction.TransactionManagerLookupFactory.getTransactionManagerLookup(TransactionManagerLookupFactory.java:93) at org.hibernate.cfg.SettingsFactory.createTransactionManagerLookup(SettingsFactory.java:439) at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:163) at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2119) at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2111) at org.hibernate.tool.hbm2x.doc.DocHelper.<init>(DocHelper.java:135) at org.hibernate.tool.hbm2x.DocExporter.setupContext(DocExporter.java:277) at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:94) at org.hibernate.tool.ant.ExporterTask.execute(ExporterTask.java:40) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:186) ... 16 more --- Nested Exception --- org.hibernate.HibernateException: Could not instantiate TransactionManagerLookup '' at org.hibernate.transaction.TransactionManagerLookupFactory.getTransactionManagerLookup(TransactionManagerLookupFactory.java:93) at org.hibernate.cfg.SettingsFactory.createTransactionManagerLookup(SettingsFactory.java:439) at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:163) at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2119) at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2111) at org.hibernate.tool.hbm2x.doc.DocHelper.<init>(DocHelper.java:135) at org.hibernate.tool.hbm2x.DocExporter.setupContext(DocExporter.java:277) at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:94) at org.hibernate.tool.ant.ExporterTask.execute(ExporterTask.java:40) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:186) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) 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.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.eclipse.ant.internal.launching.remote.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32) at org.apache.tools.ant.Project.executeTargets(Project.java:1189) at org.eclipse.ant.internal.launching.remote.InternalAntRunner.run(InternalAntRunner.java:423) at org.eclipse.ant.internal.launching.remote.InternalAntRunner.main(InternalAntRunner.java:137) Total time: 5 seconds >>> -- 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

15 years

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-1654) Generate entities for JPA can fail when explicit listed classes in persistence.xml

by Max Andersen (JIRA)

Generate entities for JPA can fail when explicit listed classes in persistence.xml ---------------------------------------------------------------------------------- Key: JBIDE-1654 URL: http://jira.jboss.com/jira/browse/JBIDE-1654 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: Max Andersen Fix For: 2.1 e.g. if the listed class does not exist JPA will fail. Consider using PersistenceXmlLoader.deploy(URL url, Map overrides, EntityResolver resolver, PersistenceUnitTransactionType defaultTransactionType) to build a "safer" persistence unit. -- 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

15 years

5
14
0 / 0

[JBoss JIRA] Created: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.

by Dmitry Geraskov (JIRA)

Provide a way to filter out elements which will be generated by exporter. ------------------------------------------------------------------------- Key: JBIDE-4269 URL: https://jira.jboss.org/jira/browse/JBIDE-4269 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.1.0.M1 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.1.0.M1 Now exporter uses Configuration object to get for example pojo's for generation. After this it calls generation for each of them. We need to add some filter for this. First place for such injection is ArtifactCollector as developer can easily specify subclass of this class and set it to exporter. Also TemplateProducer which used for files generating always gets ArtifactCollector object in constructor from exporter and has access to it. I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector class and call it when necessary in template producer. Method 'filter' by default will not filter out anything. Non default realizations should use context map to get any objects which is passed to template producer. Second variant is to add Filter field to Generic exporter and call for filtering in GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()). I prefer first way. -- 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

15 years

3
17
0 / 0

[JBoss JIRA] Created: (JBIDE-4268) Provide a way to merge files generated by exporters.

by Dmitry Geraskov (JIRA)

Provide a way to merge files generated by exporters. ----------------------------------------------------- Key: JBIDE-4268 URL: https://jira.jboss.org/jira/browse/JBIDE-4268 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.1.0.M1 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.1.0.M1 Now exporter replaces previous file version. We need to call merging when file which will be generated already exists. The best place for such injection is ArtifactCollector as developer can easily specify subclass of this class and set it to exporter. We need only to provide such API. I' going to add method merge(...) to ArtifactCollector class and call it when necessary in template producer. -- 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

15 years

3
18
0 / 0

[JBoss JIRA] Created: (JBIDE-8484) Create unit tests for o.j.t.common.projecttemplates

by Alexey Kazakov (JIRA)

Create unit tests for o.j.t.common.projecttemplates --------------------------------------------------- Key: JBIDE-8484 URL: https://issues.jboss.org/browse/JBIDE-8484 Project: Tools (JBoss Tools) Issue Type: Task Components: common Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M1 We don't have any unit tests for project templates at all. Let's create them. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8068) BPEL Editor has problems dealing with abstract processes

by Robert (Bob) Brodt (JIRA)

BPEL Editor has problems dealing with abstract processes -------------------------------------------------------- Key: JBIDE-8068 URL: https://issues.jboss.org/browse/JBIDE-8068 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.Beta2 Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Priority: Minor Fix For: 3.2.x For abstract processes, the namespace is "http://docs.oasis-open.org/wsbpel/2.0/process/abstract" but much of the editor code simply assumes that the namespace is always "http://docs.oasis-open.org/wsbpel/2.0/process/executable". This causes all kinds of problems when doing lookup of namespace prefixes to identify BEPL "built-in" features (e.g. fault names). This is also the reason why the BPELContentDescriber does not recognize an abstract process as a BPEL file. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
4
0 / 0

[JBoss JIRA] Updated: (JBIDE-8446) <rich:validator /> validation message don´t work in Eclipse/JBoss Tools browser

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8446?page=com.atlassian.jira.plugin... ] Alexey Kazakov updated JBIDE-8446: ---------------------------------- Component/s: UpStream (was: Visual Page Editor core) Looks like an issue of Eclipse/WTP. > <rich:validator /> validation message don´t work in Eclipse/JBoss Tools browser > ------------------------------------------------------------------------------- > > Key: JBIDE-8446 > URL: https://issues.jboss.org/browse/JBIDE-8446 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: UpStream > Affects Versions: 3.2.0.CR1 > Environment: Eclipse 3.6 SR1/JBoss Tools 3.2 CR1 > Reporter: Flávio Henrique > Priority: Minor > > <rich:validator /> validation message don´t work in Eclipse/JBoss Tools browser. Works fine in IE, FireFox and Google Chrome. > Exeample: > <?xml version="1.0" encoding="UTF-8" ?> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > <h:head> > <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> > <title>My Richfaces 4.0 rich:validation test</title> > </h:head> > <h:body> > <h:form> > <rich:panel> > <h:inputText id="idInput1"> > <f:validateLength maximum="5"/> > <rich:validator /> > </h:inputText> > <rich:message for="idInput1"/> > <a4j:commandButton value="Submit"/> > </rich:panel> > </h:form> > </h:body> > </html> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-8409) BPEL Process editor is not associated with *.bpel files

by Denis Golovin (JIRA)

BPEL Process editor is not associated with *.bpel files ------------------------------------------------------- Key: JBIDE-8409 URL: https://issues.jboss.org/browse/JBIDE-8409 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Attachments: screenshot112.png, screenshot113.png .bpel files in resources tree look like text files. There is no bpel icon associated with file. !screenshot112.png! Editor opened using workaround has no icon as well. !screenshot113.png! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
8
0 / 0

[JBoss JIRA] Commented: (JBIDE-8446) <rich:validator /> validation message don´t work in Eclipse/JBoss Tools browser

by Flávio Henrique (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8446?page=com.atlassian.jira.plugin... ] Flávio Henrique commented on JBIDE-8446: ---------------------------------------- The final release of JBoss Tools 3.2 also has this problem. > <rich:validator /> validation message don´t work in Eclipse/JBoss Tools browser > ------------------------------------------------------------------------------- > > Key: JBIDE-8446 > URL: https://issues.jboss.org/browse/JBIDE-8446 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor core > Affects Versions: 3.2.0.CR1 > Environment: Eclipse 3.6 SR1/JBoss Tools 3.2 CR1 > Reporter: Flávio Henrique > Priority: Minor > > <rich:validator /> validation message don´t work in Eclipse/JBoss Tools browser. Works fine in IE, FireFox and Google Chrome. > Exeample: > <?xml version="1.0" encoding="UTF-8" ?> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich"> > <h:head> > <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> > <title>My Richfaces 4.0 rich:validation test</title> > </h:head> > <h:body> > <h:form> > <rich:panel> > <h:inputText id="idInput1"> > <f:validateLength maximum="5"/> > <rich:validator /> > </h:inputText> > <rich:message for="idInput1"/> > <a4j:commandButton value="Submit"/> > </rich:panel> > </h:form> > </h:body> > </html> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2011