January 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1517) 2010 in the copyright header should be replaced by 2011

by Lukas Jungmann (JIRA)

2010 in the copyright header should be replaced by 2011 ------------------------------------------------------- Key: JBDS-1517 URL: https://issues.jboss.org/browse/JBDS-1517 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: ui/branding Affects Versions: 4.0.0.CR1 Reporter: Lukas Jungmann -open Help -> About JBDS => there is '(c) Copyright JBoss by Red Hat, contributors and others 2004 - 2010.' but it's year 2011 already hence it should be changed to ''(c) Copyright JBoss by Red Hat, contributors and others 2004 - 2011.' -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-8228) Default jBPM Server Deployer set to gpd-deployer/upload

by Jiri Peterka (JIRA)

Default jBPM Server Deployer set to gpd-deployer/upload ------------------------------------------------------- Key: JBIDE-8228 URL: https://issues.jboss.org/browse/JBIDE-8228 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jbpm Affects Versions: 3.2.0.CR1 Environment: JBT 3.2.CR1, Linux 64 Reporter: Jiri Peterka Currently default server deployer (jBPM Process -> Deployment Page -> Server Deployer) is set to /jbpm-console/upload. For recent JBoss runtimes (SOA-P specifically) default jBPM deployer is "gpd-deployer/upload". If there are no other reasons for keeping the old value, I suggest to change it to "gpd-deployer/upload". -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8240) RSE Server Shutdown Does Not Work with AS6

by Dominik Pospisil (JIRA)

RSE Server Shutdown Does Not Work with AS6 ------------------------------------------ Key: JBIDE-8240 URL: https://issues.jboss.org/browse/JBIDE-8240 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.CR1 Reporter: Dominik Pospisil Assignee: Rob Stryker RSE Server Shutdown Does Not Work with AS6. The shutdown command constructed by JBT is: org.jboss.Shutdown -S -s JAWA23.MW.LAB.ENG.BRQ.REDHAT.COM -u admin -p admin However, for AS6 the -s $HOSTNAME option no longer works and it needs to be changed to -o $HOSTNAME. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
17
0 / 0

[JBoss JIRA] Created: (JBIDE-8235) Gode Generation wizard: the launch doesn't appear in the menu like previously executed.

by Dmitry Geraskov (JIRA)

Gode Generation wizard: the launch doesn't appear in the menu like previously executed. --------------------------------------------------------------------------------------- Key: JBIDE-8235 URL: https://issues.jboss.org/browse/JBIDE-8235 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.CR1 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.2.x Test case: 1. Create hibernate code generation configuration with valid parameters 2. Run it 3. Go to Run->Hibernate Code Generation... FAILURE: the executed configuration didn't appear in the list -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-8230) Gode Generation wizard: Non convention package name shown as error

by Dmitry Geraskov (JIRA)

Gode Generation wizard: Non convention package name shown as error ------------------------------------------------------------------ Key: JBIDE-8230 URL: https://issues.jboss.org/browse/JBIDE-8230 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.CR1 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.2.x Test case: 1. run Hibernate code generation configuration wizard and fill it with valid paramaters 2. Check that Run button enabled 3. On main page change Package name to "XXX" FAILURE: Error instead of the warning is shown, Run button is disabled -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8219) Try to explore CC without DB connection - result "java.lang.UnsupportedOperationException: The user must supply a JDBC connection" - "Database" node has no child node with error message

by Vitali Yemialyanchyk (JIRA)

Try to explore CC without DB connection - result "java.lang.UnsupportedOperationException: The user must supply a JDBC connection" - "Database" node has no child node with error message ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8219 URL: https://issues.jboss.org/browse/JBIDE-8219 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.CR1 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Fix For: 3.2.0.CR2 (tentative) try to use CC with "Hibernate configured connection" hibernate.cfg.xml: >> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate Configuration DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd"> <hibernate-configuration> <session-factory> <property name="hibernate.dialect">org.hibernate.dialect.HSQLDialect</property></session-factory> </hibernate-configuration> >> try to expand Database node - get exception: >> java.lang.UnsupportedOperationException: The user must supply a JDBC connection at org.hibernate.connection.UserSuppliedConnectionProvider.getConnection(UserSuppliedConnectionProvider.java:54) at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.getConnection(AbstractMetaDataDialect.java:121) at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.getMetaData(AbstractMetaDataDialect.java:60) at org.hibernate.cfg.reveng.dialect.AbstractMetaDataDialect.caseForSearch(AbstractMetaDataDialect.java:163) at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:22) at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476) at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74) at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:117) 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:106) 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) >> and "Database" node has no child node with error message in case of some error every CC node ("Configuration", "Session Factory", "Database") should display child node with error message -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBDS-1505) allow users to submit problem reports from JBDS

by Andrew Hecox (JIRA)

allow users to submit problem reports from JBDS ----------------------------------------------- Key: JBDS-1505 URL: https://issues.jboss.org/browse/JBDS-1505 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: integration Affects Versions: LATER Environment: All Reporter: Andrew Hecox user-story: as a JBoss customer, I can create a report a problem from JBDS and instantly get suggestions back so that I can easily get help solving the problem I'm working on in my editor notes: I think something which allowed a user to create a problem report, as well as send any applicable files, with us sending back instant results (and prior to case creation) would be a good value add to JBDS. We don't yet have a public API for this, but something would be added to our subscriber API: https://access.redhat.com/knowledge/docs/Red_Hat_Customer_Portal/ probably RESTfully modeled in it's own root level domain, eg, /problem or /problem_report, /report, etc... with a synchronous response including suggested KBase articles, community forums, whitepapers, etc... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBDS-1514) JBDS does not completely clean up Teiid PREVIEW VDBs and DataSources

by Chuck Mosher (JIRA)

JBDS does not completely clean up Teiid PREVIEW VDBs and DataSources -------------------------------------------------------------------- Key: JBDS-1514 URL: https://issues.jboss.org/browse/JBDS-1514 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: teiid Affects Versions: 4.0.0.Beta2 Environment: RHEL 6 (CSB) running on a T510 laptop, 3.7Gb of memory Reporter: Chuck Mosher Assignee: Barry LaFond When exiting JBDS after using the Teiid Designer perspective to conduct previews of models, those models are not all removed from the server after JBDS is closing. This is with a normal close. An informational window comes up saying "Teiid Server cleanup (30 jobs running)", and 30 Previews is indeed the right number to clean up. However, the clean-up task exits without removing all of them. See attached screenshot. Also, the Preview datasources never seem to be cleaned up, and I would expect that they should be (see the second screenshot). I am flagging this as major since there could be a resultant massive accumulation of Previews in the server, especially since many users won't know to look for them to delete them by hand. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
12
0 / 0

[JBoss JIRA] Created: (JBIDE-8252) JBoss Maven Configurators don't check transitive dependencies

by Snjezana Peco (JIRA)

JBoss Maven Configurators don't check transitive dependencies ------------------------------------------------------------- Key: JBIDE-8252 URL: https://issues.jboss.org/browse/JBIDE-8252 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.2.0.CR1 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.3.x If you create a project based on the org.jboss.weld.archetypes:jboss-javaee6-webapp:1.0.1.Beta2 archetype, you will see that the CDI and JSF facets aren't added. The project includes CDI and JSF libraries as transitive dependencies. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8269) Add project examples from Weld 1.1

by Alexey Kazakov (JIRA)

Add project examples from Weld 1.1 ---------------------------------- Key: JBIDE-8269 URL: https://issues.jboss.org/browse/JBIDE-8269 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299), project-examples Reporter: Alexey Kazakov Assignee: Alexey Kazakov -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
3
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