July 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6749) org.guvnor.tools.Activator adds ResourceChangeListener, but doesn't remove it

by Snjezana Peco (JIRA)

org.guvnor.tools.Activator adds ResourceChangeListener, but doesn't remove it ----------------------------------------------------------------------------- Key: JBIDE-6749 URL: https://jira.jboss.org/browse/JBIDE-6749 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.2.0.M1 Reporter: Snjezana Peco Assignee: Kris Verlaenen The following exception happens sometimes when exiting Eclipse (when running tests that remove projects on exit, for instance): org.eclipse.swt.SWTException: Device is disposed at org.eclipse.swt.SWT.error(SWT.java:4083) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.SWT.error(SWT.java:3969) at org.eclipse.swt.widgets.Display.error(Display.java:1249) at org.eclipse.swt.widgets.Display.asyncExec(Display.java:700) at org.guvnor.tools.ResourceChangeListener.deleteResources(Unknown Source) at org.guvnor.tools.ResourceChangeListener.resourceChanged(Unknown Source) at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:291) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:327) at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1181) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:45) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) The solution would be to add getWorkspace().removeResourceChangeListener(rcListener) to the Activator.stop() method. -- 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, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6250) Cannot create ws from wsdl if there are more ports in service's element in wsdl

by Lukas Jungmann (JIRA)

Cannot create ws from wsdl if there are more ports in service's element in wsdl ------------------------------------------------------------------------------- Key: JBIDE-6250 URL: https://jira.jboss.org/jira/browse/JBIDE-6250 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.1.0.GA Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -have a dynamic web project -open new web service wizard -set the wizard: 1st step: ws type: top-down service definition: http://www.webservicex.net/BibleWebservice.asmx?wsdl (or use local copy of this wsdl) ws runtime: JBossWS 2nd step: leave default values hit finish => org.eclipse.core.runtime.CoreException: Failed to Generate Web Service code, please check the log for more details at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.getCompilationUnitForInterface(ImplementationClassCreationCommand.java:449) at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.generateImplClass(ImplementationClassCreationCommand.java:133) at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.execute(ImplementationClassCreationCommand.java:97) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419) ... -- 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, 8 months

4
23
0 / 0

[JBoss JIRA] Created: (JBIDE-6755) [restwizard] "Dynamic Web Project Name" label can be shortened

by Lukas Jungmann (JIRA)

[restwizard] "Dynamic Web Project Name" label can be shortened -------------------------------------------------------------- Key: JBIDE-6755 URL: https://jira.jboss.org/browse/JBIDE-6755 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M2 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick Priority: Minor -open Sample RESTful service wizard => "Dynamic Web Project Name" label can be shortened to "Dynamic Web Project" -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6106) Rewrite Web Service wizard independent on WTP

by Libor Zoubek (JIRA)

Rewrite Web Service wizard independent on WTP --------------------------------------------- Key: JBIDE-6106 URL: https://jira.jboss.org/jira/browse/JBIDE-6106 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Libor Zoubek Fix For: 3.2.next I think wizards for creating web services provided by WTP are bad solution and our way of extending them brings lots of problems we have to deal with. I suggest to write new wizards for creating web service. As it happened in the case of 'Create a Sample Web Service' which is fully under our control and is pretty simple and works well. New wizards can of course reuse code from 'Create a Sample Web Service' since there are many same or similar steps. -- 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, 8 months

4
18
0 / 0

[JBoss JIRA] Created: (JBDS-1059) ESB Editor usability

by prakash aradhya (JIRA)

ESB Editor usability --------------------- Key: JBDS-1059 URL: https://jira.jboss.org/jira/browse/JBDS-1059 Project: JBoss Developer Studio Issue Type: Feature Request Components: SOA Platform Affects Versions: 3.0.0.CR2 Environment: Mac / Windows Reporter: prakash aradhya Fix For: 3.0.0.CR2 ESB Editor - The editor looks lot better than before. There are many minor usability things we can add to make to better. Here are some of them. - Icons for each item on the left side tree instead of folders. - Add Tree view in the navigation bar for the .esb file on the left side for the file similar to the one in the editor. - For listeners - Add button pops up a list of menu items - add icons for each of them. - Also, it will be nice if we can pop up a window (editor) that offers all those options and navigator through. -- 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, 8 months

5
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6411) [tester] Add ability to peruse JBoss UDDI v3 repository to pick WS to test

by Brian Fitzpatrick (JIRA)

[tester] Add ability to peruse JBoss UDDI v3 repository to pick WS to test -------------------------------------------------------------------------- Key: JBIDE-6411 URL: https://jira.jboss.org/browse/JBIDE-6411 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.2.next Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.2.next Now that we have the ability to poke at a WSDL file and pick out enough details to test a WS we should offer a way to browse the UDDI v3 repository in some JBoss runtimes to allow someone to pick from the list of published services to test. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-6110) Create ESB test tool

by Vlado Pakan (JIRA)

Create ESB test tool -------------------- Key: JBIDE-6110 URL: https://jira.jboss.org/jira/browse/JBIDE-6110 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.1.0.GA Reporter: Vlado Pakan Fix For: 3.2.next Create ESB tool which will be able to test ESB project deployed to server. It should allow user to send/receive messages to/from ESB service/queue within JBDS to give user faster test developed ESB project -- 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, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6597) Seam tools are taking big amount of the memory

by Adrian Mitev (JIRA)

Seam tools are taking big amount of the memory ---------------------------------------------- Key: JBIDE-6597 URL: https://jira.jboss.org/browse/JBIDE-6597 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Reporter: Adrian Mitev Assignee: Alexey Kazakov Attachments: 2010-07-12_1044.swf Hello! I have a relatively big project: - 5000 classes ~ 150 seam components - 520.xhtml files - 20 pages.xml files When i open a resource related to seam (like pages.xml, components.xml). The IDE loads the seam plugins, does some computations and takes most of my memory. I'm attaching a short video to see what happens and some useful information. -- 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, 8 months

3
15
0 / 0

[JBoss JIRA] Created: (JBIDE-6466) Several class loader related unsafe places in JBoss Tools

by Vitali Yemialyanchyk (JIRA)

Several class loader related unsafe places in JBoss Tools --------------------------------------------------------- Key: JBIDE-6466 URL: https://jira.jboss.org/browse/JBIDE-6466 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Archives, bpel, jbpm, jmx Affects Versions: 3.1.1 Reporter: Vitali Yemialyanchyk Assignee: Max Rydahl Andersen I find several unsafe places which are related with Thread.currentThread().getContextClassLoader() and Thread.currentThread().setContextClassLoader(). These places in code could have dramatic outcome during JBoss Tools normal work. Especially Hibernate Tools depends on it - and this result will be visible ONLY in JPA confoguration. Here are code places: 1) \jbosstools\trunk\jbpm\plugins\org.jboss.tools.flow.jpdl4.multipage\src\org\jboss\tools\flow\jpdl4\multipage\validator\Jpdl4Validator.java 2) \jbosstools\trunk\archives\plugins\org.jboss.ide.eclipse.archives.core\src\main\org\jboss\ide\eclipse\archives\core\model\internal\xb\XMLBinding.java 1 and 2 - are dangerous cause in case of execution exception - here there are no restore of Thread.currentThread() - ContextClassLoader; 3) \jbosstools\trunk\as\plugins\org.jboss.ide.eclipse.as.core\jbosscore\org\jboss\ide\eclipse\as\core\extensions\jmx\JMXSafeRunner.java 3 - here also Hibernate Tools dangerous place in finally block - if we get exception in JMXClassLoaderRepository.getDefault().removeConcerned(s, r); 4) \jbosstools\trunk\common\plugins\org.jboss.tools.common\src\org\jboss\tools\common\xml\SAXValidator.java 4 - here also Hibernate Tools dangerous place in finally block - if we get exception in ErrorHandlerImpl h = new ErrorHandlerImpl(); 5) \jbosstools\trunk\bpel\plugins\org.eclipse.bpel.ui\src\org\eclipse\bpel\ui\util\BPELEditorUtil.java - here is potential unsafe code commented; 6) \jbosstools\trunk\smooks\plugins\org.jboss.tools.smooks.ui\src\org\jboss\tools\smooks\edimap\editor\EDIMapFormPage.java - here is potential unsafe code commented; -- 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, 8 months

4
3
0 / 0

[JBoss JIRA] Updated: (JBIDE-6464) Running a SeamTest when multiple projects are open in the Eclipse workspace fails

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/browse/JBIDE-6464?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen updated JBIDE-6464: --------------------------------------- Assignee: Alexey Kazakov Fix Version/s: 3.2.x Alexey, any idea of what is going on ? > Running a SeamTest when multiple projects are open in the Eclipse workspace fails > --------------------------------------------------------------------------------- > > Key: JBIDE-6464 > URL: https://jira.jboss.org/browse/JBIDE-6464 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam > Environment: XP, JBoss 5.1.0 GA, Seam 2.2.0 GA, JBoss Tools 3.1.0 GA > Reporter: Shu-Wei Tan > Assignee: Alexey Kazakov > Fix For: 3.2.x > > > My eclipse workspace contains 2 JBoss Tools generated Seam projects: > - Project1.war > - Project1.ear > - Project1.ejb > - Project1.test > - Project2.war > - Project2.ear > - Project2.ejb > - Project2.test > Project2.ear depends on both Project1.ejb and Project2.ejb. > Project2.test contains a SeamTest test case. When running that test case, I get an exception saying TimerServiceDispatcher already deployed. This is because jboss-seam.jar seems to be picked up twice by the bootstrap process, once from Project1.ear and once from Project2.ear. > If I close the Project1.ear project in Eclipse then rerun the test, it works. > Here's the exception (the actual project name is different from my simplified example above): > ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Real: name=vfsjar:file:/E:/gbahn/SeamProjects/General/General-ear/EarContent/jboss-seam.jar!/ state=PostClassLoader mode=Manual requiredState=Real > org.jboss.deployers.spi.DeploymentException: Error deploying jboss-seam.jar: Error creating ejb container TimerServiceDispatcher: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered > at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:158) > at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:88) > at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalDeploy(AbstractVFSRealDeployer.java:45) > at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) > at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853) > at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794) > at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) > at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) > at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498) > at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506) > at org.jboss.embedded.DeploymentGroup.process(DeploymentGroup.java:127) > at org.jboss.embedded.Bootstrap.deployResourceBases(Bootstrap.java:289) > at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:19) > at org.jboss.seam.mock.AbstractSeamTest.startJbossEmbeddedIfNecessary(AbstractSeamTest.java:1024) > at org.jboss.seam.mock.AbstractSeamTest.startSeam(AbstractSeamTest.java:915) > at org.jboss.seam.mock.SeamTest.startSeam(SeamTest.java:58) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:607) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:417) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:154) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:88) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:284) > at org.testng.SuiteRunner.run(SuiteRunner.java:204) > at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:877) > at org.testng.TestNG.runSuitesLocally(TestNG.java:842) > at org.testng.TestNG.run(TestNG.java:751) > at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73) > at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:124) > Caused by: org.jboss.deployers.spi.DeploymentException: Error creating ejb container TimerServiceDispatcher: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered > at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:540) > at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:486) > at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:468) > at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:434) > at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:376) > at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:145) > ... 36 more > Caused by: java.lang.IllegalStateException: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered > at org.jboss.ejb3.Ejb3Registry.register(Ejb3Registry.java:128) > at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:536) > ... 41 more -- 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, 8 months

1
0
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 July 2010