[JBoss JIRA] Updated: (JBDS-1579) Give the Designer's .log file a real name
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBDS-1579?page=com.atlassian.jira.plugin.... ]
Brian Fitzpatrick updated JBDS-1579:
------------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Fix Version/s: 4.0.1
LATER
> Give the Designer's .log file a real name
> -----------------------------------------
>
> Key: JBDS-1579
> URL: https://issues.jboss.org/browse/JBDS-1579
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Environment: All
> Reporter: Paul Nittel
> Assignee: Dan Florian
> Fix For: 4.0.1, LATER
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> (I called this a Feature since it's been this way for years and we've not recorded it as a defect before. However, Bernd Groh pointed out this issue, so I'm recording it on his behalf.)
> The MetaMatrix and Teiid Designers have always created a .log file in the .metadata directory. The name is not easy to find and is a nuisance to use (for example, when attaching the log file to an email message).
> Please incorporate a "real" name, like "designer.log".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Moved: (JBDS-1579) Give the Designer's .log file a real name
by Paul Nittel (JIRA)
[ https://issues.jboss.org/browse/JBDS-1579?page=com.atlassian.jira.plugin.... ]
Paul Nittel moved TEIIDDES-428 to JBDS-1579:
--------------------------------------------
Project: Developer Studio (JBoss Developer Studio) (was: Teiid Designer)
Key: JBDS-1579 (was: TEIIDDES-428)
Affects Version/s: (was: 7.0)
Component/s: (was: Housekeeping)
Fix Version/s: (was: 7.4)
> Give the Designer's .log file a real name
> -----------------------------------------
>
> Key: JBDS-1579
> URL: https://issues.jboss.org/browse/JBDS-1579
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Environment: All
> Reporter: Paul Nittel
> Assignee: Dan Florian
>
> (I called this a Feature since it's been this way for years and we've not recorded it as a defect before. However, Bernd Groh pointed out this issue, so I'm recording it on his behalf.)
> The MetaMatrix and Teiid Designers have always created a .log file in the .metadata directory. The name is not easy to find and is a nuisance to use (for example, when attaching the log file to an email message).
> Please incorporate a "real" name, like "designer.log".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JBIDE-6198) "J2EE 5.0 libraries (JBoss Tools)" contains only subset of API
by henk de boer (JIRA)
"J2EE 5.0 libraries (JBoss Tools)" contains only subset of API
--------------------------------------------------------------
Key: JBIDE-6198
URL: https://jira.jboss.org/jira/browse/JBIDE-6198
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.GA
Environment: Eclipse 3.5.2 / JBoss AS 5.1 / Mac OS X 10.5.7 / Ubuntu 9.10 (JDK 6u18)
Reporter: henk de boer
Assignee: Rob Stryker
JBoss Tools 3.1.0.GA adds a library to Eclipse called "J2EE 5.0 libraries (JBoss Tools)". The name of this library suggests it's the full Java EE 5 API, however upon inspection it appears to be a subset:
javax.annotation
javax.ejb
javax.enterprise.deploy
javax.jms
javax.persistence
javax.resource
javax.security.jacc
javax.servlet
javax.transaction
javax.xml
Among others, javax.faces and javax.mail are missing.
Additionally, the name of the library is not consistent. In project -> properties -> Java Build Path -> Add Library... it's called "JEE 5.0 libraries", but after adding it to a project it's referred to as "J2EE 5.0 libraries (JBoss Tools)". I think "Java EE 5 libraries" would be the best name as both "JEE 5.0" and "J2EE 5.0" are not official terms.
--
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
15 years
[JBoss JIRA] Created: (JBIDE-8438) Publishing / Use of RSE servers lead to thread overload, connection limit, failure of tools
by Rob Stryker (JIRA)
Publishing / Use of RSE servers lead to thread overload, connection limit, failure of tools
-------------------------------------------------------------------------------------------
Key: JBIDE-8438
URL: https://issues.jboss.org/browse/JBIDE-8438
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: deltacloud, JBossAS
Affects Versions: 3.2.0.CR1
Reporter: Rob Stryker
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.2.0.Final
Every launch to twiddle (which is typically twice during every publish) or *ANY* remote shell command in the current tools, never cleans up its host shell connections.
According to API this is platform dependent. IHostShell may or may not close its connection after executing a command. There is no guarantee, but on some platforms it may not close them. It seems in linux (and possibly other platforms) the host shell is NOT closed.
Eventually, there are too many connections to the remote system, and further attempts to connect OR transfer files become failures, leading to a complete paralysis of the tooling.
Workaround is to go to the Remote System view and disconnect and reconnect to your remote system, however, 4 publishes later, the same action will be needed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JBIDE-8380) OrmLabelProvider -> updateColumnSqlType -> column.getSqlType - swallow MappingException for some tests
by Vitali Yemialyanchyk (JIRA)
OrmLabelProvider -> updateColumnSqlType -> column.getSqlType - swallow MappingException for some tests
------------------------------------------------------------------------------------------------------
Key: JBIDE-8380
URL: https://issues.jboss.org/browse/JBIDE-8380
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Hibernate
Affects Versions: 3.3.x
Reporter: Vitali Yemialyanchyk
Assignee: Vitali Yemialyanchyk
Priority: Minor
Fix For: 3.3.x
column.getSqlType in end result call SimpleValue -> getType() -> throw MappingException with message "Could not determine type for...";
in OrmLabelProvider -> updateColumnSqlType we swallow the exception - right resolution - we should not swallow the exception - is necessary to print it in Error Log, is necessary to getSqlType in ConsoleConfiguration execution context - so we get correct expected result and avoid the exception.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years