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