January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-180) Create SY bot test for testing implementation properties

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-180?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-180. ----------------------------------- > Create SY bot test for testing implementation properties > -------------------------------------------------------- > > Key: JBTIS-180 > URL: https://issues.jboss.org/browse/JBTIS-180 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.1.3 > Reporter: Andrej Podhradsky > Assignee: Tomáš Sedmík > Fix For: 4.1.3 > > > Create SY bot test for testing implementation properties. > 1. Create SY project > 2. Add an implementation component (do it for each one) > 3. Select the component and set all available properties > This test should also check bugs reported at SWITCHYARD-1732 and SWITCHYARD-1526 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-196) Create a quickstart fuse bot test

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-196?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-196. ----------------------------------- verified > Create a quickstart fuse bot test > --------------------------------- > > Key: JBTIS-196 > URL: https://issues.jboss.org/browse/JBTIS-196 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.1.3 > Environment: Eclipse Kepler / JBDS 7.1.1.GA > Reporter: Andrej Podhradsky > Assignee: Tomáš Sedmík > Fix For: 4.1.3 > > > Create an automated test for Fuse IDE [2]. Elaborate on simple scenario to be tested. > 1. Switch to Fuse perspective > 2. Create Fuse project through wizard > 3. Create sample route through graphic route editor > 4. Create sample test with JUnit Wizard > 5. Add existing server / Create server through fabric [1] > 6. Deploy application on server > 7. Check application is in active state and correctly working > [1] http://fuse.fusesource.org/fabric/docs/index.html > [2] http://fusesource.com/docs/ide/7.1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-206) Create fuse bot test for creating fuse projects

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-206?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-206. ----------------------------------- > Create fuse bot test for creating fuse projects > ----------------------------------------------- > > Key: JBTIS-206 > URL: https://issues.jboss.org/browse/JBTIS-206 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.1.3 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.1.3 > > > What should be tested: > 1. create a fuse project from available archetypes > 2. check if the generated pom.xml is valid > 3. check if the project contains a valid route definition which can be edited in the camel editor -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-187) Create Recursive XML Text Source Test

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-187?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-187. ----------------------------------- > Create Recursive XML Text Source Test > ------------------------------------- > > Key: JBTIS-187 > URL: https://issues.jboss.org/browse/JBTIS-187 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.1.3 > Environment: Teiid Designer 8.x > Reporter: Andrej Podhradsky > Assignee: Lucie Fabrikova > Fix For: 4.1.3 > > > The test will include: > * Importing an XML schema > * Modeling recursive XML documents > * Setting up a connection to a text source > * Using the TEXTTABLE function to access the data in a relational fashion > * Creating and deploying a VDB > * Executing queries that return XML documents -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-213) Create SY bot test for camel service implementation

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-213?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-213. ----------------------------------- > Create SY bot test for camel service implementation > --------------------------------------------------- > > Key: JBTIS-213 > URL: https://issues.jboss.org/browse/JBTIS-213 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.1.3.Beta5 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.1.3.Beta5, 4.1.3.Final > > > Create SY bot test for camel service implementation > * Camel (Java) > * Camel (XML) > ** using standard XML editor > ** using camel editor from fuse tooling -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18900) CordovaSim: Can't run default FeedHenry app locally

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18900?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen edited comment on JBIDE-18900 at 1/12/15 10:39 AM: ----------------------------------------------------------------------- imagine you could not edit the startup arguments to your project in eclipse ? Why not just always use the same main class as defined in your jar projects manifest.mf ? Why would you need something else ? one simple reasons: What you test/develop is *not* exactly the same as your production deployment settings. feedhenry is a very good example of this - if we had done what you vote for here using feedhenry in development mode would be impossible for users to do. Thus being able to customize the start argument are important. Adding parameters could simply be a field and the field would just be *appended* to the content page; thus: |content| start value| parameter value| actual start page| reason | |null | null | null | index.html | default value for content when null is index.html| |index.html | null | url=localhost:8088 | index.html?url=localhost:8088 | combine content + parameter value with a ? since content had no ? |index.html?cordovamode=true | null | url=blah | index.html?cordovamode=true&url=blah | combine content + parameter value with a & since content contains a ?| |index.html | cordovatesting.html| url=testing | cordovatesting.html?url=testing | content is ignored since start value is now explicitly set|| Above are pretty basic and standard behavior of how launch configs or even any custom configuration that likes convention over configuration works. about the #1 to #3: #1: my assumption is that "run cordovasim w/feedhenry" creates an *additional* launchconfig, not just reuses the one "run cordovasim" uses. Just like when you have test classes in your java project and uses "run junit" it will actually not reuse the same launchconfiguration if your focus is a different class. same here - run cordavsim will run the "plain" launch configuration without start page configured, and "run cordovasim w/feedhenry" would create or reuse the launchconfig that has the parameter/start page set. #2 start value can either be empty (null) or contain a value empty string or a value (i.e. "startme.html") At launch: if start value = null then take content flag value else use the start value #3 so users will still have to manually toggle between running with or without feedhenry so this does not actually solve the original problem afaics ? was (Author: maxandersen): imagine you could not edit the startup arguments to your project in eclipse ? Why not just always use the same main class as defined in your jar projects manifest.mf ? Why would you need something else ? one simple reasons: What you test/develop is *not* exactly the same as your production deployment settings. feedhenry is a very good example of this - if we had done what you vote for here using feedhenry in development mode would be impossible for users to do. Thus being able to customize the start argument are important. Adding parameters could simply be a field and the field would just be *appended* to the content page; thus: ||content| |start value|parameter value|actual start page||reason|| |null | null | null | index.html | default value for content when null is index.html| |index.html | null | url=localhost:8088 | index.html?url=localhost:8088 | combine content + parameter value with a ? since content had no ? |index.html?cordovamode=true | null | url=blah | index.html?cordovamode=true&url=blah | combine content + parameter value with a & since content contains a ?| |index.html | cordovatesting.html| url=testing | cordovatesting.html?url=testing | content is ignored since start value is now explicitly set|| Above are pretty basic and standard behavior of how launch configs or even any custom configuration that likes convention over configuration works. about the #1 to #3: #1: my assumption is that "run cordovasim w/feedhenry" creates an *additional* launchconfig, not just reuses the one "run cordovasim" uses. Just like when you have test classes in your java project and uses "run junit" it will actually not reuse the same launchconfiguration if your focus is a different class. same here - run cordavsim will run the "plain" launch configuration without start page configured, and "run cordovasim w/feedhenry" would create or reuse the launchconfig that has the parameter/start page set. #2 start value can either be empty (null) or contain a value empty string or a value (i.e. "startme.html") At launch: if start value = null then take content flag value else use the start value #3 so users will still have to manually toggle between running with or without feedhenry so this does not actually solve the original problem afaics ? > CordovaSim: Can't run default FeedHenry app locally > --------------------------------------------------- > > Key: JBIDE-18900 > URL: https://issues.jboss.org/browse/JBIDE-18900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.0.Alpha1 > > Attachments: configuration.png, cordovasimFH.png, hello_tom.png, newLaunch.png, preferences.png, ToolsProject-Cloud-App.zip, ToolsProject-Cordova-App.zip > > > Basically, the situation is the following: > 1. *ToolsProject-Cordova-App.zip* - is a basic FH hybrid app (all the app does is saying Hello + 'username' from the input field ) > 2. To run this app one simply needs to unpack the archive and import it as a cordova project to the studio > 3. The application will work with a *remote* server like a charm !hello_tom.png|thumbnail! > 4. However, there is an option to use *local* server instead of *remote* one > 5. *ToolsProject-Cloud-App.zip* - is a app for running local server via grunt task runner > 6. In order to run local server one needs: > - unpack the app > - run *npm install .* > - run *grunt serve* > Need to find the way to made CordovaSim use this *local* server -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18900) CordovaSim: Can't run default FeedHenry app locally

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18900?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18900: --------------------------------------------- imagine you could not edit the startup arguments to your project in eclipse ? Why not just always use the same main class as defined in your jar projects manifest.mf ? Why would you need something else ? one simple reasons: What you test/develop is *not* exactly the same as your production deployment settings. feedhenry is a very good example of this - if we had done what you vote for here using feedhenry in development mode would be impossible for users to do. Thus being able to customize the start argument are important. Adding parameters could simply be a field and the field would just be *appended* to the content page; thus: ||content| |start value|parameter value|actual start page||reason|| |null | null | null | index.html | default value for content when null is index.html| |index.html | null | url=localhost:8088 | index.html?url=localhost:8088 | combine content + parameter value with a ? since content had no ? |index.html?cordovamode=true | null | url=blah | index.html?cordovamode=true&url=blah | combine content + parameter value with a & since content contains a ?| |index.html | cordovatesting.html| url=testing | cordovatesting.html?url=testing | content is ignored since start value is now explicitly set|| Above are pretty basic and standard behavior of how launch configs or even any custom configuration that likes convention over configuration works. about the #1 to #3: #1: my assumption is that "run cordovasim w/feedhenry" creates an *additional* launchconfig, not just reuses the one "run cordovasim" uses. Just like when you have test classes in your java project and uses "run junit" it will actually not reuse the same launchconfiguration if your focus is a different class. same here - run cordavsim will run the "plain" launch configuration without start page configured, and "run cordovasim w/feedhenry" would create or reuse the launchconfig that has the parameter/start page set. #2 start value can either be empty (null) or contain a value empty string or a value (i.e. "startme.html") At launch: if start value = null then take content flag value else use the start value #3 so users will still have to manually toggle between running with or without feedhenry so this does not actually solve the original problem afaics ? > CordovaSim: Can't run default FeedHenry app locally > --------------------------------------------------- > > Key: JBIDE-18900 > URL: https://issues.jboss.org/browse/JBIDE-18900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.0.Alpha1 > > Attachments: configuration.png, cordovasimFH.png, hello_tom.png, newLaunch.png, preferences.png, ToolsProject-Cloud-App.zip, ToolsProject-Cordova-App.zip > > > Basically, the situation is the following: > 1. *ToolsProject-Cordova-App.zip* - is a basic FH hybrid app (all the app does is saying Hello + 'username' from the input field ) > 2. To run this app one simply needs to unpack the archive and import it as a cordova project to the studio > 3. The application will work with a *remote* server like a charm !hello_tom.png|thumbnail! > 4. However, there is an option to use *local* server instead of *remote* one > 5. *ToolsProject-Cloud-App.zip* - is a app for running local server via grunt task runner > 6. In order to run local server one needs: > - unpack the app > - run *npm install .* > - run *grunt serve* > Need to find the way to made CordovaSim use this *local* server -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-20) aggregate SOA source features into a single site

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-20?page=com.atlassian.jira.plugin.s... ] Andrej Podhradsky closed JBTIS-20. ---------------------------------- Verified that all source bundles are aggregated in JBDS-IS 8.0.0.Beta2a, except one BPMN2 feature. This bug is reported at JBTIS-375 so closing this issue. > aggregate SOA source features into a single site > ------------------------------------------------ > > Key: JBTIS-20 > URL: https://issues.jboss.org/browse/JBTIS-20 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: releng > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Blocker > Fix For: 8.0.0.Beta2, 4.2.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-300) JBDS-IS 8.0.0.Alpha1 contains old version of bpmn2 modeler

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-300?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-300. ----------------------------------- JBDS-IS 8.0.0.Beta2a contains BPMN2 of version 1.1.1.201412181844 > JBDS-IS 8.0.0.Alpha1 contains old version of bpmn2 modeler > ---------------------------------------------------------- > > Key: JBTIS-300 > URL: https://issues.jboss.org/browse/JBTIS-300 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.Alpha1 > Environment: JBDS 8.0.0.Beta3 > Reporter: Jozef Marko > Assignee: Paul Leacu > Priority: Critical > Fix For: 8.0.0.Alpha2, 4.2.0.Alpha2 > > > Current version of bpmn2 modeler is 1.0.2. Desired version is 1.1.0 [1] which works well with eclipse luna. > [1] http://download.eclipse.org/bpmn2-modeler/updates/luna/1.1.0/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-165) Regression - Cannot add a file to the attachments

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-165?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-165. ----------------------------------- Verified with JBDS 7.1.1.GA + JBDS-IS 7.0.3.GA and JBDS 8.0.1.GA + JBDS-IS 8.0.0.Beta2a > Regression - Cannot add a file to the attachments > ------------------------------------------------- > > Key: JBTIS-165 > URL: https://issues.jboss.org/browse/JBTIS-165 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: ESB > Affects Versions: 4.1.2 > Environment: JBoss ESB Tools 1.5.300.Final-v20130815-1755-B1189 > Reporter: Andrej Podhradsky > Assignee: Viacheslav Kabanovich > Priority: Blocker > Attachments: esb_attachment_bug.png, test.zip > > > Cannot add a file to the attachments from esbcontent folder. It's also impossible to add .txt file from the root but .zip file is possible to add. See the screenshot -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2015