[JBoss JIRA] (JBDS-1934) (Teiid) Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-1934?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-1934:
-------------------------------
Summary: (Teiid) Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio (was: Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio)
> (Teiid) Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio
> ------------------------------------------------------------------------------------------------------
>
> Key: JBDS-1934
> URL: https://issues.jboss.org/browse/JBDS-1934
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform , teiid
> Affects Versions: 5.x
> Environment: JBoss Developer Studio 4.0
> JBoss Developer Studio 4.1
> Reporter: Johnathon Lee
> Assignee: Barry LaFond
> Fix For: 5.0.0.CR1-SOA
>
>
> /*+ cache */
> CREATE VIRTUAL PROCEDURE
> SELECT 'winning';
> BEGIN
> END
> The cache hint is saved w/the Command Object even though it is not reflected in the display of the text after validation.
> com.metamatrix.query.internal.ui.sqleditor.component.QueryDisplayComponent:313 & 314
> The Command object on these lines has a member cacheHint, holding the reference to the cacheHint, this is ignored when the sqlText is set with the line:
> this.sqlText = sqlDisplayNode.toDisplayString();
--
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, 10 months
[JBoss JIRA] (JBDS-1934) Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-1934?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-1934:
-------------------------------
Fix Version/s: 5.0.0.CR1-SOA
(was: 5.0.0.CR1)
Component/s: SOA Tooling / Platform
> Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio
> ----------------------------------------------------------------------------------------------
>
> Key: JBDS-1934
> URL: https://issues.jboss.org/browse/JBDS-1934
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform , teiid
> Affects Versions: 5.x
> Environment: JBoss Developer Studio 4.0
> JBoss Developer Studio 4.1
> Reporter: Johnathon Lee
> Assignee: Barry LaFond
> Fix For: 5.0.0.CR1-SOA
>
>
> /*+ cache */
> CREATE VIRTUAL PROCEDURE
> SELECT 'winning';
> BEGIN
> END
> The cache hint is saved w/the Command Object even though it is not reflected in the display of the text after validation.
> com.metamatrix.query.internal.ui.sqleditor.component.QueryDisplayComponent:313 & 314
> The Command object on these lines has a member cacheHint, holding the reference to the cacheHint, this is ignored when the sqlText is set with the line:
> this.sqlText = sqlDisplayNode.toDisplayString();
--
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, 10 months
[JBoss JIRA] (JBIDE-12000) Random "Unable to publish to ther server" error
by George Lindholm (JIRA)
George Lindholm created JBIDE-12000:
---------------------------------------
Summary: Random "Unable to publish to ther server" error
Key: JBIDE-12000
URL: https://issues.jboss.org/browse/JBIDE-12000
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.x
Environment: JBoss 6.1.1 server
Reporter: George Lindholm
Assignee: Rob Stryker
Priority: Minor
What steps will reproduce the problem?
1. Unknown, randomnly happens
2.
3.
-- Error Details --
Date: Thu May 24 13:35:41 PDT 2012
Message: Could not publish to the server.
Severity: Error
Product: Eclipse 1.4.2.20120131-1457 (org.eclipse.epp.package.jee.product)
Plugin: org.eclipse.wst.server.core
Session Data:
eclipse.buildId=M20120208-0800
java.version=1.7.0_04
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_CA
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product -data e:\java\workspace
Exception Stack Trace:
java.lang.NullPointerException
at org.jboss.ide.eclipse.as.core.server.internal.ExtendedServerPropertiesAdapterFactory.getExtendedProperties(ExtendedServerPropertiesAdapterFactory.java:53)
at org.jboss.ide.eclipse.as.core.server.internal.ExtendedServerPropertiesAdapterFactory.getAdapter(ExtendedServerPropertiesAdapterFactory.java:42)
at org.jboss.ide.eclipse.as.core.server.internal.ExtendedServerPropertiesAdapterFactory.getJBossExtendedProperties(ExtendedServerPropertiesAdapterFactory.java:32)
at org.jboss.ide.eclipse.as.jmx.integration.JBoss3To6ConnectionProvider.belongsHere(JBoss3To6ConnectionProvider.java:37)
at org.jboss.ide.eclipse.as.jmx.integration.AbstractJBossJMXConnectionProvider.getConnections(AbstractJBossJMXConnectionProvider.java:106)
at org.jboss.ide.eclipse.as.jmx.integration.AbstractJBossJMXConnectionProvider.findConnection(AbstractJBossJMXConnectionProvider.java:94)
at org.jboss.ide.eclipse.as.jmx.integration.JBossJMXConnectionProviderModel.getConnection(JBossJMXConnectionProviderModel.java:59)
at org.jboss.ide.eclipse.as.jmx.integration.JBossJMXConnectionProviderModel.run(JBossJMXConnectionProviderModel.java:76)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerJMXRunner.run(JBossServerJMXRunner.java:33)
at org.jboss.ide.eclipse.as.core.server.internal.LocalJBossBehaviorDelegate.publishStart(LocalJBossBehaviorDelegate.java:211)
at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.publishStart(DelegatingServerBehavior.java:139)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:927)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
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, 10 months
[JBoss JIRA] (JBIDE-11308) server adapter adds .dodeploy before Clean/publish has finished
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-11308:
-------------------------------------------
Summary: server adapter adds .dodeploy before Clean/publish has finished
Key: JBIDE-11308
URL: https://issues.jboss.org/browse/JBIDE-11308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.Beta2
EXECUTE: import decent sized project, i.e. GWT project from central and follo the readme regarding tooling
EXECUTE: after Run As have been done, right click server and press Clean...
ASSERT: clean is done and publish goes on and then in the end .dodeploy file occurrs
What actually seem to happen is deploymen is removed, dir added, then .dodeploy and *then* file copying occurs - causing the scanner to pickup partially deployed project.
--
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, 10 months
[JBoss JIRA] Created: (JBIDE-9356) NLS.bind vs MessageFormat.format
by Rob Stryker (JIRA)
NLS.bind vs MessageFormat.format
--------------------------------
Key: JBIDE-9356
URL: https://issues.jboss.org/browse/JBIDE-9356
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Cleanup
Affects Versions: 3.3.0.M3
Reporter: Rob Stryker
Assignee: Max Rydahl Andersen
Fix For: 3.3.0.Final
A substantial number of classes use NLS.bind(Messages.SomeString, name) to bind message strings. Another subset of the classes use MessageFormat.format(etc).
I believe NLS.bind() is the correct solution which works properly with eclipse osgi and all that jazz. Should this be standardized? Is it confusing to be using two interchangable APIs?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months