July 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8890) CLONE - CLONE - CDI Component N&N

by Max Rydahl Andersen (JIRA)

CLONE - CLONE - CDI Component N&N --------------------------------- Key: JBIDE-8890 URL: https://issues.jboss.org/browse/JBIDE-8890 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Denis Golovin Assignee: Alexey Kazakov -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8842) Code completion for tag names of Seam config xml

by Alexey Kazakov (JIRA)

Code completion for tag names of Seam config xml ------------------------------------------------ Key: JBIDE-8842 URL: https://issues.jboss.org/browse/JBIDE-8842 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.3.0.M2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-3120) Support webbeans typesafe xml schema

by Max Rydahl Andersen (JIRA)

Support webbeans typesafe xml schema ------------------------------------- Key: JBIDE-3120 URL: https://jira.jboss.org/jira/browse/JBIDE-3120 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: webbeans Reporter: Max Rydahl Andersen Fix For: LATER http://docs.jboss.org/webbeans/reference/1.0/en-US/html/xml.html "The advantage of this approach is that you can write an XML schema that prevents spelling errors in your XML document. It's even possible for a tool to generate the XML schema automatically from the compiled Java code. Or, an integrated development environment could perform the same validation without the need for the explicit intermediate generation step." 1) the RI will have a code->xsd generator for web-beans.xml; could maybe be used for validation....but requires that all classes can compile 2) we should have xml completions following the naming standard layed out by webbeans spec -- 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

14 years, 9 months

5
12
0 / 0

[JBoss JIRA] Created: (JBIDE-9303) BPEL editor always adds "bpel" namespace prefix if missing

by Robert (Bob) Brodt (JIRA)

BPEL editor always adds "bpel" namespace prefix if missing ---------------------------------------------------------- Key: JBIDE-9303 URL: https://issues.jboss.org/browse/JBIDE-9303 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.1.CR1 Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Priority: Minor Fix For: LATER The BPEL editor automatically adds the "bpel" namespace prefix to a file if it does not already have this prefix defined. This causes the editor to show as "dirty" the first time it is opened, even though it hasn't been touched. This is one of those minor annoyances that is difficult to fix because a lot of places in the code assume that the "bpel" prefix is always defined (that's why it's created if it doesn't exist ;) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-8830) Long running tasks detected in org.jboss.tools.seam.ui.test.wizard.Seam20XOperationsTestSuite221CR1.org.jboss.tools.seam.ui.test.wizard.Seam20WARNewOperationTest

by Nick Boldt (JIRA)

Long running tasks detected in org.jboss.tools.seam.ui.test.wizard.Seam20XOperationsTestSuite221CR1.org.jboss.tools.seam.ui.test.wizard.Seam20WARNewOperationTest ------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-8830 URL: https://issues.jboss.org/browse/JBIDE-8830 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.1.M1 Reporter: Nick Boldt Assignee: Alexey Kazakov Fix For: 3.2.1.M1 https://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/job/jboss... Error Message Long running tasks detected: Building workspace (class org.eclipse.core.internal.events.AutoBuildJob) Decoration Calculation (class org.eclipse.ui.internal.decorators.DecorationScheduler$1) JBoss Tools Model Update (class org.jboss.tools.common.model.XJob) Compacting resource model (class org.eclipse.core.internal.utils.StringPoolJob) Stacktrace java.lang.RuntimeException: Long running tasks detected: Building workspace (class org.eclipse.core.internal.events.AutoBuildJob) Decoration Calculation (class org.eclipse.ui.internal.decorators.DecorationScheduler$1) JBoss Tools Model Update (class org.jboss.tools.common.model.XJob) Compacting resource model (class org.eclipse.core.internal.utils.StringPoolJob) at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:49) at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:27) at org.jboss.tools.seam.core.test.project.facet.AbstractSeamFacetTest.createSeamProject(AbstractSeamFacetTest.java:253) at org.jboss.tools.seam.core.test.project.facet.AbstractSeamFacetTest.createSeamWarProject(AbstractSeamFacetTest.java:261) at org.jboss.tools.seam.ui.test.wizard.Seam12WARNewOperationTest.setUp(Seam12WARNewOperationTest.java:55) at org.jboss.tools.seam.ui.test.wizard.Seam20WARNewOperationTest.setUp(Seam20WARNewOperationTest.java:50) at org.jboss.tools.seam.ui.test.wizard.Seam20XOperationsTestSuite201GABase$Seam20WARNewOperationTestSetup.setUp(Seam20XOperationsTestSuite201GABase.java:53) at junit.extensions.TestSetup$1.protect(TestSetup.java:22) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-3725) Seam components from sources are not loaded by Seam Tools model right after project creation.

by Alexey Kazakov (JIRA)

Seam components from sources are not loaded by Seam Tools model right after project creation. --------------------------------------------------------------------------------------------- Key: JBIDE-3725 URL: https://jira.jboss.org/jira/browse/JBIDE-3725 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.0.0.CR2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.0.0.GA 1. Create Seam EAR project using New Seam Web Project (I tested on Seam 2.1) 2. Open home.xhtml 3. Ctrl+Space on #{|}. There is not "authenticator" component (see Authenticator.java). 4. Open "Open Seam Component" dialog. Type "authenticator". There is not any "authenticator" component in the project. Clean/Rebuild helps. -- 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

14 years, 9 months

5
24
0 / 0

[JBoss JIRA] Created: (JBIDE-8016) Content Assist does not propose head-specific tags inside h:head

by Yahor Radtsevich (JIRA)

Content Assist does not propose head-specific tags inside h:head ---------------------------------------------------------------- Key: JBIDE-8016 URL: https://issues.jboss.org/browse/JBIDE-8016 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.Beta2 Reporter: Yahor Radtsevich Assignee: Alexey Kazakov Priority: Minor STEPS TO REPRODUCE (see h_head-vs-head.png): 1. Create a XHTML file with the following content: =================================== <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://java.sun.com/jsf/html"> <h:head> <t </h:head> <h:body> </h:body> </html> =================================== 2. Place the editor cursor after '<t' and press Ctrl-Space. ACTUAL RESULT: No tags is proposed by the Content Assist. EXPECTED RESULT: 'title' tag is proposed. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (JBDS-1582) web.xml error on login authentication scheme

by Neil Buesing (JIRA)

web.xml error on login authentication scheme -------------------------------------------- Key: JBDS-1582 URL: https://issues.jboss.org/browse/JBDS-1582 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 4.0.0.CR4 Environment: Windows 32bit Reporter: Neil Buesing In problems view we get the following error: 'Value should be one of BASIC, DIGEST, FORM, CLIENT-CERT', because we have a custom login module. According to XSD 9http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd) it states the value of <auth-method> within element <login-config> must be : BASIC, DIGEST, FORM, CLIENT-CERT or a vendor specific authentication scheme. We are using a vendor specfiic authentication scheme, and still get this red-x error in the problems view, for the project, and in the editor. I have turned off all validations of the IDE (as I can tell), and I still get this error. How do I disable this error, since our web.xml appears to be valid with the XSD. If there is a known workaround, please let me know. <xsd:complexType name="auth-methodType"> <xsd:annotation> <xsd:documentation> The auth-methodType is used to configure the authentication mechanism for the web application. As a prerequisite to gaining access to any web resources which are protected by an authorization constraint, a user must have authenticated using the configured mechanism. Legal values are "BASIC", "DIGEST", "FORM", "CLIENT-CERT", or a vendor-specific authentication scheme. Used in: login-config </xsd:documentation> </xsd:annotation> <xsd:simpleContent> <xsd:restriction base="javaee:string"/> </xsd:simpleContent> </xsd:complexType> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9230) JAX-RS Content Assist fails when the @java.ws.rs.Path() annotation is typed before the method itself

by Xavier Coulon (JIRA)

JAX-RS Content Assist fails when the @java.ws.rs.Path() annotation is typed before the method itself ---------------------------------------------------------------------------------------------------- Key: JBIDE-9230 URL: https://issues.jboss.org/browse/JBIDE-9230 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Reporter: Xavier Coulon Assignee: Xavier Coulon The following error is raised in the error view when a user attempts to obtain content assist for the @GET() annotation value while this annotation has no parent element in the compilation unit. @Path() public class HelloWorldResource { @GET() } java.lang.NullPointerException at org.jboss.tools.ws.jaxrs.ui.contentassist.PathParamAnnotationValueCompletionProposalComputer.getEnclosingType(PathParamAnnotationValueCompletionProposalComputer.java:233) at org.jboss.tools.ws.jaxrs.ui.contentassist.PathParamAnnotationValueCompletionProposalComputer.resolveContextualCompilationUnit(PathParamAnnotationValueCompletionProposalComputer.java:202) at org.jboss.tools.ws.jaxrs.ui.contentassist.PathParamAnnotationValueCompletionProposalComputer.computeCompletionProposals(PathParamAnnotationValueCompletionProposalComputer.java:89) at org.eclipse.jdt.internal.ui.text.java.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:318) at org.eclipse.jdt.internal.ui.text.java.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:267) at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor.collectProposals(ContentAssistProcessor.java:283) at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor.computeCompletionProposals(ContentAssistProcessor.java:243) at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1830) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:556) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:553) at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:488) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:482) at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1656) at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor$AdaptedSourceViewer.doOperation(CompilationUnitEditor.java:183) at org.eclipse.ui.texteditor.ContentAssistAction$1.run(ContentAssistAction.java:82) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.texteditor.ContentAssistAction.run(ContentAssistAction.java:80) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:185) at org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:109) 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:1262) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1052) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1104) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1100) at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1509) at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4623) at org.eclipse.swt.widgets.Canvas.WM_CHAR(Canvas.java:345) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4511) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4970) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2530) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3750) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) 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:344) 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:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9006) In resolving observers take into account qualifier members

by Viacheslav Kabanovich (JIRA)

In resolving observers take into account qualifier members ---------------------------------------------------------- Key: JBIDE-9006 URL: https://issues.jboss.org/browse/JBIDE-9006 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Affects Versions: 3.3.0.M1 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M2 EXECUTE: create following Java elements: 1) class: TamingCommand 2) Qualifier: Role with member String value(); 3) Observer in some class: public void tamed(@Observes @Role("Master") TamingCommand tamed) 4) Field in some class: @Role("Master") Event<TamingCommand> tamingEvent; 5) Field in some class: @Role("Alien") Event<TamingCommand> solicitingEvent; ASSERT: Observer is resolved to field tamingEvent. ASSERT: Observer is not resolved to field solicitingEvent. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
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 2011