November 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-6944) Related preferences pages are not populated with imported runtimes.

by Vlado Pakan (JIRA)

Related preferences pages are not populated with imported runtimes. ------------------------------------------------------------------- Key: JBIDE-6944 URL: https://jira.jboss.org/browse/JBIDE-6944 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration, JBossAS Affects Versions: 3.2.0.M2 Environment: JBDS 4.0.0.v201008261621R-H420-M2 Reporter: Vlado Pakan When importing runtimes as described in related jira https://jira.jboss.org/browse/JBIDE-6119. Imported runtimes preference pages are not populated with imported runtimes i. e. when user clicks on the WTP Runtime link and WTP Runtimes were imported there are no imported WTP runtimes displayed in table on WTP Runtime preference page. After preferences dialog is reopened all imported runtimes are correctly displayed on their related Proprties pages -- 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, 4 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-7318) NullPointerException occurreswhile running JUnit test org.jboss.tools.seam.ui.test.ca.SeamELContentAssistTestCase.testSeamELContentAssist

by Victor Rubezhny (JIRA)

NullPointerException occurreswhile running JUnit test org.jboss.tools.seam.ui.test.ca.SeamELContentAssistTestCase.testSeamELContentAssist ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-7318 URL: https://jira.jboss.org/browse/JBIDE-7318 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.Beta1 Reporter: Victor Rubezhny Assignee: Alexey Kazakov Fix For: 3.2.0.Beta2 !ENTRY org.eclipse.wst.sse.ui 2 0 2010-10-12 17:58:46.336 !MESSAGE The ''org.jboss.tools.jst.jsp.proposalComputer.xhtmlEL'' proposal computer from the ''org.jboss.tools.jst.jsp'' plug-in did not complete normally. The extension has thrown a runtime exception. !STACK 0 java.lang.NullPointerException at org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.getProposals(AbstractELCompletionEngine.java:106) at org.jboss.tools.jst.web.kb.PageProcessor.getProposals(PageProcessor.java:164) at org.jboss.tools.jst.web.kb.PageProcessor.getProposals(PageProcessor.java:61) at org.jboss.tools.jst.jsp.contentassist.computers.XmlELCompletionProposalComputer.addELPredicateProposals(XmlELCompletionProposalComputer.java:357) at org.jboss.tools.jst.jsp.contentassist.computers.XmlELCompletionProposalComputer.addAttributeValueProposals(XmlELCompletionProposalComputer.java:143) at org.eclipse.wst.xml.ui.internal.contentassist.AbstractXMLCompletionProposalComputer.computeAttributeValueProposals(AbstractXMLCompletionProposalComputer.java:594) at org.eclipse.wst.xml.ui.internal.contentassist.AbstractXMLCompletionProposalComputer.computeCompletionProposals(AbstractXMLCompletionProposalComputer.java:399) at org.eclipse.wst.xml.ui.internal.contentassist.AbstractXMLCompletionProposalComputer.computeCompletionProposals(AbstractXMLCompletionProposalComputer.java:169) at org.jboss.tools.jst.jsp.contentassist.computers.AbstractXmlCompletionProposalComputer.computeCompletionProposals(AbstractXmlCompletionProposalComputer.java:81) at org.jboss.tools.jst.jsp.contentassist.computers.FaceletsELCompletionProposalComputer.computeCompletionProposals(FaceletsELCompletionProposalComputer.java:85) at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:284) at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:294) at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.collectProposals(StructuredContentAssistProcessor.java:455) at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.computeCompletionProposals(StructuredContentAssistProcessor.java:252) at org.eclipse.wst.sse.ui.internal.contentassist.CompoundContentAssistProcessor.computeCompletionProposals(CompoundContentAssistProcessor.java:126) at org.jboss.tools.jst.jsp.test.TestUtil.collectProposals(TestUtil.java:133) at org.jboss.tools.seam.ui.test.ca.SeamELContentAssistTestCase.testSeamELContentAssist(SeamELContentAssistTestCase.java:574) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:23) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.extensions.TestSetup.run(TestSetup.java:27) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at org.codehaus.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:75) at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:25) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.codehaus.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:21) at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:109) at org.codehaus.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:27) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) -- 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, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4496) Seam builder somtimes creates components without any declarations at all.

by Alexey Kazakov (JIRA)

Seam builder somtimes creates components without any declarations at all. ------------------------------------------------------------------------- Key: JBIDE-4496 URL: https://jira.jboss.org/jira/browse/JBIDE-4496 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.M1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.1.0.M4 Sometimes our tests fails because seam model is not correct. For example we have: @Name("comp1") public class Comp1 {...} Seam builder creates "comp1" component but getJavaDeclaration() return null even if the project is correct and all nedded libs are in classpath. It's hard to reproduce this issue. We need to investigate it and found the resoun of this bug. Looks like thread racing is responsible for that. -- 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, 4 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-7607) Error in coverage report for org.jboss.tools.esb.validator.test.ESBValidatorAllTests

by Denis Golovin (JIRA)

Error in coverage report for org.jboss.tools.esb.validator.test.ESBValidatorAllTests ------------------------------------------------------------------------------------ Key: JBIDE-7607 URL: https://jira.jboss.org/browse/JBIDE-7607 Project: Tools (JBoss Tools) Issue Type: Bug Components: ejb3, testing Affects Versions: 3.2.0.Beta2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.2.0.Beta2 Running org.jboss.tools.esb.validator.test.ESBValidatorAllTests Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.558 sec Results : Tests run: 3, Failures: 0, Errors: 0, Skipped: 0 Could not instrument all bundles as they were not in the bundle context: null Exception in thread "State Saver" java.lang.NullPointerException at org.eclipse.osgi.internal.baseadaptor.BaseStorage.saveBundleDatas(BaseStorage.java:575) at org.eclipse.osgi.internal.baseadaptor.BaseStorage.saveAllData(BaseStorage.java:447) at org.eclipse.osgi.internal.baseadaptor.BaseStorage.access$1(BaseStorage.java:435) at org.eclipse.osgi.internal.baseadaptor.BaseStorage$StateSaver.run(BaseStorage.java:1227) at java.lang.Thread.run(Thread.java:619) [INFO] All tests passed! -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6397) JstJspAllTests fail intermittently on slave vmg18-rhel5-x86_64 for both JBT & JBDS builds

by Nick Boldt (JIRA)

JstJspAllTests fail intermittently on slave vmg18-rhel5-x86_64 for both JBT & JBDS builds ----------------------------------------------------------------------------------------- Key: JBIDE-6397 URL: https://jira.jboss.org/browse/JBIDE-6397 Project: Tools (JBoss Tools) Issue Type: Bug Components: testing Affects Versions: 3.1.1 Reporter: Nick Boldt Not sure why these tests appear here: http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-3.... (soa3-RHEL5-x86) http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-3.... (vmg18-rhel5-x86_64) http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-3.... (conf1-linux) Then disappear (failed? disabled? missing?) for these builds: #90, 96, 98 (vmg18-rhel5-x86_64) And, similarly: http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... (soa6-rhel5-x86_64) http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... (hudson1-rhel5-x86_64) http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... (soa4-rhel5-x86_64) http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... (vmg19-rhel5-x86) But once again disappear (failed? disabled? missing?) for these builds: #102, 103, 111 (on vmg18-rhel5-x86_64) I would blame the slave (bad config? low ram? low disk?) but as we see, this test suite *did* pass once (build #92). -- 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, 4 months

6
11
0 / 0

[JBoss JIRA] Created: (JBIDE-6819) Guvnor repository view can not display snapshots list

by Denny Xu (JIRA)

Guvnor repository view can not display snapshots list ----------------------------------------------------- Key: JBIDE-6819 URL: https://jira.jboss.org/browse/JBIDE-6819 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.2.0.M1 Environment: Drools-Guvnor runtime: drools-guvnor.5.1.0 Reporter: Denny Xu Assignee: Denny Xu create a guvnor repository connection such as : localhost:8080/drools-5.1.0-guvnor/org.drools.guvnor.Guvnor/webdav/, when trying to expand the 'snapshots' tree item, it occurs error : org.xml.sax.SAXParseException: Premature end of file. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:239) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124) at org.guvnor.tools.utils.webdav.StreamProcessingUtils.parseListing(StreamProcessingUtils.java:57) at org.guvnor.tools.utils.webdav.WebDavClient.listDirectory(WebDavClient.java:110) at org.guvnor.tools.views.model.TreeParent.listDirectory(TreeParent.java:122) at org.guvnor.tools.views.model.TreeParent.fetchDeferredChildren(TreeParent.java:97) at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) the error only appear for drools-guvnor.5.1.0. -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-1332) Exporting EAR places jars into ear root dir instead of lib dir when EAR version is 1.4

by Toshiya Kobayashi (JIRA)

Exporting EAR places jars into ear root dir instead of lib dir when EAR version is 1.4 --------------------------------------------------------------------------------------- Key: JBDS-1332 URL: https://jira.jboss.org/browse/JBDS-1332 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Upstream Affects Versions: 3.0.1.GA Reporter: Toshiya Kobayashi In case that EAR version is 1.4, if you place XXX.jar in your project like: [project] + EarContent + lib - XXX.jar + META-INF - application.xml , [Export] -> [Ear file] will generate Ear like: [app.ear] + META-INF - application.xml + lib + XXX.jar In case that EAR version is 5.0, generated Ear will have proper structure: [app.ear] + META-INF - application.xml + lib - XXX.jar JBDS 2.1.1 also generates a proper structure Ear. -- 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, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7700) Add m2eclipse-core 0.12.0 and m2eclipse-wtp 0.11.1 to build

by Snjezana Peco (JIRA)

Add m2eclipse-core 0.12.0 and m2eclipse-wtp 0.11.1 to build ----------------------------------------------------------- Key: JBIDE-7700 URL: https://jira.jboss.org/browse/JBIDE-7700 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Affects Versions: 3.2.0.Beta2 Reporter: Snjezana Peco Assignee: Nick Boldt The m2eclipse team has been released new m2eclipse-core and m2eclipse-wtp versions. The following are update sites: m2eclipse-core 0.12.0 - http://m2eclipse.sonatype.org/sites/m2e/ m2eclipse-wtp 0.11.1 - http://m2eclipse.sonatype.org/sites/m2e-extras/ The JBoss Maven Integration is already compatible with both of them. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-1103) Creating simple Axis Web Service fails running

by Libor Zoubek (JIRA)

Creating simple Axis Web Service fails running ---------------------------------------------- Key: JBDS-1103 URL: https://jira.jboss.org/jira/browse/JBDS-1103 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 3.0.0.CR2 Environment: Sun JDK 1.6.0_17, x86_64, JBDS-H7-CR3, Jboss-AS 5.1-GA Reporter: Libor Zoubek Priority: Critical It seems like JDBS wrongly creates axis-based web service. In comparsion to Eclipse 3.5 WTP, where everything goes OK as well as deploying and running od jboss-as 5.1 Can be reproduced by following this tutorial http://www.eclipse.org/webtools/jst/components/ws/1.5/tutorials/BottomUpW... Notes: Eclipse 3.5 WTP creating, deploying, running - OK Opening workspace created by Eclipse 3.5 WTP by JBDS and deploying+running Axis WS - OK See attached log and workspace -- 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, 4 months

6
30
0 / 0

[JBoss JIRA] Created: (JBDS-1356) Multiple basic functions in JBDS generate log errors

by Len DiMaggio (JIRA)

Multiple basic functions in JBDS generate log errors ---------------------------------------------------- Key: JBDS-1356 URL: https://jira.jboss.org/browse/JBDS-1356 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 4.0.0.Beta1 Environment: Version: 4.0.0.Beta1 Build id: v201010052359R Build date: 201010060016 Reporter: Len DiMaggio Attachments: delete_project.log, deploy_esb.log, import_helloworld.log See the attached log files - the file names represent the functions performed - there does not seem to be functional/operational impacts - but the log messages may be alarming to users. -- 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, 4 months

4
13
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 2010