[JBoss JIRA] Created: (JBDS-1618) Teiid Designer Preview Feature doesn't work if you close and then re-open JBDS
by Debbie Steigner (JIRA)
Teiid Designer Preview Feature doesn't work if you close and then re-open JBDS
------------------------------------------------------------------------------
Key: JBDS-1618
URL: https://issues.jboss.org/browse/JBDS-1618
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: teiid
Affects Versions: 4.0.0.CR4
Reporter: Debbie Steigner
Assignee: Barry LaFond
In Teiid Designer after you first create your models you can run the preview feature to query a table, but once you close JBDS and re-open it the Preview no longer works on your existing tables. Gives the popup error "Error running preview see log for more details" click OK then another popup error "Validate the username and password in the default Teiid Server" ( this error is a red herring though, the username and password are correct) Looking in the server.log you'll see the error that the corresponding Preview.vdb doesn't exist. It doesn't exist because once you close JBDS this is deleted from the deploy directory, but it should be re-created every time you open JBDS and run the Preview and isn't.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-8555) Compilation failure for 3.3.indigo branch :: common
by Nick Boldt (JIRA)
Compilation failure for 3.3.indigo branch :: common
---------------------------------------------------
Key: JBIDE-8555
URL: https://issues.jboss.org/browse/JBIDE-8555
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: testing
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_3.3.indigo.continuou...
[ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-compiler-plugin:0.10.0:compile (default-compile) on project org.jboss.tools.ui.bot.ext: Compilation failure: Compilation failure:
[ERROR] /qa/hudson_ws/workspace/jbosstools-3.3_3.3.indigo.continuous/sources/tests/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/SWTBotExt.java (at line 132):[-1,-1]
[ERROR] public SWTBotScaleExt scale() {
[ERROR] ^^^^^^^^^^^^^^
[ERROR] The return type is incompatible with SWTBot.scale()
[ERROR]
[ERROR] /qa/hudson_ws/workspace/jbosstools-3.3_3.3.indigo.continuous/sources/tests/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/SWTBotExt.java (at line 136):[-1,-1]
[ERROR] public SWTBotScaleExt scale(int index) {
[ERROR] ^^^^^^^^^^^^^^
[ERROR] The return type is incompatible with SWTBot.scale(int)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBDS-1512) JBDS locks up when creating artifacts in a new Teiid metadata model
by Chuck Mosher (JIRA)
JBDS locks up when creating artifacts in a new Teiid metadata model
-------------------------------------------------------------------
Key: JBDS-1512
URL: https://issues.jboss.org/browse/JBDS-1512
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: SOA Platform
Affects Versions: 4.0.0.Beta2
Environment: RHEL 6 64-bit (CSB), T510 laptop with 3.7Gb memory
Reporter: Chuck Mosher
Created a new Teiid Model project (Demo), followed by a blank Teiid Metadata Model (testmodel). Then created two child base tables, Account and Schedule. Tried to move one of them and the program locked up. I had a 5.1 SOA-P/EDS server instance running, and had already verified connectivity to it via executing some previews from another model in my workspace. I was up against memory limits and there was a fair amount of swapping going on. In fact I thought at first that the system was just swapping so waited for it to complete but it never did. I had to do a hard shutdown of my laptop to get it back.
I have attached the .log file (JBDSfrozen-log.txt).
I have tried to reproduce this behavior and have been unsuccessful.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-8743) Cannot deploy a webapp referencing a utility project using the Deploy Only server
by Fred Bricon (JIRA)
Cannot deploy a webapp referencing a utility project using the Deploy Only server
---------------------------------------------------------------------------------
Key: JBIDE-8743
URL: https://issues.jboss.org/browse/JBIDE-8743
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Final
Environment: eclipse.buildId=M20110210-1200
java.version=1.6.0_24
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=fr_FR
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
JBossAS Tools 2.2.0.v20110216-1758-H51-GA
Reporter: Fred Bricon
Assignee: Rob Stryker
Attachments: test-web.war
While testing maven projects deployment on AS7 via the deploy only server, I was struck by the following error : "Full publish failed for module test-util"
{noformat}
java.io.IOException: Aucun fichier ou dossier de ce type
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.checkAndCreate(File.java:1704)
at java.io.File.createTempFile(File.java:1792)
at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.fullPublish(AbstractServerToolsPublisher.java:194)
at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.publishModule(AbstractServerToolsPublisher.java:105)
at org.jboss.ide.eclipse.as.core.publishers.AbstractPublishMethod.publishModule(AbstractPublishMethod.java:77)
at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:67)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1029)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1119)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:952)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:775)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2893)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:337)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{noformat}
IOException message says "No file or folder of this type".
I managed to reproduce the problem using simple, stock WTP projects. As a matter of fact, when a web project references a utility project, then the latter cannot be deployed.
Web project is deployed correctly to the deployment directory, so this is not a rights issue. If I remove the utility project from the equation, there's no error.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months