[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-1654) Include BPEL editor update hooks in JBDS 4.1 if possible
by mark yarborough (JIRA)
Include BPEL editor update hooks in JBDS 4.1 if possible
--------------------------------------------------------
Key: JBDS-1654
URL: https://issues.jboss.org/browse/JBDS-1654
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: installer
Reporter: mark yarborough
Assignee: Brian Fitzpatrick
Fix For: 4.1.0.CR1
Include BPEL as part of installer in JBDS 4.1, if not already, so that update for customers is seamless in JBDS 4.1.1 (in case jbds411 goes out as update only with no new installer). This jira opened in response to Ken Johnson request at 10-May SOA PM meeting. His goal was to make update easier for customers without necessitating a full installer rebuild for jbds411 (at least, trying to avoid a full rebuild just for this item if can be avoided by putting right hooks into jbds41). Not sure if the wording is correct here, so will ping Ken to review/amend this jira as needed...
--
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] Closed: (JBDS-1579) Give the Designer's .log file a real name
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-1579?page=com.atlassian.jira.plugin.... ]
Pavol Srna closed JBDS-1579.
----------------------------
> 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: Barry LaFond
> Fix For: 4.1.0.CR1, 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
14 years, 10 months