March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16476) Run As on JAX-RS Node generates wrong URI if Application path has no leading slash

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16476?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-16476. ----------------------------------- Verified in JBDS 8.0.0 Alpha2-v20140214-1707-B71 > Run As on JAX-RS Node generates wrong URI if Application path has no leading slash > ---------------------------------------------------------------------------------- > > Key: JBIDE-16476 > URL: https://issues.jboss.org/browse/JBIDE-16476 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.2.0.Alpha2 > > > * Create an HTML5 project from central > * In JaxRsActivator, change @ApplicationPath("/rest") to @ApplicationPath("rest") > * Do Run As > Run on Server on the GET rest/members endpoint in the JAX-RW Web Services node > * Assert the WS Tester opens with http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members > FAIL : URL is http://localhost:8080/jboss-as-kitchensink-html5-mobilerest/members > [JAX-RS doc|http://docs.oracle.com/cd/E19798-01/821-1841/ginpw/] says leading slashes are not mandatory for @Path, but I didn't see any mention of ApplicationPath (my guess is the rule should be consistent). At least, the application server doesn't puke on it so it's a valid use case to me. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16606) New Server Wizard updated for 'profiles'

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16606?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-16606: ------------------------------------- Hi Martin: I made some commits this morning. Give this a day to build out and then give it another runthrough. > New Server Wizard updated for 'profiles' > ---------------------------------------- > > Key: JBIDE-16606 > URL: https://issues.jboss.org/browse/JBIDE-16606 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Rob Stryker > Assignee: Martin Malina > Fix For: 4.2.0.Beta1 > > Attachments: new-new-server.png, new_server.jpg, new_server_remote.jpg > > > With the additions of server profiles, servers in the rse profile (or others) do not necessarily require a local runtime. This means in a new server wizard, we don't need to force the user to create a runtime until they're in a profile that requires one. > This will make changes to the new server wizard workflow which may affect some swt bot tests and documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16606) New Server Wizard updated for 'profiles'

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16606?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-16606: -------------------------------- Assignee: Martin Malina (was: Rob Stryker) > New Server Wizard updated for 'profiles' > ---------------------------------------- > > Key: JBIDE-16606 > URL: https://issues.jboss.org/browse/JBIDE-16606 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Rob Stryker > Assignee: Martin Malina > Fix For: 4.2.0.Beta1 > > Attachments: new-new-server.png, new_server.jpg, new_server_remote.jpg > > > With the additions of server profiles, servers in the rse profile (or others) do not necessarily require a local runtime. This means in a new server wizard, we don't need to force the user to create a runtime until they're in a profile that requires one. > This will make changes to the new server wizard workflow which may affect some swt bot tests and documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-7515) Add (optional) start/stop script to the Deploy only server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7515?page=com.atlassian.jira.plugin... ] Rob Stryker resolved JBIDE-7515. -------------------------------- Resolution: Done As shown above, this patch has fixed several things. First, the deploy-only server previously was not able to be created in rse mode. You had to create it in local mode, and then switch to rse in the editor. This was bad workflow. Second, the enhancement of allowing launch scripts has been added. The launch tabs, however, will be inactive if your server is set to ignore launches in the server editor. If, however, that setting is not checked, then the launch tabs will be active and you can set startup or shutdown commands. In the event of a shutdown, the shutdown script will be called. In the event the shutdown script fails, the initial launch process will be terminated. If your initial launch leaves background processes running, and we force-kill the launched process, the deploy-only server will NOT terminate all of them! This is because java cannot send specific termination signals to a process. The java implementation of process.destroy() may kill, for example, a wildfly's standalone.sh, but will not kill the java process that standalone.sh has launched. Users should take care when using this feature. > Add (optional) start/stop script to the Deploy only server > ---------------------------------------------------------- > > Key: JBIDE-7515 > URL: https://issues.jboss.org/browse/JBIDE-7515 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > Attachments: JBIDE-7515_1.png, JBIDE-7515_2.png, JBIDE-7515_3.png, JBIDE-7515_lc1.png, JBIDE-7515_lc2.png, JBIDE-7515_lc3.png > > > Currently the "Deploy only" server can just "deploy" - I suggest we add support for running a start (and optional) a stop script to let users start/stop what they want. > This would be a nice stop-gap feature for things like AS 7 or other runtimes out in the world until "native" integration is possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2913) Console log when running EAP 6.2.x not formatted correctly

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-2913?page=com.atlassian.jira.plugin.... ] Rob Stryker closed JBDS-2913. ----------------------------- Resolution: Done > Console log when running EAP 6.2.x not formatted correctly > ---------------------------------------------------------- > > Key: JBDS-2913 > URL: https://issues.jboss.org/browse/JBDS-2913 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: server > Affects Versions: 7.1.0.GA > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Fix For: 7.1.1.CR1 > > Attachments: dodgyDialgue.png, EAP-6.1.0.png, EAP-6.2.1.png > > > When running EAP from JBDS the console logging shows strange characters from the logging. See screen shots comparing EAP 6.1.0 to EAP 6.2.1 (this also happens on EAP 6.2.0) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-7515) Add (optional) start/stop script to the Deploy only server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7515?page=com.atlassian.jira.plugin... ] Rob Stryker updated JBIDE-7515: ------------------------------- Attachment: JBIDE-7515_lc2.png JBIDE-7515_lc1.png JBIDE-7515_lc3.png JBIDE-7515_1.png JBIDE-7515_3.png JBIDE-7515_2.png Attached some screenshots. > Add (optional) start/stop script to the Deploy only server > ---------------------------------------------------------- > > Key: JBIDE-7515 > URL: https://issues.jboss.org/browse/JBIDE-7515 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > Attachments: JBIDE-7515_1.png, JBIDE-7515_2.png, JBIDE-7515_3.png, JBIDE-7515_lc1.png, JBIDE-7515_lc2.png, JBIDE-7515_lc3.png > > > Currently the "Deploy only" server can just "deploy" - I suggest we add support for running a start (and optional) a stop script to let users start/stop what they want. > This would be a nice stop-gap feature for things like AS 7 or other runtimes out in the world until "native" integration is possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-254) JBoss Developer Studio 7 fails in Camel Editor under "Properties" when click on "Documentation"

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBTIS-254?page=com.atlassian.jira.plugin.... ] Lars Heinemann commented on JBTIS-254: -------------------------------------- Easiest would be to install a JBDS 7 only and then add the update site and install from there. Lars > JBoss Developer Studio 7 fails in Camel Editor under "Properties" when click on "Documentation" > ----------------------------------------------------------------------------------------------- > > Key: JBTIS-254 > URL: https://issues.jboss.org/browse/JBTIS-254 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Fuse IDE > Environment: JBDS 7.1 and Integration Stack 7.0 > Reporter: Roger Hui > Assignee: Lars Heinemann > > Trying to use the Camel editor in JBoss Developer Studio 7 fails as soon as we try to access the "Documentation" tab in the "Properties" View. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16584) Cordova engine version change is not reflected in running CordovaSim

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16584?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-16584: ------------------------------------------- Assignee: Ilya Buziuk > Cordova engine version change is not reflected in running CordovaSim > -------------------------------------------------------------------- > > Key: JBIDE-16584 > URL: https://issues.jboss.org/browse/JBIDE-16584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2-v20140212-1651-B82 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.2.0.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > 1. Create Hybrid Mobile Project and download 3.1.0 and 3.2.0 Cordova engines > 2. Select 3.1.0. as Cordova engine for project > 3. Add device feature > 4. Add this line to index.js deviceready: function() > alert("Cordova version: " + device.cordova); > 5. Run project with CordovaSim > ASSERT: 3.1.0 version is displayed in CordovaSim > 6. Change project Cordova engine version to 3.2.0 > ERROR: 3.1.0 version is displayed in CordovaSim -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-254) JBoss Developer Studio 7 fails in Camel Editor under "Properties" when click on "Documentation"

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBTIS-254?page=com.atlassian.jira.plugin.... ] Lars Heinemann resolved JBTIS-254. ---------------------------------- Resolution: Done Fix included into 7.2.x and master branch of Fuse Tooling. Will be part of the next release. > JBoss Developer Studio 7 fails in Camel Editor under "Properties" when click on "Documentation" > ----------------------------------------------------------------------------------------------- > > Key: JBTIS-254 > URL: https://issues.jboss.org/browse/JBTIS-254 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Fuse IDE > Environment: JBDS 7.1 and Integration Stack 7.0 > Reporter: Roger Hui > Assignee: Lars Heinemann > > Trying to use the Camel editor in JBoss Developer Studio 7 fails as soon as we try to access the "Documentation" tab in the "Properties" View. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16617) New Hybrid Mobile dialog shows error before anything is entered

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16617?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-16617: -------------------------------------- This is now fixed as part of the new project wizard improvements. http://www.youtube.com/watch?v=QrsQJvI6SO4 > New Hybrid Mobile dialog shows error before anything is entered > --------------------------------------------------------------- > > Key: JBIDE-16617 > URL: https://issues.jboss.org/browse/JBIDE-16617 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Alpha2 > Environment: JBDS 8.0.0.Alpha2b B71 > Reporter: Martin Malina > Fix For: 4.2.0.Beta1 > > Attachments: hybrid-dialog-1.png, hybrid-dialog-2.png > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > When you create a new hybrid mobile project (File -> New -> Hybrid Mobile...), on the first page of the dialog, you're shown an error at the top even though you haven't done anything yet. > This is ugly and violates http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html#Wizards Guideline 5.3. > !hybrid-dialog-1.png! > Also, consider polishing the next page, too. > !hybrid-dialog-2.png! > If I don't have an engine installed, I get the error Please select a Hybrid Mobile Engine. This is not very nice, but I'm not sure how to improve it - perhaps if there are no engines installed, have a different message? And if you have at least one engine, select the first one by default, so that we avoid unnecessary errors? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

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 March 2014