[jbosstools-issues] [JBoss JIRA] (JBIDE-13610) As-you-type CDI validation not working if CDI support is added after cdi components creation

[Jaroslav Jankovič (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-13610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jaroslav Jankovič updated JBIDE-13610:
--------------------------------------

    Steps to Reproduce: 
*First test case covers as-you-type CDI validation for CDI beans fail*:

STEP: create dynamic web project with simple bean:
{code:title=A.test}
public class A {

	public A() {
		
	}

}
{code}
STEP: enable cdi support on the project
STEP: modify bean to be session scoped (don't save the file):
{code:title=A.java}
@SessionScoped
public class A {

	public A() {
		
	}

}
{code}
FAIL: there is no expected validation warning ("Managed bean A1 which declares a passivating scope SessionScoped must be passivation capable [JSR-299 §6.6.4]")
STEP: save the file (validation marker should be finally invoked)
STEP: remove line with session scoped annotation (don't save the file)
FAIL: validation marker is still there even session scoped validation is removed
STEP: save the file (validation marker should disappear)

*Second test case covers as-you-type CDI validation for beans.xml fail*:

STEP: create dynamic web project with one simple bean (A1.java) and one alternative bean (A2.java) but don't register alternative bean in beans.xml:
STEP: create beans.xml via wizard
STEP: enable cdi support on the project
STEP: modify beans.xml to contain non-alternative bean A1 (don't save the file)
FAIL: there is no expected validation error ("is not an alternative bean class [JSR-299 §5.1.1]")
STEP: save the file (validation marker should be finally invoked)
STEP: modify alternative bean in beans.xml to be A2.java (don't save the file)
FAIL: validation marker is still there even that A2.java is regular alternative bean
STEP: save the file (validation marker should disappear)

  was:
First test case covers as-you-type CDI validation for CDI beans fail:

STEP: create dynamic web project with simple bean:
{code:title=A.test}
public class A {

	public A() {
		
	}

}
{code}
STEP: enable cdi support on the project
STEP: modify bean to be session scoped (don't save the file):
{code:title=A.java}
@SessionScoped
public class A {

	public A() {
		
	}

}
{code}
FAIL: there is no expected validation warning ("Managed bean A1 which declares a passivating scope SessionScoped must be passivation capable [JSR-299 §6.6.4]")
STEP: save the file (validation marker should be finally invoked)
STEP: remove line with session scoped annotation (don't save the file)
FAIL: validation marker is still there even session scoped validation is removed
STEP: save the file (validation marker should disappear)

Second test case covers as-you-type CDI validation for beans.xml fail:
STEP: create dynamic web project with one simple bean (A1.java) and one alternative bean (A2.java) but don't register alternative bean in beans.xml:
STEP: create beans.xml via wizard
STEP: enable cdi support on the project
STEP: modify beans.xml to contain non-alternative bean A1 (don't save the file)
FAIL: there is no expected validation error ("is not an alternative bean class [JSR-299 §5.1.1]")
STEP: save the file (validation marker should be finally invoked)
STEP: modify alternative bean in beans.xml to be A2.java (don't save the file)
FAIL: validation marker is still there even that A2.java is regular alternative bean
STEP: save the file (validation marker should disappear)


    
> As-you-type CDI validation not working if CDI support is added after cdi components creation
> --------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13610
>                 URL: https://issues.jboss.org/browse/JBIDE-13610
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: CDI
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Jaroslav Jankovič
>            Assignee: Alexey Kazakov
>            Priority: Critical
>             Fix For: 4.1.0.Alpha2
>
>
> As-you-type cdi validation is not working if cdi support is added into project after cdi components creation. I have tested it for both CDI beans and beans.xml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira