June 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6533) workingset test failures

by Nick Boldt (JIRA)

workingset test failures ------------------------ Key: JBIDE-6533 URL: https://jira.jboss.org/browse/JBIDE-6533 Project: Tools (JBoss Tools) Issue Type: Sub-task Affects Versions: 3.2.0.M1 Reporter: Nick Boldt Assignee: Max Rydahl Andersen From: http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-3.2.0.M1/... Tests run: 3, FAILUREs: 2, Errors: 0, Skipped: 0, Time elapsed: 0.04 sec <<< FAILURE! testSingleMatch(org.jboss.tools.workingset.core.test.GroupingTest) Time elapsed: 0.004 sec <<< FAILURE! junit.framework.ComparisonFAILURE: null expected:<[eclipse]> but was:<[jdt]> at junit.framework.Assert.assertEquals(Assert.java:81) at junit.framework.Assert.assertEquals(Assert.java:87) at org.jboss.tools.workingset.core.test.GroupingTest.testSingleMatch(GroupingTest.java:49) at junit.framework.TestCase.runTest(TestCase.java:168) -- testMultiMatch(org.jboss.tools.workingset.core.test.GroupingTest) Time elapsed: 0.001 sec <<< FAILURE! junit.framework.ComparisonFAILURE: null expected:<[eclipse]> but was:<[jdt]> at junit.framework.Assert.assertEquals(Assert.java:81) at junit.framework.Assert.assertEquals(Assert.java:87) at org.jboss.tools.workingset.core.test.GroupingTest.testMultiMatch(GroupingTest.java:58) at junit.framework.TestCase.runTest(TestCase.java:168) -- -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6551) The method compareElements(VpeController, Document, String, String) from the type ComponentContentTest is not visible in vpe/jsf/test/jbide/JBIDE4179Test.java

by Nick Boldt (JIRA)

The method compareElements(VpeController, Document, String, String) from the type ComponentContentTest is not visible in vpe/jsf/test/jbide/JBIDE4179Test.java -------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-6551 URL: https://jira.jboss.org/browse/JBIDE-6551 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.2.0.M1 Reporter: Nick Boldt Assignee: Maxim Areshkau [java] [javac] 44. ERROR in /qa/services/hudson/hudson_workspace/workspace/jbosstools-nightly-3.2/jbds-build/eclipse/plugins/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE4179Test.java (at line 84) [java] [javac] compareElements(vpeController, xmlTestDocument, id, id); [java] [javac] ^^^^^^^^^^^^^^^ [java] [javac] The method compareElements(VpeController, Document, String, String) from the type ComponentContentTest is not visible http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6543) Add line numbers to error messages of tests of VPE Templates

by Yahor Radtsevich (JIRA)

Add line numbers to error messages of tests of VPE Templates ------------------------------------------------------------ Key: JBIDE-6543 URL: https://jira.jboss.org/browse/JBIDE-6543 Project: Tools (JBoss Tools) Issue Type: Task Components: Visual Page Editor core, Visual Page Editor Templates Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.2.0.M1 Now VPE templates tests framework prints error messages like [Child of node "DIV" is "null", but should be "H1"] without line numbers where error appears. It would much faster to find the reason of the errors if the framework prints something like [line 56: Child of node "DIV" is "null", but should be "H1"]. -- 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, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6549) New Interceptor Binding Type wizard should suggest only @Target({TYPE, METHOD}) or @Target(TYPE)

by Alexey Kazakov (JIRA)

New Interceptor Binding Type wizard should suggest only @Target({TYPE, METHOD}) or @Target(TYPE) ------------------------------------------------------------------------------------------------ Key: JBIDE-6549 URL: https://jira.jboss.org/browse/JBIDE-6549 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.M1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.0.M2 See the spec. (9.1): An interceptor binding type is a Java annotation defined as @Target({TYPE, METHOD}) or @Target(TYPE) and @Retention(RUNTIME). -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-6046) ESB Editor for JMS Router missing fields or has wrong field name

by Brian Fitzpatrick (JIRA)

ESB Editor for JMS Router missing fields or has wrong field name ---------------------------------------------------------------- Key: JBIDE-6046 URL: https://jira.jboss.org/jira/browse/JBIDE-6046 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Fix For: 3.2.next, 3.1.1 This came from JBDS-1156 The JMS Router Action does not have a field on the screen for JNDI Name: Need to add via source view: <property name="jndiName" value="queue/quickstart_jms_router_routeTo"/> The credential name is misspelled, so need to add: <property name="security-credential" value="guest"/> -- 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, 9 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-5916) Wrong Compiler Compliance Level set when creating new ESB Project

by Vlado Pakan (JIRA)

Wrong Compiler Compliance Level set when creating new ESB Project ------------------------------------------------------------------ Key: JBIDE-5916 URL: https://jira.jboss.org/jira/browse/JBIDE-5916 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Environment: JBDS 3.0.0v201002190339M-H173-CR2 Java Sun JDK 1.6.0_16-b01 JBoss [SOA] 5.0.0.GA_SOA (build: SVNTag=5.0.0.GA_SOA date=201002151345) Reporter: Vlado Pakan Fix For: 3.1.0.CR2 When new ESB Project is created (File > New > Others > ESB Project) this project has set Compiler Compliance Level to 1.5 (Project > Properties > Java Compiler) even when only Java JDK 1.6 Runtime is specified within workspace. Then when user adds new ESB Action to this project (File > New > Others > ESB Action) it generates new class with this content (JBoss ESB Runtime jas to be added to project classpath): import org.jboss.soa.esb.actions.AbstractActionPipelineProcessor; import org.jboss.soa.esb.helpers.ConfigTree; import org.jboss.soa.esb.actions.ActionProcessingException; import org.jboss.soa.esb.message.Message; public class EsbAction extends AbstractActionPipelineProcessor { protected ConfigTree _config; public EsbAction(ConfigTree config) { _config = config; } @Override public Message process(Message message) throws ActionProcessingException { //ADD CUSTOM ACTION CODE HERE return message; } } And compiler is complaining about @Override annotation on method process(Message) displaying this error: The method process(Message) of type EsbAction must override a superclass method Either when Compiler Compliance level is set to 1.6 or Project Facets Java version is set to 6.0 (Project Properties > Project Facets > Java) error disappear. I think it should work in the way that when user creates new EBS Action it should be created without errors so Compiler Compliance Level or Project Facets Java should be set properly. -- 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, 9 months

6
41
0 / 0

[JBoss JIRA] Created: (JBIDE-6497) [tester] wrong namespace is used in generated soap body for wsdl importing another wsdl

by Lukas Jungmann (JIRA)

[tester] wrong namespace is used in generated soap body for wsdl importing another wsdl --------------------------------------------------------------------------------------- Key: JBIDE-6497 URL: https://jira.jboss.org/browse/JBIDE-6497 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M1 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -deploy attached project containing ws from wsdl -open tester view -open "Get from WSDL..." dialog, fill in the WSDL URI, keep defaults and press ok -invoke the service => response says: Cannot find dispatch method for {http://webservices.www.ecubicle.net/}GetSearchResults problem is that generated SOAP request contains: <GetSearchResults xmlns = "http://webservices.www.ecubicle.net/"> but it should contain: <GetSearchResults xmlns = "http://www.ecubicle.net/webservices"> the cause of the problem seems to be the fact that target namespace in concrete WSDL is different from the one defined in imported/abstract WSDL -- 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, 9 months

2
20
0 / 0

[JBoss JIRA] Created: (JBIDE-6532) portlet test failures

by Nick Boldt (JIRA)

portlet test failures --------------------- Key: JBIDE-6532 URL: https://jira.jboss.org/browse/JBIDE-6532 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Portal/GateIn Affects Versions: 3.2.0.M1 Reporter: Nick Boldt Assignee: Snjezana Peco From: http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-3.2.0.M1/... Tests run: 2, FAILUREs: 0, Errors: 1, Skipped: 0, Time elapsed: 0.054 sec <<< FAILURE! testOrgJbossPortletUiPluginIsActivated(org.jboss.tools.portlet.core.test.PortletPluginsLoadTest) Time elapsed: 0.004 sec <<< ERROR! java.lang.NullPointerException at org.jboss.tools.tests.AbstractPluginsLoadTest.assertPluginsResolved(AbstractPluginsLoadTest.java:85) at org.jboss.tools.tests.AbstractPluginsLoadTest.assertPluginResolved(AbstractPluginsLoadTest.java:92) at org.jboss.tools.portlet.core.test.PortletPluginsLoadTest.testOrgJbossPortletUiPluginIsActivated(PortletPluginsLoadTest.java:13) -- -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-943) Does not run on Mac after installing with the attached error

by Jim Tyrrell (JIRA)

Does not run on Mac after installing with the attached error ------------------------------------------------------------ Key: JBDS-943 URL: https://jira.jboss.org/jira/browse/JBDS-943 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4 Environment: Mac Snow Leopard Macintosh-75:Applications jimtyrrell$ java -version java version "1.6.0_15" Java(TM) SE Runtime Environment (build 1.6.0_15-b03-219) Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02-90, mixed mode) Reporter: Jim Tyrrell Attachments: Screen shot 2009-11-10 at 7.57.16 PM.png Clicking on JBoss Developer Studio.app results in the attached error. -- 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, 9 months

5
15
0 / 0

[JBoss JIRA] Created: (JBDS-875) BRMS pluging, deleting file not working

by Jehudi Castro (JIRA)

BRMS pluging, deleting file not working --------------------------------------- Key: JBDS-875 URL: https://jira.jboss.org/jira/browse/JBDS-875 Project: JBoss Developer Studio Issue Type: Bug Reporter: Jehudi Castro see GUVNOR-459 -- 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, 9 months

4
14
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 June 2010