November 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-1595) Editing Documentation property for WSDL - result is that text written to wsdl shows a one-char lag behind that shown in property field in JBDS

by Len DiMaggio (JIRA)

Editing Documentation property for WSDL - result is that text written to wsdl shows a one-char lag behind that shown in property field in JBDS ----------------------------------------------------------------------------------------------------------------------------------------------- Key: JBDS-1595 URL: https://issues.jboss.org/browse/JBDS-1595 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: visualeditor Environment: Version: 4.0.0.GA Build id: v20110216-1930-H239-GA Build date: 20110216-1930 SOA-P 5.1 GA JBoss Tools http://download.jboss.org/jbosstools/updates/nightly/trunk/ (BPEL editor) 1.0.0.v20110217-0324-H60-Alpha1 Reporter: Len DiMaggio Editing Documentation property for WSDL - result is that text written to wsdl shows a one-char lag behind that shown in property field in JBDS See the attached screen shot for an example of this -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8329) Automatic detection of web port does not work for EAP 4.3

by Magnus Mogren (JIRA)

Automatic detection of web port does not work for EAP 4.3 --------------------------------------------------------- Key: JBIDE-8329 URL: https://issues.jboss.org/browse/JBIDE-8329 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.CR1 Reporter: Magnus Mogren Assignee: Rob Stryker The automatic detection of web port does not work for EAP 4.3 servers. The reason is a faulty XPath expession used to detect the port: //Server/Service[@name='jboss.web']/Connector[count(@sslProtocol) = 0 and (count(@protocol) = 0 or @protocol = 'HTTP/1.1')] That expression tries to get the value of the Connector element in the server.xml, not the port attribute of the element. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8045) Unable to select fault variable data type in faultHandler.

by Marek Baluch (JIRA)

Unable to select fault variable data type in faultHandler. ---------------------------------------------------------- Key: JBIDE-8045 URL: https://issues.jboss.org/browse/JBIDE-8045 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.Beta2, 3.2.0.CR1 Reporter: Marek Baluch Attachments: fault_handler.zip User is not able to select the data type for a user defined fault when defining a faultHandler catch branch. It's possible to attempt to select the data type using the browse button but the chosen type is not noticed by the UI. The message structure is missing too. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
10
0 / 0

[JBoss JIRA] Created: (JBIDE-7953) Add "main menu" and/or "context menu" actions for all remaining operations in BPEL editor.

by Marek Baluch (JIRA)

Add "main menu" and/or "context menu" actions for all remaining operations in BPEL editor. ------------------------------------------------------------------------------------------ Key: JBIDE-7953 URL: https://issues.jboss.org/browse/JBIDE-7953 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpel Affects Versions: 3.2.0.Beta2 Reporter: Marek Baluch The missing operations which are not accessible via the main or context menu are the following: - addition/removal of variables - addition/removal of partner links - addition/removal of correlation sets - addition/removal of message exchanges -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

7
12
0 / 0

[JBoss JIRA] Created: (JBIDE-4454) Write automated tests for UI part of JBT

by Yura Zhishko (JIRA)

Write automated tests for UI part of JBT ---------------------------------------- Key: JBIDE-4454 URL: https://jira.jboss.org/jira/browse/JBIDE-4454 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Yura Zhishko -- 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

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-7924) Allow user to create a web service in custom source root

by Lukas Jungmann (JIRA)

Allow user to create a web service in custom source root -------------------------------------------------------- Key: JBIDE-7924 URL: https://issues.jboss.org/browse/JBIDE-7924 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.2.0.Beta2 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -create or have a web project with two or more java source roots, say src (default) and src2 (custom) -create some @WebService class in the src2 source root -create a Bottom-up web service from the class created in previous step => generated classes are in src (default) java source root but I'd expect them in src2 (custom) source root since the class I used is there or I should have an option to choose where to put generated classes for Top-down ws there's no way to say where to put generated stuff If I choose to use Axis, I'm given an option to specify target source folder, if I use JBossWS I'm not given any option -- 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-8075) Cannot create message correlation property using the wizzard.

by Marek Baluch (JIRA)

Cannot create message correlation property using the wizzard. ------------------------------------------------------------- Key: JBIDE-8075 URL: https://issues.jboss.org/browse/JBIDE-8075 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Environment: JBoss BPEL editor: 1.0.0.v20110106-2124-H21-CR1 Reporter: Marek Baluch As stated in the summary I cannot create message correlation property using the wizzard. When a property type is selected then the "Create Message Property" dialog will not notice the selection - no type is shown after the "Type:" label and the "New..." alias button remains greyed-out. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

7
18
0 / 0

[JBoss JIRA] Created: (JBIDE-4971) Deploying BIRT aaplication to JBoss AS 5.x

by Snjezana Peco (JIRA)

Deploying BIRT aaplication to JBoss AS 5.x ------------------------------------------ Key: JBIDE-4971 URL: https://jira.jboss.org/jira/browse/JBIDE-4971 Project: Tools (JBoss Tools) Issue Type: Bug Components: birt, JBossAS Affects Versions: 3.1.0.M3 Reporter: Snjezana Peco Assignee: Snjezana Peco Steps to reproduce - download testbirt.zip project from https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/seam-examples... (56MB) - configure Seam 2.2.0 and a JBoss Runtime - deploy to JBoss AS server - call the "Test Birt" link JBoss AS 4.2.3 - works correctly JBoss AS 5.1.0 GA - doesn't work due to the problem described on http://www.jboss.org/index.html?module=bb&op=viewtopic&t=156898 JBoss EAP 5.0 You will often get warnings (eap5log1.txt) When calling the "Test Birt" action, you will get either eap5log2.txt or eap5log3.txt. The problem isn't always reproducible. Sometimes it doesn't happen, but rarely. The problem happens due to the way in which JBoss AS 5 initializes the application. BIRT uses org.eclipse.birt.report.listener.ViewerServletContextListener to initialize the BIRT engine (OSGi) when starting the application. If this listener is commented/removed, the problem won't happen. If the BIRT engine hasn't been already initialized, it will be initialized when starting a BIRT servlet so that this listener isn't obliged. Maybe this is even better because the BIRT engine is initialized only when it is called. For now, we can use this as a workaround. However, it seems that there is a problem when the JBoss AS server initializes the application. Another problem is that JBoss AS aggressively logs a warning about missing classes in BIRT internal jars (WEB-INF/platform/plugins/*.jar) when adding a new *xhtml file to the application. This can be solved by adding a line to <JBOSSAS_HOME/server/default/conf/bootstrap/profile.xml: ... <bean name="WebVisitorAttributes" class="org.jboss.system.server.profile.basic.IncludeExcludeVisitorAttributes"> <constructor> <parameter> <set> <value>.war</value> </set> </parameter> <parameter> <set> <value>WEB-INF/classes</value> <value>WEB-INF/lib</value> <value>WEB-INF/platform</value>  </set> </parameter> </constructor> </bean> ... The workaround isn't applicable to JBoss AS 5.1.0.GA. -- 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

6
19
0 / 0

[JBoss JIRA] Created: (JBIDE-8520) Smooks process invalid xml files without validation

by Jiri Peterka (JIRA)

Smooks process invalid xml files without validation --------------------------------------------------- Key: JBIDE-8520 URL: https://issues.jboss.org/browse/JBIDE-8520 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.2.0.Final Environment: JBDS 4.0.0.GA H180, Linux 64 Reporter: Jiri Peterka Assignee: Tom Fennelly 1. Have smooks configuration 2. Create input task (anything) 3. Add apply template with corrupted xml file (missing closing tag or anything else) ERROR: XML is proceeded, nothing happends or xml is partially proceeded Smooks should validate xml before using and report validation errors if any -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-8870) Instance view reports an instance to be running after it just has been stopped

by Libor Zoubek (JIRA)

Instance view reports an instance to be running after it just has been stopped ------------------------------------------------------------------------------- Key: JBIDE-8870 URL: https://issues.jboss.org/browse/JBIDE-8870 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.1.M1 Reporter: Libor Zoubek Assignee: Andre Dietisheim -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
6
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