September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15502) Internal browser is using wrong URL if launched for already deployed ear-app via Servers tab

by Tomas Repel (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15502?page=com.atlassian.jira.plugi... ] Tomas Repel updated JBIDE-15502: -------------------------------- Description: I am using JBDS 7.0.0.GA with Integration Stack, EAP 6.1.0 is configured in Servers tab. When importing JDF example ejb-in-ear [1], then right-click on jboss-ejb-in-ear-ear -> Run As -> Run on Server, the example is deployed and the internal browser window is opened automatically using following URL: http://localhost:8080/jboss-ejb-in-ear/greeter.jsf (this is correct behavior). If you go to Servers tab, expand the EAP 6.1 Server, right-click on deployed jboss-ejb-in-ear-ear, use Show in menu item and then click Web Browser, the internal browser is opened with wrong URL (http://localhost:8080/jboss-ejb-in-ear-web/). It seems the configuration in application.xml file is ignored for some reason. [1] http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/ejb-in-ear/ was: I am using JBDS 7.0.0.GA with Integration Stack, EAP 6.1.0 is configured in Servers tab. When importing JDF example ejb-in-ear [1], then right-click on jboss-ejb-in-ear-ear -> Run As -> Run on Server, the example is deployed and the internal browser window is opened automatically using following URL: http://localhost:8080/jboss-ejb-in-ear/greeter.jsf (this is correct behavior). If you go to Servers tab, expand the EAP 6.1 Server, right-click on deployed jboss-ejb-in-ear-ear, use Show in menu item and then click Web Browser, the internal browser is opened with wrong URL (http://localhost:8080/jboss-ejb-in-ear-web/). It seems the configuration in application.xml file is ignored for some reason. [1]http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/ejb-in-ear/ > Internal browser is using wrong URL if launched for already deployed ear-app via Servers tab > -------------------------------------------------------------------------------------------- > > Key: JBIDE-15502 > URL: https://issues.jboss.org/browse/JBIDE-15502 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Tomas Repel > > I am using JBDS 7.0.0.GA with Integration Stack, EAP 6.1.0 is configured in Servers tab. When importing JDF example ejb-in-ear [1], then right-click on jboss-ejb-in-ear-ear -> Run As -> Run on Server, the example is deployed and the internal browser window is opened automatically using following URL: http://localhost:8080/jboss-ejb-in-ear/greeter.jsf (this is correct behavior). > If you go to Servers tab, expand the EAP 6.1 Server, right-click on deployed jboss-ejb-in-ear-ear, use Show in menu item and then click Web Browser, the internal browser is opened with wrong URL (http://localhost:8080/jboss-ejb-in-ear-web/). > It seems the configuration in application.xml file is ignored for some reason. > [1] http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/ejb-in-ear/ -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2767: ------------------------------------------- This is a feature request - thus Burr is the one that needs to +1 it first. > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Rob Stryker > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15502) Internal browser is using wrong URL if launched for already deployed ear-app via Servers tab

by Tomas Repel (JIRA)

Tomas Repel created JBIDE-15502: ----------------------------------- Summary: Internal browser is using wrong URL if launched for already deployed ear-app via Servers tab Key: JBIDE-15502 URL: https://issues.jboss.org/browse/JBIDE-15502 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Reporter: Tomas Repel I am using JBDS 7.0.0.GA with Integration Stack, EAP 6.1.0 is configured in Servers tab. When importing JDF example ejb-in-ear [1], then right-click on jboss-ejb-in-ear-ear -> Run As -> Run on Server, the example is deployed and the internal browser window is opened automatically using following URL: http://localhost:8080/jboss-ejb-in-ear/greeter.jsf (this is correct behavior). If you go to Servers tab, expand the EAP 6.1 Server, right-click on deployed jboss-ejb-in-ear-ear, use Show in menu item and then click Web Browser, the internal browser is opened with wrong URL (http://localhost:8080/jboss-ejb-in-ear-web/). It seems the configuration in application.xml file is ignored for some reason. [1]http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/ejb-in-ear/ -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15499) Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15499?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15499: --------------------------------------------- [~snjeza] be my guest to create a PR for this - use similar mechanisms as found in eclipse marketplace but with less bugs :) > Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-15499 > URL: https://issues.jboss.org/browse/JBIDE-15499 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.1.1.Beta1 > > > usecase is that you can have a link to a connector, such as JBDS-IS could be installed by drag'n'drop to jboss tools or jbds. > Similar to eclipse marketplace for marketplace urls something like: > * https://devstudio.jboss.com/central/install?connector=com.jbds.integratio... or > * http://download.jboss.org/jbosstools/central/install?CID=com.jbds.integra... > would install the two connectors named "com.jbds.integration-stack.bpel" and "org.eclipse.m2e" > This would allow drag'n'drop install from html docs. > Consider also supporting this from any clipboard object (eg., dragged from an Acrobat Reader PDF or Microsoft Office doc). Would need to ensure we do lots of platform testing. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15499) Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15499?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15499: --------------------------------------------- in addition - if this could also be used to trigger start of wizards/import of quickstarts would be interesting too. > Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-15499 > URL: https://issues.jboss.org/browse/JBIDE-15499 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.1.1.Beta1 > > > usecase is that you can have a link to a connector, such as JBDS-IS could be installed by drag'n'drop to jboss tools or jbds. > Similar to eclipse marketplace for marketplace urls something like: > * https://devstudio.jboss.com/central/install?connector=com.jbds.integratio... or > * http://download.jboss.org/jbosstools/central/install?CID=com.jbds.integra... > would install the two connectors named "com.jbds.integration-stack.bpel" and "org.eclipse.m2e" > This would allow drag'n'drop install from html docs. > Consider also supporting this from any clipboard object (eg., dragged from an Acrobat Reader PDF or Microsoft Office doc). Would need to ensure we do lots of platform testing. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15494) Software/Update page - Cannot create temporary directory

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15494?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15494: --------------------------------------------- Bug opened at bugs.sun.com - have not yet received a url for the bugreport. Submitted: package tempfile; import java.io.File; import java.io.IOException; public class Main { public static void main(String[] args) throws IOException { String fileName= "/foo"; File target = File.createTempFile(fileName, ".jar", new File(".")); System.out.println(target.getCanonicalPath() + " " + target.exists()); } } which fails on recent _40 version but not on any other previous version of java as far as I can see. Issue is that the fix done to avoid ../../foo to be passed in removed the existing guard/allowance to pass in just /foo. > Software/Update page - Cannot create temporary directory > -------------------------------------------------------- > > Key: JBIDE-15494 > URL: https://issues.jboss.org/browse/JBIDE-15494 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Final, 4.1.1.Alpha1 > Reporter: Radim Hopp > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.1.1.Alpha2 > > > Recently, Software/Update page of JBoss Central stopped working (No Connectors Found). > Error log: > {noformat} > Cannot download bundle at http://download.jboss.org/jbosstools/updates/development/kepler/plugins/o...: Unable to create temporary file > {noformat} > {noformat} > a.io.IOException: Unable to create temporary file > at java.io.File$TempDirectory.generateFile(File.java:1891) > at java.io.File.createTempFile(File.java:1979) > at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:217) > at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > {noformat} > This issue affects both JBDS and JBT, both not only in 7.1.0 (4.1.1) but also in 7.0.0.Final (4.1.0.Final), thus it's marked as blocker. -- 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, 9 months

1
0
0 / 0

[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 updated JBTIS-180: ------------------------------------ Description: 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 was: 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 a bug reported at SWITCHYARD-1732 > 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 > Security Level: Public(Everyone can see) > 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 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, 9 months

1
0
0 / 0

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

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-180: --------------------------------------- Summary: 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 Security Level: Public (Everyone can see) 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 a bug reported at SWITCHYARD-1732 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-173) Teiid has custom user agreement text for attribution that fits better in about.html

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/JBTIS-173?page=com.atlassian.jira.plugin.... ] Paul Richardson resolved JBTIS-173. ----------------------------------- Resolution: Done Fixed in 8.2.x branch for next teiid product release > Teiid has custom user agreement text for attribution that fits better in about.html > ----------------------------------------------------------------------------------- > > Key: JBTIS-173 > URL: https://issues.jboss.org/browse/JBTIS-173 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: teiid > Affects Versions: 4.1.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Paul Richardson > > when installing from Beta1, Teiid has this text added to license text: > "In addition, plugins contain work credited to Brian Goetz and Tim Peierls (http://www.jcip.net) (c) 2005, released under the Creative Commons Attribution License." > This is already documented in the text before it and makes Teiid show up as "special" compared to the other features. > This specific attribution should be added to the feature/plugins about.html instead as done for i.e. browsersim (https://github.com/jbosstools/jbosstools-vpe/blob/master/plugins/org.jbos...) -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2768) Installer scripts should be linked from jbdevstudio

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2768?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2768: ------------------------------------------- I agree that we should not mix devstudio and jbt instructions, also these scripts should really be cleaned up and not contain nboldt specific settings if they are to be shared as documentation. Also the list of features aren't in sync thus that should be figured out too before making it actually linked up IMO. until then I suggest to just put the jbt related ones in jbosstools-devdoc and use jbdevstudio-devdoc for jbds instead of in magnolia. > Installer scripts should be linked from jbdevstudio > --------------------------------------------------- > > Key: JBDS-2768 > URL: https://issues.jboss.org/browse/JBDS-2768 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.Alpha1 > Reporter: Michelle Murray > Assignee: Nick Boldt > > Currently availability of scripts is listed on community site: > https://www.jboss.org/tools/download/installation/update_4_1#fromscript > And that links to instructions on community site: > http://download.jboss.org/jbosstools/updates/scripted-installation/JBDS/ > Given that the instructions are for JBDS, the sites should be devstudio sites. For example, availability stated here: > https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html > And linking to scripts on same base URL. > If we want to have scripts on community site then they should only be for headless JBT install. -- 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, 9 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 2013