[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-1696) Incremental Seam Validator does not validate subclasses.

[Alexey Kazakov (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBIDE-1696?page=all ]

Alexey Kazakov updated JBIDE-1696:
----------------------------------

    Description: 
How it should work:
1. EXECUTE: Create seam war project.
2. EXECUTE: Create ClassA.java:

public class ClassA {}

3. EXECUTE: Create ClassB.java:

@Stateful
@Name("comp")
public class ClassB extends ClassA {
}

4. EXECUTE: build project.
5. ASSERT: There is an error marker: Stateful component must have a method marked @Remove
6. EXECUTE: Add @Remove to ClassA:

public class ClassA {
   @Remove
   public void foo() {}
}

7. EXECUTE: build project.
8. ASSERT: Validator removes the error marker.

But now only cleaning/building the project or changing ClassB makes Validator see changes for ClassB.

  was:
How it should work:
1. EXECUTE: Create seam war project.
2. EXECUTE: Create ClassA.java:

public class ClassA {}

3. EXECUTE: Create ClassB.java:

@Stateful
@Name("comp")
public class ClassB {
}

4. EXECUTE: build project.
5. ASSERT: There is an error marker: Stateful component must have a method marked @Remove
6. EXECUTE: Add @Remove to ClassA:

public class ClassA {
   @Remove
   public void foo() {}
}

7. EXECUTE: build project.
8. ASSERT: Validator removes the error marker.

But now only cleaning/building the project or changing ClassB makes Validator see changes for ClassB.


> Incremental Seam Validator does not validate subclasses.
> --------------------------------------------------------
>
>                 Key: JBIDE-1696
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-1696
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Seam
>    Affects Versions: 2.0.1
>            Reporter: Alexey Kazakov
>         Assigned To: Alexey Kazakov
>             Fix For: 2.1
>
>
> How it should work:
> 1. EXECUTE: Create seam war project.
> 2. EXECUTE: Create ClassA.java:
> public class ClassA {}
> 3. EXECUTE: Create ClassB.java:
> @Stateful
> @Name("comp")
> public class ClassB extends ClassA {
> }
> 4. EXECUTE: build project.
> 5. ASSERT: There is an error marker: Stateful component must have a method marked @Remove
> 6. EXECUTE: Add @Remove to ClassA:
> public class ClassA {
>    @Remove
>    public void foo() {}
> }
> 7. EXECUTE: build project.
> 8. ASSERT: Validator removes the error marker.
> But now only cleaning/building the project or changing ClassB makes Validator see changes for ClassB.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira