[JBoss JIRA] Created: (JBDS-983) Console not showing up when staritng a EAP/SOA-P Instance
by Jim Tyrrell (JIRA)
Console not showing up when staritng a EAP/SOA-P Instance
---------------------------------------------------------
Key: JBDS-983
URL: https://jira.jboss.org/jira/browse/JBDS-983
Project: JBoss Developer Studio
Issue Type: Feature Request
Affects Versions: 3.0.0.M4
Reporter: Jim Tyrrell
For some reason starting a SOA-P instance by right clicking in the server view does not start/open the console for the output of the server as it is starting. For EAP and Seam projects this does not seem to be the case as often, but I think I have seen it. The current JBDS 3.0 M4 release does seem to not show the console unless I open the console via the Window -> Show View -> General -> Console and then I have to click an icon to enable the "Java Stack Trace Console". Once I have setup the console once as just noted even if I close it it will open as I expect. If I close JBDS and make sure that the console was not left open, I get the same behaviour when I try to right click on the SOA-P instance.
--
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
1 day
[JBoss JIRA] Created: (JBIDE-9535) JPA: take into account hibernate.default_schema/hibernate.default_catalog when validate Table
by Dmitry Geraskov (JIRA)
JPA: take into account hibernate.default_schema/hibernate.default_catalog when validate Table
---------------------------------------------------------------------------------------------
Key: JBIDE-9535
URL: https://issues.jboss.org/browse/JBIDE-9535
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.3.0.M2
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: LATER
JPA validator doen't take into account hibernate.default_schema/hibernate.default_catalog when validates Table existance.
Test case:
1. Create table mytable in schema test
2. in Persistence.xml add hibernate.default_schema=test
3. cerate Entity Mytable without @Table(schema="test")
4. Make a DTP connection to the databse
OBSERVE: wrong error appiared (Table "Mytable" cannot be sesolved)
add @Table(schema="test") - error disappeared
Probably the properties should be processed like the project properties (Oveddide default schema/catalog)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years