November 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-9044) New BPEL Process wizard should display a warning when user selects a target other than bpelContent folder

by Robert (Bob) Brodt (JIRA)

New BPEL Process wizard should display a warning when user selects a target other than bpelContent folder --------------------------------------------------------------------------------------------------------- Key: JBIDE-9044 URL: https://issues.jboss.org/browse/JBIDE-9044 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpel Affects Versions: 3.3.0.M1 Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Priority: Minor Fix For: 3.3.x Although the user should be allowed to create a new BPEL process anywhere in the workspace (for e.g. a non-deployable BPEL process file intended to be used for documentation only), the New BPEL Process wizard should display a warning message if the target folder is not bpelContent. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7922) WSDL should be read once

by Lukas Jungmann (JIRA)

WSDL should be read once ------------------------ Key: JBIDE-7922 URL: https://issues.jboss.org/browse/JBIDE-7922 Project: Tools (JBoss Tools) Issue Type: Task Reporter: Lukas Jungmann see http://anonsvn.jboss.org/repos/jbosstools/trunk/ws/plugins/org.jboss.tool... The class is involved in Top-Down web service scenario where it is responsible for creating a web service implementation class from artifacts generated by wscosume tool and user supplied WSDL. The problem with this class is that for each data it needs to know from wsdl there is separate read from external resource (local WSDL file) - see getTNSFromWSDL(), getServiceNameFromWSDL() (as of r27544) and this can cause some performance penalty in case of big WSDL. The code should be changed so the particular WSDL is read only once per wizard's run. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8989) Setup m2eclipse-wtp build jobs on JBoss infrastructure

by Fred Bricon (JIRA)

Setup m2eclipse-wtp build jobs on JBoss infrastructure ------------------------------------------------------ Key: JBIDE-8989 URL: https://issues.jboss.org/browse/JBIDE-8989 Project: Tools (JBoss Tools) Issue Type: Task Components: maven, UpStream Affects Versions: 3.3.x Reporter: Fred Bricon Assignee: Nick Boldt Priority: Blocker Fix For: 3.3.x The current JBT/maven 3.3.x builds fail due to an incompatibility between m2e-core and m2eclipse-wtp. The Sonatype Hudson grid, used to build m2eclipse-wtp, is down, for good. Seems the best way to build m2eclipse-wtp is to do it on our own infrastructure. Ideally we'd need to create 2 new Hudson jobs on the JBoss grid, building https://github.com/sonatype/m2eclipse-wtp.git and basically running {noformat} mvn clean deploy -Dtarget.platform=m2e-wtp-e36 -Ppublish-site{noformat} and {noformat} mvn clean deploy -Dtarget.platform=m2e-wtp-e37{noformat} We'll need to set the appropriate parameters for site publishing (see https://github.com/sonatype/m2eclipse-wtp/blob/master/org.maven.ide.eclip...) as well as things like -Xmx512m and the path to a private local repo, if needed. Please contact me you need more informations. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7005) Create validator for non-externilized string on web page

by Maxim Areshkau (JIRA)

Create validator for non-externilized string on web page --------------------------------------------------------- Key: JBIDE-7005 URL: https://jira.jboss.org/browse/JBIDE-7005 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml source editing Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.3.x Create a validator which is looking for non-externalised strings on web-pages simular to eclipse non-ext string validator. Here should be a prefference page for configuration validation and Quick fixes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6020) Add interactive debugging to BPEL editor

by Robert (Bob) Brodt (JIRA)

Add interactive debugging to BPEL editor ---------------------------------------- Key: JBIDE-6020 URL: https://jira.jboss.org/jira/browse/JBIDE-6020 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpm Affects Versions: 3.1.0.CR2 Reporter: Robert (Bob) Brodt At the least I would like to be able to set breakpoints and inspect variables at runtime; of course a full-featured interactive debugger, which allows single-stepping, changing variables, watchpoints, etc. would be nice to have. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
7
0 / 0

[JBoss JIRA] (JBIDE-9999) Forge Launch Configurations Don't Get Deleted

by Koen Aers (Created) (JIRA)

Forge Launch Configurations Don't Get Deleted --------------------------------------------- Key: JBIDE-9999 URL: https://issues.jboss.org/browse/JBIDE-9999 Project: Tools (JBoss Tools) Issue Type: Task Components: forge Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.3.0.Beta1 Starting Forge results in the creation of a launch configuration. This should be deleted from the list of configurations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
2
0 / 0

[JBoss JIRA] (JBDS-1876) emma code coverage in overall jbosstools-3.3_trunk.soa-tooling.tests fails to find org.eclipse.bpel.* sources; cannot do coverage report so builds fail

by Nick Boldt (Created) (JIRA)

emma code coverage in overall jbosstools-3.3_trunk.soa-tooling.tests fails to find org.eclipse.bpel.* sources; cannot do coverage report so builds fail ------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBDS-1876 URL: https://issues.jboss.org/browse/JBDS-1876 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Build, updatesite, Upstream Affects Versions: 5.0.0.M4 Reporter: Nick Boldt Assignee: Len DiMaggio Fix For: 5.0.0.M4 {code} 2011-10-07 15:42:31) nickboldt: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job... is failing due to emma coverage for bpel (2011-10-07 15:42:57) nickboldt: it's failing to generate emma coverage because the sources for o.e.bpel.* aren't in the workspace, so the build is therefore red (2011-10-07 15:43:28) ldimaggi: ok? (2011-10-07 15:43:51) nickboldt: I'm wondering if you're ok w/ just disabling code coverage for bpel, or if you want us to figure out some way to fetch org.eclipse.bpel.* sources into the .tests job's workspace so that it can properly do the emma code coverage reporting (2011-10-07 15:44:32) ldimaggi: 1) For today disable emma (2011-10-07 15:44:41) ldimaggi: 2) On Monday - let's try to fix it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9197) No user error message for UnsupportedClassVersionError

by Tom Fennelly (JIRA)

No user error message for UnsupportedClassVersionError ------------------------------------------------------ Key: JBIDE-9197 URL: https://issues.jboss.org/browse/JBIDE-9197 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 3.3.0.M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-9082) If project name contains spaces - VPE does not display pictures on html page

by Vitali Yemialyanchyk (JIRA)

If project name contains spaces - VPE does not display pictures on html page ---------------------------------------------------------------------------- Key: JBIDE-9082 URL: https://issues.jboss.org/browse/JBIDE-9082 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.3.0.M1 Reporter: Vitali Yemialyanchyk Assignee: Denis Maliarevich Priority: Blocker create project with name without spaces, create html page with image (path to image is relative to project) - image is visible; update project name with space in the middle of the name - open html page - image is not visible; rename back - image is visible; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
9
0 / 0

[JBoss JIRA] (JBIDE-9975) VPE does not display css pictures if it's path contains "(" & ")" and may be others special symbols

by Vitali Yemialyanchyk (Created) (JIRA)

VPE does not display css pictures if it's path contains "(" & ")" and may be others special symbols --------------------------------------------------------------------------------------------------- Key: JBIDE-9975 URL: https://issues.jboss.org/browse/JBIDE-9975 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.3.0.M4 Reporter: Vitali Yemialyanchyk Assignee: Yahor Radtsevich Priority: Critical I've get this problem just cause my workspace path: ${workspace_loc}/../runtime-New_configuration(2) I'll attach screenshot and examples and description how to fix it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

14
61
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 November 2011