September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18461) org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18461?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-18461: ------------------------------------------- All I'm asking here is that we add the IJBossToolingConstants.EAP_61 reference to the array for org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants > org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61 > -------------------------------------------------------------------------------- > > Key: JBIDE-18461 > URL: https://issues.jboss.org/browse/JBIDE-18461 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Brian Fitzpatrick > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.CR2 > > > When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-16066: ------------------------------------------- Adding the IJBossToolingConstants.EAP_61 reference to the array for org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants would do it. :) > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR2 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick edited comment on JBIDE-16066 at 9/30/14 6:15 PM: -------------------------------------------------------------------- You can get around the "Runtime Location not set" problem by defining a JBoss AS 7.1 runtime that points to EAP. Going that route, I was able to create a Dynamic Web Project, create a WSDL there, and then create a new Web Service (top-down), which created a new EAR file that was deployed just fine. And I was able to get to the WSDL via the WS Tester without incident. was (Author: bfitzpat): You can get around the "Runtime Location not set" problem by defining a JBoss AS 7.1 runtime that points to EAP. Going that route, I was able to create a Dynamic Web Project, create a WSDL there, and then create a new Web Service (top-down), which created a new EAR file that was deployed just fine. > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR2 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-16066: ------------------------------------------- You can get around the "Runtime Location not set" problem by defining a JBoss AS 7.1 runtime that points to EAP. Going that route, I was able to create a Dynamic Web Project, create a WSDL there, and then create a new Web Service (top-down), which created a new EAR file that was deployed just fine. > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR2 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16066: --------------------------------------------- [~bfitzpat] if you know what to fix can you make a PR for it and I or Rob will review it when we wake up ;) > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR2 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18461) org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18461?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18461: ---------------------------------------- Fix Version/s: 4.2.0.CR2 > org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61 > -------------------------------------------------------------------------------- > > Key: JBIDE-18461 > URL: https://issues.jboss.org/browse/JBIDE-18461 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Brian Fitzpatrick > Priority: Critical > Fix For: 4.2.0.CR2 > > > When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18461) org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18461?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18461: ---------------------------------------- Assignee: Rob Stryker > org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61 > -------------------------------------------------------------------------------- > > Key: JBIDE-18461 > URL: https://issues.jboss.org/browse/JBIDE-18461 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Brian Fitzpatrick > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.CR2 > > > When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick edited comment on JBIDE-16066 at 9/30/14 5:59 PM: -------------------------------------------------------------------- I have a workaround for JBIDE-18461, but it would be MUCH BETTER if it was fixed upstream. It is the cause of the "The JBoss WS Runtime Location is not set. Please set the location on the JBoss WS preferences page." message that comes up when you try to go beyond the first page of the WTP-based Web Service wizard. I suspect that it's a timing thing, because I can get WS projects to deploy and start sometimes via the wizard in my dev environment. But it's inconsistent. And I am unable to test in a built version of JBDS 8 or JBDS 7.1.1 at this point. [~maxandersen] getting JBIDE-18461 into CR2 would make this a lot easier. was (Author: bfitzpat): I have a workaround for JBIDE-18461, but it would be MUCH BETTER if it was fixed upstream. It is the cause of the "The JBoss WS Runtime Location is not set. Please set the location on the JBoss WS preferences page." message that comes up when you try to go beyond the first page of the WTP-based Web Service wizard. I suspect that it's a timing thing, because I can get WS projects to deploy and start sometimes via the wizard in my dev environment. But it's inconsistent. > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR2 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-16066: ------------------------------------------- I have a workaround for JBIDE-18461, but it would be MUCH BETTER if it was fixed upstream. It is the cause of the "The JBoss WS Runtime Location is not set. Please set the location on the JBoss WS preferences page." message that comes up when you try to go beyond the first page of the WTP-based Web Service wizard. I suspect that it's a timing thing, because I can get WS projects to deploy and start sometimes via the wizard in my dev environment. But it's inconsistent. > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR2 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18461) org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61

by Brian Fitzpatrick (JIRA)

Brian Fitzpatrick created JBIDE-18461: ----------------------------------------- Summary: org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61 Key: JBIDE-18461 URL: https://issues.jboss.org/browse/JBIDE-18461 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.0.CR1 Reporter: Brian Fitzpatrick Priority: Critical When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework -- This message was sent by Atlassian JIRA (v6.3.1#6329)

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