[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
[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
[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
[JBoss JIRA] Created: (JBIDE-8709) Removing class which there are still references too causes error logging/unrelated invalidation errors
by Max Rydahl Andersen (JIRA)
Removing class which there are still references too causes error logging/unrelated invalidation errors
------------------------------------------------------------------------------------------------------
Key: JBIDE-8709
URL: https://issues.jboss.org/browse/JBIDE-8709
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.Final
Reporter: Max Rydahl Andersen
Assignee: Alexey Kazakov
Priority: Minor
I created a qualifier annotation called Asynchronous and reference it in an inject:
@Inject @Asynchronous Foo bar;
then I deleted the Asynchrounous class and the above error becomes a compile error ( that is expected )
but all CDI validation now reported nothing was correct (alot of EL validation errors not related to bar reference) and
the following was logged in errors:
Java Model Exception: Java Model Status [Asynhronous.java [in org.jboss.weld.examples.pastecode.session [in src/main/java [in weld-jsf-pastecode]]] does not exist]
at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:502)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246)
at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107)
at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:515)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:252)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:238)
at org.eclipse.jdt.internal.core.SourceType.getAnnotations(SourceType.java:191)
at org.jboss.tools.cdi.internal.core.impl.definition.AbstractMemberDefinition.init(AbstractMemberDefinition.java:66)
at org.jboss.tools.cdi.internal.core.impl.definition.AbstractTypeDefinition.init(AbstractTypeDefinition.java:60)
at org.jboss.tools.cdi.internal.core.impl.definition.AnnotationDefinition.init(AnnotationDefinition.java:60)
at org.jboss.tools.cdi.internal.core.impl.definition.AbstractMemberDefinition.setAnnotatable(AbstractMemberDefinition.java:50)
at org.jboss.tools.cdi.internal.core.impl.definition.AbstractTypeDefinition.setType(AbstractTypeDefinition.java:54)
at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.createAnnotation(DefinitionContext.java:232)
at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.getAnnotationKind(DefinitionContext.java:226)
at org.jboss.tools.cdi.internal.core.impl.AbstractBeanElement.getQualifierDeclarations(AbstractBeanElement.java:172)
at org.jboss.tools.cdi.internal.core.impl.AbstractBeanElement.getQualifierDeclarations(AbstractBeanElement.java:165)
at org.jboss.tools.cdi.internal.core.impl.CDIProject.getBeans(CDIProject.java:307)
at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateInjectionPoint(CDICoreValidator.java:1349)
at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:465)
at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:366)
at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:270)
at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validate(ValidatorManager.java:113)
at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:84)
at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Missing classes should not *stop* our validator since that is a common scenario so not sure what is going on ? Some stale model references maybe?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-9020) NPE when Ctrl+Click on @Inject void foo(Object o);
by Alexey Kazakov (JIRA)
NPE when Ctrl+Click on @Inject void foo(Object o);
--------------------------------------------------
Key: JBIDE-9020
URL: https://issues.jboss.org/browse/JBIDE-9020
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M2
EXECUTE: Create any CDI Project.
EXECUTE: Enable CDI support for the project.
EXECUTE: Add @Inject void foo(Object o) {} method to any class.
EXECUTE: Ctrl+Click on foo
FAILURE:
java.lang.NullPointerException
at org.jboss.tools.cdi.internal.core.impl.CDIProject.getEventType(CDIProject.java:846)
at org.jboss.tools.cdi.internal.core.impl.CDIProject.resolveObserverMethods(CDIProject.java:813)
at org.jboss.tools.cdi.text.ext.hyperlink.EventAndObserverMethodHyperlinkDetector.detectHyperlinks(EventAndObserverMethodHyperlinkDetector.java:112)
at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80)
at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:286)
at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:258)
at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:462)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:211)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months