July 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6445) OpenOn for Injection points hands Eclipse for a while.

by Alexey Kazakov (JIRA)

OpenOn for Injection points hands Eclipse for a while. ------------------------------------------------------ Key: JBIDE-6445 URL: https://jira.jboss.org/browse/JBIDE-6445 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.next Reporter: Alexey Kazakov Assignee: Daniel Azarov Priority: Critical Fix For: 3.2.next 1. Create a big CDI project (you can take our tests project from *.cdi.core.test plug-in). 2. Open any java fle with @Inject 3. Try to Ctrl+Click on @Inject. Works fine. 4. Restart Eclipse. 5. Ctrl+Click on the same @Inject. Eclipse hangs for a while (on my PC with the project from *.cdi.core.test, it takes about a minute) until builders complete working. And only after that you will see OpenOn dialog. Maybe it's better to show the dialog always and do a real search only if user click on our hyperlink? Or is it possible to show progress dialog while the project is being built? How Java OpenOns work? -- 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
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6589) [Tester] Can't actually cancel a web service invocation

by Brian Fitzpatrick (JIRA)

[Tester] Can't actually cancel a web service invocation ------------------------------------------------------- Key: JBIDE-6589 URL: https://jira.jboss.org/browse/JBIDE-6589 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M1 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.2.0.M2 Though I've wired up the JAX-WS and JAX-RS test invocation to the Jobs API, it never really worked to actually cancel a request. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6513) @Inject Instance<BeanType> should be resolve to beans with BeanType bean type.

by Alexey Kazakov (JIRA)

@Inject Instance<BeanType> should be resolve to beans with BeanType bean type. ------------------------------------------------------------------------------ Key: JBIDE-6513 URL: https://jira.jboss.org/browse/JBIDE-6513 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 5.6. Programmatic lookup. All the tests in org.jboss.tools.cdi.core.test.tck.DynamicLookupTest should pass. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6548) New CDI Stereotype/Qualifier/Scope/... wizards seem to invoke full build for the project.

by Alexey Kazakov (JIRA)

New CDI Stereotype/Qualifier/Scope/... wizards seem to invoke full build for the project. ----------------------------------------------------------------------------------------- Key: JBIDE-6548 URL: https://jira.jboss.org/browse/JBIDE-6548 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.M1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Priority: Critical Fix For: 3.2.0.M2 1. Create any CDI project. Build it. 2. Close the Eclipse. 3. Re-open it. 4. New->CDI->Stereotype. Press Next 5. Eclipse hangs while the project is building (full build!). Why we need a full build? Why we don't show any progress view if we need to prepare CDI model for the wizard before run it and this process is long? -- 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
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6635) Open Injected Class ignores decorators

by Pete Muir (JIRA)

Open Injected Class ignores decorators -------------------------------------- Key: JBIDE-6635 URL: https://jira.jboss.org/browse/JBIDE-6635 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Reporter: Pete Muir Assignee: Max Rydahl Andersen When I choose "Open Injected Class" on a class which has a decorator, CDI tools ignores the decorator and takes me to the bean. Probably need to add more option here when there are interceptors or decorators - "Open Injected Class" "Open Decorator XXX" "Open Decorator YYY" "Open Interceptor ZZZ" -- 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
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6638) Open Injected Class isn't aware of @Any

by Pete Muir (JIRA)

Open Injected Class isn't aware of @Any --------------------------------------- Key: JBIDE-6638 URL: https://jira.jboss.org/browse/JBIDE-6638 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Reporter: Pete Muir Assignee: Max Rydahl Andersen If you have an injection point @Inject @Any Foo foo; it does resolve to a bean @Bar class Foo {} as @Any is an implicit qualifier -- 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

5
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6481) [Web Service Wizard] Issues creating web service project for simple WSDL

by Brian Fitzpatrick (JIRA)

[Web Service Wizard] Issues creating web service project for simple WSDL ------------------------------------------------------------------------ Key: JBIDE-6481 URL: https://jira.jboss.org/browse/JBIDE-6481 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.x Reporter: Brian Fitzpatrick Assignee: Feng Qian Priority: Critical Fix For: 3.2.x Ran into an issue while doing some testing. The simple WSDL at http://www.ecubicle.net/gsearch_rss.asmx?WSDL, which can be used and tested to convert a simple Google search into an RSS feed, is causing issues when I try to create a new Web Service out of it. I've tried with the WSDL at the url and with a locally saved version and get the same response. Any ideas? This particular issue also showed up with my new WS wizard that I'm working on. The error in this case is generated from the existing WTP Web Service wizard available in the New wizards under the Web Services category. I've also noticed that though a new project is created, it's lacking the JRE library entry in its path and you have to go in and add it to the classpath manually. I don't think these issues are related however. Here's the console output with the exception: Retrieving document at 'file:/NotBackedUp/bfitzpat/eclipse3.6m7b/runtime-New_configuration_May25/WSDLProj/gsearch_rss.wsdl'. Gsearch_rssSoap !ENTRY org.jboss.tools.ws.creation.core 4 0 2010-06-16 16:24:13.838 !MESSAGE Failed to Generate Web Service code, please check the log for more details !STACK 1 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:450) 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) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1008) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:887) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:426) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3552) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3171) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:254) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:274) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1525) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1257) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1294) at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:730) at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:2839) at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:734) at org.eclipse.swt.widgets.Tree.gtk_key_press_event(Tree.java:1977) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1743) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4794) at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:3485) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4372) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8163) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1239) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2224) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3169) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) 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:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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) !SUBENTRY 1 id 4 0 2010-06-16 16:24:13.841 !MESSAGE Failed to Generate Web Service code, please check the log for more details -- 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

5
36
0 / 0

[JBoss JIRA] Created: (JBIDE-6660) [tester] does not handle password protected services

by Max Rydahl Andersen (JIRA)

[tester] does not handle password protected services ---------------------------------------------------- Key: JBIDE-6660 URL: https://jira.jboss.org/browse/JBIDE-6660 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M1 Reporter: Max Rydahl Andersen Assignee: Brian Fitzpatrick Fix For: 3.2.0.M2 Trying to use WS Tester against a password protected url (such as deltacloudd) give me a username/password dialog but the result never shows up. Doing the request again also asks me again for username/password, no way to make it persist it. -- 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
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6583) org.jboss.tools.seam.ui.test takes more than 15 mins - can it be split into smaller pieces?

by Nick Boldt (JIRA)

org.jboss.tools.seam.ui.test takes more than 15 mins - can it be split into smaller pieces? ------------------------------------------------------------------------------------------- Key: JBIDE-6583 URL: https://jira.jboss.org/browse/JBIDE-6583 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.M1 Reporter: Nick Boldt Assignee: Alexey Kazakov [ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-test-plugin:0.9.0:test (default-test) on project org.jboss.tools.seam.ui.test: Error while executing platform: Error while executing external command, process killed. Process timeout out after 900 seconds -> [Help 2] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonatype.tycho:maven-osgi-test-plugin:0.9.0:test (default-test) on project org.jboss.tools.seam.ui.test: Error while executing platform at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:141) org.jboss.tools.seam.ui.test takes more than 15 mins - can it be split into smaller pieces? -- 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-6005) JBoss Profiler 2 integration

by Jesper Pedersen (JIRA)

JBoss Profiler 2 integration ---------------------------- Key: JBIDE-6005 URL: https://jira.jboss.org/jira/browse/JBIDE-6005 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Jesper Pedersen Provide integration support for the JBoss Profiler 2 branch, such that the tool and be run from within JBoss Tools - and the reports can be viewed. -- 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

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