December 2011 - jbosstools-issues

[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: (JBDS-1666) If a new namespace prefic is created in a .bpel file, the new namespace does not appear until the file is closed and re-opened - saving the file is not enough

by Len DiMaggio (JIRA)

If a new namespace prefic is created in a .bpel file, the new namespace does not appear until the file is closed and re-opened - saving the file is not enough -------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBDS-1666 URL: https://issues.jboss.org/browse/JBDS-1666 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: SOA Platform Environment: Version: 4.0.0.GA Build id: v20110216-1930-H239-GA Build date: 20110216-1930 Reporter: Len DiMaggio Attachments: Screenshot.png To recreate: Define a new namespace prefix in the source to a .bpel definition file - save the file. Note that if the prefix is deleted, it is removed from the prefix list when the .bpel file is saved. See attached screenshot. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
12
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-8577) Code completion for valid phases in <s:viewAction phase="|"/>

by Alexey Kazakov (JIRA)

Code completion for valid phases in <s:viewAction phase="|"/> ------------------------------------------------------------- Key: JBIDE-8577 URL: https://issues.jboss.org/browse/JBIDE-8577 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.M1 The valid phases are: APPLY_REQUEST_VALUES UPDATE_MODEL_VALUES PROCESS_VALIDATIONS INVOKE_APPLICATION See http://docs.jboss.org/seam/3/faces/latest/reference/en-US/html/components... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
14
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] (JBIDE-10312) Define a minimal target platform as opposed to the recommend one we have now for builds

by Max Rydahl Andersen (Created) (JIRA)

Define a minimal target platform as opposed to the recommend one we have now for builds --------------------------------------------------------------------------------------- Key: JBIDE-10312 URL: https://issues.jboss.org/browse/JBIDE-10312 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Reporter: Max Rydahl Andersen Assignee: Nick Boldt Priority: Critical Seeing JBIDE-10311 made me realize that we actually could catch these by having a *minimal* target platform to either build or test against. The problem here is that a plugin got a plugin dependency based on the target platform - but the target platform have the latest 3.7.1 version meaning those users running 3.7.0 would have problems installing it. If we had a minimal target platform (.target) we could actually install/verify these issues against it. Not necessarily every night - but like once a week run the build or install the updatesite against the minimal target platform would reveal these dependency issues. WDYT? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

6
25
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: (TOOLSDOC-227) Create update site for JBT eclipse documentation plug-ins

by Isaac Rooskov (JIRA)

Create update site for JBT eclipse documentation plug-ins --------------------------------------------------------- Key: TOOLSDOC-227 URL: https://issues.jboss.org/browse/TOOLSDOC-227 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Security Level: Public (Everyone can see) Components: General documentation issues Reporter: Isaac Rooskov Assignee: Isaac Rooskov Fix For: 3.3.0.Final Create an update site for Eclipse that contains the JBT documentation as Eclipse plug-ins -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-226) JBDS and JBT documentation as eclipse help

by Isaac Rooskov (JIRA)

JBDS and JBT documentation as eclipse help ------------------------------------------ Key: TOOLSDOC-226 URL: https://issues.jboss.org/browse/TOOLSDOC-226 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Security Level: Public (Everyone can see) Components: General documentation issues Reporter: Isaac Rooskov Assignee: Isaac Rooskov Fix For: 3.3.0.Final This bug tracks the progress of the overall initiative of having the JBT and JBDS documentation as eclipse plug-ins and help within the respective programs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
2
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 December 2011