January 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6018) Improve BPEL refactoring

by Robert (Bob) Brodt (JIRA)

Improve BPEL refactoring ------------------------ Key: JBIDE-6018 URL: https://jira.jboss.org/jira/browse/JBIDE-6018 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpm Reporter: Robert (Bob) Brodt Often times I find myself changing the names of variables, port types, partner links, etc. either in the Property sheet or directly on the editor canvas without thinking; what I really wanted to do was refactor the name change and have it propagate through to the WSDL or XSD where the element is defined. It would be simple enough to provide a change listener that prompts you with "Hey, I noticed you changed the name of this <thing> - did you intend to refactor instead?" possibly with a "Don't ask me again!" checkbox. The same functionality should be provided for the WSDL and XSD editor. This would go a long way to better integration within the tooling. -- 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, 2 months

4
16
0 / 0

[JBoss JIRA] Created: (JBIDE-8192) Could not instantiate dialect class HibernateException when Database in CC is expanded

by Jiri Peterka (JIRA)

Could not instantiate dialect class HibernateException when Database in CC is expanded -------------------------------------------------------------------------------------- Key: JBIDE-8192 URL: https://issues.jboss.org/browse/JBIDE-8192 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.CR1 Environment: JBDS 4.0.0.CR1 H88, Linux 64 Reporter: Jiri Peterka For example when creating dynamic web project and hibernate console (for precise steps see JBIDE-8189) when trying to expand HB CC -> Database for the FIRST TIME there is an HibernateException (see below). After "Rebuild Configuration" everything goes to normal. Exception is not always here but I saw it several times during few days. org.hibernate.HibernateException: Could not instantiate dialect class at org.hibernate.dialect.resolver.DialectFactory.constructDialect(DialectFactory.java:163) at org.hibernate.dialect.resolver.DialectFactory.buildDialect(DialectFactory.java:109) at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:146) at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2163) at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2155) at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:110) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:72) at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:107) at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:63) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.lang.ClassCastException: org.hibernate.dialect.HSQLDialect cannot be cast to org.hibernate.dialect.Dialect at org.hibernate.dialect.resolver.DialectFactory.constructDialect(DialectFactory.java:157) ... 12 more rebuild -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7996) Hibernate Configuration File (cfg.xml) Wizard: add possibility to import existing DTP connection settings

by Vitali Yemialyanchyk (JIRA)

Hibernate Configuration File (cfg.xml) Wizard: add possibility to import existing DTP connection settings --------------------------------------------------------------------------------------------------------- Key: JBIDE-7996 URL: https://issues.jboss.org/browse/JBIDE-7996 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.2.0.Beta2 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor https://issues.jboss.org/browse/JBIDE-1420 - initial idea of this enhancement. I see 2 ways to implement the feature: 1) add "Import DTP connection" button -> small dialog just with combobox - to select one existing DTP connection and Ok & Cancel buttons; 2) add checkbox "Import DTP connection" and combobox - to select one existing DTP connection - here to import DTP connection is necessary to check "Import DTP connection" and select connection from combobox, if the user change some config value - checkbox should become unchecked and empty valu in combobox be selected -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

7
15
0 / 0

[JBoss JIRA] Created: (JBIDE-4233) Support for fine grained pages.xml editing

by Max Rydahl Andersen (JIRA)

Support for fine grained pages.xml editing ------------------------------------------ Key: JBIDE-4233 URL: https://jira.jboss.org/jira/browse/JBIDE-4233 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Reporter: Max Rydahl Andersen Assignee: Alexey Kazakov Priority: Critical Fix For: 3.1.0.M3 Add support for fine grained page.xml (now we have support for coarse grained pages.xml) in the graphical pages.xml editor. I imagine an additonal tab or a toggle on the current tab that when enabled shows not just the pages that are in the single file, but also includes any info from other *.page.xml files. In the first iteration we can just make this a read only mode for any external files and then double click for editing (maybe that will be too cumbersome for the users ?) -- 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, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-146) Missing doc for Hibernate Ant Code Generation

by Jiri Peterka (JIRA)

Missing doc for Hibernate Ant Code Generation --------------------------------------------- Key: TOOLSDOC-146 URL: https://issues.jboss.org/browse/TOOLSDOC-146 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: Hibernate Tools Reference Guide Affects Versions: 3.2.0.Final Reporter: Jiri Peterka Hibernate documentation should contain information related to Ant Code Generation. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-4727) Support distribution defining "New Project" dependencies

by Pete Muir (JIRA)

Support distribution defining "New Project" dependencies -------------------------------------------------------- Key: JBIDE-4727 URL: https://jira.jboss.org/jira/browse/JBIDE-4727 Project: JBoss Tools Issue Type: Feature Request Components: Seam Reporter: Pete Muir Summary: Move the responsibility for defining a "New Seam Project"'s dependencies (libraries) from JBoss Tools to the Seam distribution. Use the Maven 2 POM format to define the dependencies. Use Maven POM profiles to support different use cases for Seam projects. Reason: Currently JBoss Tools defines the project dependencies which causes issues very time Seam changes either the dependency set of a new seam project, or the layout of libraries in the distribution. Use Maven 2 POM format as it is already a well defined and understood model. Use of Maven POM profiles can further increase the flexibility and support various use cases for Seam (for example, Seam with jBPM or Seam with ICEFaces). Details: JBoss Tools should be able to read these files from the seam-gen/ directory: war.pom.xml, ear.pom.xml, ejb-jar.ear.pom.xml, war.ear.pom.xml. The war.pom.xml defines the dependencies for a WAR project; the *ear.pom.xml define dependencies for the composite modules of an EAR project. The standard Maven scopes are used: compile to indicate compile/runtime dependencies of the project, test to indicate extra dependencies required in the test project. Maven profiles are used to define additional dependency sets for new seam projects, allowing the user to optionally add extra dependencies to his project. To make this extensible, and not require JBossTools to use a well-known list of profile ids, an xml namespace will be used to add additional metadata to the profile. This allows JBossTools to identify the possible profiles: <profile> <id>drools5</id> <jbt:profile> <jbt:description>Drools 5 support (Tech Preview)</jbt:description> </jbt:profile>  </profile> <profile> <id>ICEFaces</id> <jbt:profile> <jbt:description>ICEFaces</jbt:description> </jbt:profile>  </profile> JBossTools can recognize the jbt:profile element, and use the jbt:description element to as a descriptive element to present to the user: [x] ICEFaces [x] Drools 5 support (Tech Preview) displayed in the New Seam Project Wizard. We should allow for additional information to be placed in the POM and in the future beyond dependency information. For example, additional configuration files to include in the generated project, however this is not a critical feature. We should also consider allowing JBoss Tools to retrieve the POMs from a Maven repository. This would require a user to simply specify the version of Seam they require, and have JBoss Tools download the seam-gen artifact containing all templates and resources. -- 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, 2 months

5
9
0 / 0

[JBoss JIRA] Created: (JBIDE-4791) Properties list in Properties view disappears when the user clicks a tab in CSS Properties view

by Olga Chukhutsina (JIRA)

Properties list in Properties view disappears when the user clicks a tab in CSS Properties view ----------------------------------------------------------------------------------------------- Key: JBIDE-4791 URL: https://jira.jboss.org/jira/browse/JBIDE-4791 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M3 Environment: Ubuntu 8.10, JBossTools revision 17062 Reporter: Olga Chukhutsina Assignee: Sergey Dzmitrovich Properties list disappears from Properties view when the user clicks tabs in CSS Properties view. Steps: Choose some selector in CSS file>Text/Font tab is opened in CSS Properties view by default and the properties list in Properties view is displayed>choose another tab in CSS Properties view(e.g Background )>now properties list in Properties view is not shown any more -- 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, 3 months

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6085) Implement Validation of ESB config file

by Viacheslav Kabanovich (JIRA)

Implement Validation of ESB config file --------------------------------------- Key: JBIDE-6085 URL: https://jira.jboss.org/jira/browse/JBIDE-6085 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Affects Versions: 3.1.0.GA Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.2.next We have no validation implemented for consistency of objects, especially of actions that formally may be supplied by any set of properties while each action class requires a specific configuration. We should implement validation similar to that we have for beans in Seam and CDI. Documentation on ESB contains many rules on consistency of ESB objects not covered by simply complying with xml schema. -- 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, 3 months

4
20
0 / 0

[JBoss JIRA] Created: (JBIDE-4973) OpenOn for <xsi:schemaLocation "|" > in components.xml doesn't open a separate file with schema.

by Anton Klimkovich (JIRA)

OpenOn for <xsi:schemaLocation "|" > in components.xml doesn't open a separate file with schema. ------------------------------------------------------------------------------------------------ Key: JBIDE-4973 URL: https://jira.jboss.org/jira/browse/JBIDE-4973 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, Seam Affects Versions: 3.1.0.M4 Reporter: Anton Klimkovich Assignee: Alexey Kazakov Priority: Minor EXECUTE: Create Seam 2.0 or Seam 2.2 web project EXECUTE: Open components.xml EXECUTE: Make OpenOn on xsi:schemaLocation= "... http://jboss.com/products/seam/core-2.0.xsd for example FAILURE: File with schema isn't found EXECUTE: Make OpenOn on xsi:schemaLocation= "http://jboss.com/products/seam/core " ASSERT: Web Browser with JBoss.com page is opened; XML schema description should exists FAILURE: JBoss.com is opened with 404 - Page Not Found error on the page. -- 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, 3 months

5
12
0 / 0

[JBoss JIRA] Created: (JBIDE-4920) New Hibernate Console Configuration File (cfg.xml) file doesn't save state for Classpath tab in New Habirnate Console Configuration Step after '<Back' is pressed

by Denis Golovin (JIRA)

New Hibernate Console Configuration File (cfg.xml) file doesn't save state for Classpath tab in New Habirnate Console Configuration Step after '<Back' is pressed ----------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4920 URL: https://jira.jboss.org/jira/browse/JBIDE-4920 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M4 Reporter: Denis Golovin Priority: Trivial 1. EXECUTE: Create Java Project 2. EXECUTE: Select Java Project from step 1 and invoke New Hibernate Configuration file Wizard 3. EXECUTE: Go through all steps to New Hibernate Console Configuration step 4. EXECUTE: Select 'Classpath' tab, remove 'default classpath' entry 5. EXECUTE: Press '<Back' 6. EXECUTE: Press 'Next>' and select 'Classpath' tab 7. ASSERT: State is the same as it was after 4 step 4 above executed Now it restores default values -- 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, 3 months

5
14
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 January 2011