August 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6586) VPE JUnits failed: child of node X must be Y

by Yahor Radtsevich (JIRA)

VPE JUnits failed: child of node X must be Y -------------------------------------------- Key: JBIDE-6586 URL: https://jira.jboss.org/browse/JBIDE-6586 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core, Visual Page Editor Templates Affects Versions: 3.2.0.M1 Reporter: Yahor Radtsevich Assignee: Maxim Areshkau Fix For: 3.2.0.M1 With XULRunner 1.9.2 the following tests are being failed: -------------------------------------------------------------------------------- junit.framework.AssertionFailedError: D:\doc\prj\jboss\wrksps\junit-workspace\jsf2test\WebContent\pages\JBIDE\5908\welcome.xhtml.xml[/tests/test/DIV/DIV/DIV[2]/DIV/DIV/DIV/DIV[1]/H1]: Child of node "DIV" is "null", but should be "H1" at junit.framework.Assert.fail(Assert.java:47) at org.jboss.tools.vpe.ui.test.ComponentContentTest.compareContent(ComponentContentTest.java:108) at org.jboss.tools.vpe.ui.test.ComponentContentTest.performContentTest(ComponentContentTest.java:86) at org.jboss.tools.jsf.vpe.jsf.test.jbide.RenderFacetAndInsertChildrenTest.testRenderFacetAndInsertChildren(RenderFacetAndInsertChildrenTest.java:28) ... -------------------------------------------------------------------------------- junit.framework.AssertionFailedError: D:\doc\prj\jboss\wrksps\junit-workspace\jsf2test\WebContent\pages\components\head2.xhtml.xml[/tests/test/div/h1]: name of tag is "BR"but must be "h1" at junit.framework.Assert.fail(Assert.java:47) at org.jboss.tools.vpe.ui.test.ComponentContentTest.compareContent(ComponentContentTest.java:108) at org.jboss.tools.vpe.ui.test.ComponentContentTest.performContentTest(ComponentContentTest.java:86) at org.jboss.tools.jsf.vpe.jsf.test.Jsf20ComponentContentTest.testHead2(Jsf20ComponentContentTest.java:74) ... -------------------------------------------------------------------------------- junit.framework.AssertionFailedError: D:\doc\prj\jboss\wrksps\junit-workspace\jsf2test\WebContent\pages\JBIDE\5015\login.xhtml.xml[/tests/test/FORM/DIV[1]/DIV/DIV[1]/H1]: name of tag is "BR"but must be "H1" at junit.framework.Assert.fail(Assert.java:47) at org.jboss.tools.vpe.ui.test.ComponentContentTest.compareContent(ComponentContentTest.java:108) at org.jboss.tools.vpe.ui.test.ComponentContentTest.performContentTest(ComponentContentTest.java:86) at org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE2550Test.testForJSF2CustomTags(JBIDE2550Test.java:35) ... -------------------------------------------------------------------------------- -- 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

15 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5066) JBIDE1105Test failed sometimes with following exception

by Maxim Areshkau (JIRA)

JBIDE1105Test failed sometimes with following exception ------------------------------------------------------- Key: JBIDE-5066 URL: https://jira.jboss.org/jira/browse/JBIDE-5066 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Reporter: Maxim Areshkau Assignee: Yura Zhishko Fix For: 3.1.0.CR1 JBIDE1105Test failed rundomly with BadLocationException -- 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

15 years, 7 months

4
10
0 / 0

[JBoss JIRA] Created: (JBDS-1167) SOA-P5 , Security , and the ESB XML in JBDS 3.0

by Gary Lamperillo (JIRA)

SOA-P5 , Security , and the ESB XML in JBDS 3.0 ----------------------------------------------- Key: JBDS-1167 URL: https://jira.jboss.org/jira/browse/JBDS-1167 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Affects Versions: 3.0.0.CR1 Reporter: Gary Lamperillo Using security setting within an ESB Service definition requires a Security element to be added. An example of this is the PicketLink sample, security_saml. When bringing this over to a JBDS project and editing the esb.xml, the only way to add the security element is to add it in the source view. Here is an example of the xml section to be added to a service: <service category="SamlSecurityQuickstart" description="This service demonstrates how a service can be configured to issue and validate a security token" invmScope="GLOBAL" name="issueTokenService"> <security callbackHandler="org.jboss.soa.esb.services.security.auth.login.JBossSTSIssueCallbackHandler" moduleName="saml-issue-token">  <property name="org.jboss.soa.esb.services.security.contextTimeout" value="0"/> </security> <listeners> ...... The tooling should have "Security Settings" as an option for services. Also, Soap Proxy should have the addition of a "Content Type Settings" as an option to allow compatibility with endpoints. -- 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

15 years, 7 months

5
14
0 / 0

[JBoss JIRA] Created: (JBIDE-6615) [ESB Editor] Support new Camel Router functionality in ESB 4.9

by Brian Fitzpatrick (JIRA)

[ESB Editor] Support new Camel Router functionality in ESB 4.9 -------------------------------------------------------------- Key: JBIDE-6615 URL: https://jira.jboss.org/browse/JBIDE-6615 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Affects Versions: 3.2.x Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.2.x In ESB 4.9, we have a new Camel Gateway to support in the ESB Editor. Some details from David Ward: In addition to the 1st article explaining the CamelGateway: http://community.jboss.org/wiki/CamelGateway I have just introduced a new related article which explains how to add non-core Camel Components to gain further functionality: http://community.jboss.org/wiki/CamelGatewayUsingnon-coreComponents -- 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

15 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6303) Edit Action Dialog doesn't allow to select methods with non-void return type.

by Alexey Kazakov (JIRA)

Edit Action Dialog doesn't allow to select methods with non-void return type. ----------------------------------------------------------------------------- Key: JBIDE-6303 URL: https://jira.jboss.org/browse/JBIDE-6303 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.0.GA Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.next 1. Create JSF project. Use any KickStart template from New JSF Project wizard. 2. Add following method to the managed bean: public String checkGuess() { ... } 3. Open inputname.xhtml/jsp. 4. Add <h:commandButton action=""/> 5. Select this component in visual part, right click. Select <h:commandButton> Attributes. 6. Select action attribute. 7. Select its value and click "..." button. 8. There is no checkGuess method among available Managed Beans methods. -- 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

15 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5677) Project Facets don't support JSF 2 (only JSF 1.2 and 1.1)

by Juergen Zimmermann (JIRA)

Project Facets don't support JSF 2 (only JSF 1.2 and 1.1) --------------------------------------------------------- Key: JBIDE-5677 URL: https://jira.jboss.org/jira/browse/JBIDE-5677 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.0.CR1 Reporter: Juergen Zimmermann Attachments: screenshot-project-facets.jpg When JSF capabilities are added to a web project I can only choose between JSF 1.2 (= default) and 1.1. There is no option for JSF 2. A screenshot will be provided. -- 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

15 years, 7 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6540) Adding JSF Capabilities to existing project fails

by Viacheslav Kabanovich (JIRA)

Adding JSF Capabilities to existing project fails ------------------------------------------------- Key: JBIDE-6540 URL: https://jira.jboss.org/browse/JBIDE-6540 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.M1 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.2.0.M2 This problem appeared after migration to Eclipse 3.6. Create new Java project and add to it folder WebContent/WEB-INF with web.xml and faces-config.xml. Try Configure->Add JSF Capabilities. Wizard finishes with errors in log and corrupted project settings (empty or missing files in .settings folder). -- 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

15 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6563) NLS unused message in the org.jboss.tools.jsf.ui plugin

by Snjezana Peco (JIRA)

NLS unused message in the org.jboss.tools.jsf.ui plugin ------------------------------------------------------- Key: JBIDE-6563 URL: https://jira.jboss.org/browse/JBIDE-6563 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.x Reporter: Snjezana Peco Assignee: Alexey Kazakov If you start JBoss Tools trunk in the debug mode, you will get the following messages: !ENTRY org.eclipse.osgi 2 1 2010-06-30 22:56:55.265 !MESSAGE NLS unused message: UI_WIZARD_XHTML_NEW_TITLE in: org.jboss.tools.jsf.ui.messages !ENTRY org.eclipse.osgi 2 1 2010-06-30 22:56:55.265 !MESSAGE NLS unused message: UI_WIZARD_XHTML_NEW_Description in: org.jboss.tools.jsf.ui.messages !ENTRY org.eclipse.osgi 2 1 2010-06-30 22:56:55.265 !MESSAGE NLS unused message: NewXHTMLTemplatesWizardPage_0 in: org.jboss.tools.jsf.ui.messages !ENTRY org.eclipse.osgi 2 1 2010-06-30 22:56:55.265InitFunctions took: 47ms !MESSAGE NLS unused message: NewXHTMLTemplatesWizardPage_1 in: org.jboss.tools.jsf.ui.messages !ENTRY org.eclipse.osgi 2 1 2010-06-30 22:56:57.062 !MESSAGE NLS unused message: NewXHTMLTemplatesWizardPage_2 in: org.jboss.tools.jsf.ui.messages !ENTRY org.eclipse.osgi 2 1 2010-06-30 22:56:57.062 !MESSAGE NLS unused message: NewXHTMLTemplatesWizardPage_3 in: org.jboss.tools.jsf.ui.messages !ENTRY org.eclipse.osgi 2 1 2010-06-30 22:56:57.062 !MESSAGE NLS unused message: NewXHTMLTemplatesWizardPage_4 in: org.jboss.tools.jsf.ui.messages !ENTRY org.eclipse.osgi 2 1 2010-06-30 22:56:57.062 !MESSAGE NLS unused message: NewXHTMLTemplatesWizardPage_5 in: org.jboss.tools.jsf.ui.messages !ENTRY org.eclipse.osgi 2 1 2010-06-30 22:56:57.062 !MESSAGE NLS unused message: NewXHTMLTemplatesWizardPage_6 in: org.jboss.tools.jsf.ui.messages !ENTRY org.eclipse.osgi 2 1 2010-06-30 22:56:57.062 !MESSAGE NLS unused message: NewXHTMLTemplatesWizardPage_7 in: org.jboss.tools.jsf.ui.messages !ENTRY org.eclipse.osgi 2 1 2010-06-30 22:56:57.062 !MESSAGE NLS missing message: EL_REFACTOR_RENAME_HANDLER_ERROR in: org.jboss.tools.jsf.ui.messages -- 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

15 years, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6453) Text caret in source part disapears after text selection in VPE

by Yahor Radtsevich (JIRA)

Text caret in source part disapears after text selection in VPE --------------------------------------------------------------- Key: JBIDE-6453 URL: https://jira.jboss.org/browse/JBIDE-6453 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.2.0.M1 Environment: Windows XP SP3/Vista Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.2.0.M1 STEPS TO REPRODUCE (also see demo-1.swf): 1. Create a HTML page and open it in VPE. 2. Type any text in the page. 3. Select the text in VPE. 4. Click on the text in source editor. RESULT: Caret is disappeared. -- 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

15 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6706) StackOverflowError in KB Project Validator

by Adrian Mitev (JIRA)

StackOverflowError in KB Project Validator ------------------------------------------ Key: JBIDE-6706 URL: https://jira.jboss.org/browse/JBIDE-6706 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.M1 Reporter: Adrian Mitev Assignee: Alexey Kazakov Attachments: jbosstools-diagnostics-20100726171259.zip It happens when i clean-up the project. See the attached file for more infom. -- 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

15 years, 7 months

4
9
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 August 2010