[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-2259) NullPointerException in SeamXMLHelper in case of repeatedly created Seam EAR projects with the same name

[Victor Rubezhny (JIRA)]

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

Victor Rubezhny resolved JBIDE-2259.
------------------------------------

    Resolution: Done

The revisions #8497 and #8498 resolved the issue. 

At least Seam***ARNewOperationTest TestCases are successfully passed in my environment with no NullPointerException in the .log

> NullPointerException in SeamXMLHelper in case of repeatedly created Seam EAR projects with the same name
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-2259
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-2259
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Seam
>    Affects Versions: 2.1.0.CR1
>         Environment: Eclipse 3.3, Seam 1.2 branch2.1.x
>            Reporter: Victor Rubezhny
>         Assigned To: Victor Rubezhny
>            Priority: Critical
>             Fix For: 2.1.x, 3.0.x
>
>         Attachments: SeamXMLHelper.log
>
>
> A NullPointerException occures in SeamXMLHelper while executing the Seam12EARNewOperationTest JUnit TestCase.
> See the log-file attached
> TestCase: 
> EXECUTE: Create Seam EAR project with name "SeamTestProject"
> EXECUTE: Wait while the project is built
> EXECUTE: Delete the project
> EXECUTE: Create yet another Seam EAR project with name "SeamTestProject" (the same name)
> EXECUTE: Wait while the project is built
> ASSERT: The project crfeated successfully and no NullPointerException is in the .log
> Probably the latency between delete and create project operation is meaningfull. The exception was caught while executing the Seam12EARNewOperationTest. The test creates a Seam EAR project, then performs one of "Create Seam..." operations on the project created (create an Action or Form or Conversation or Entity), then deletes the project. Then it creates the project again with the same name to test the next operation. That was the moment the exception appeared.
> TestCase2: 
> EXECUTE: Start the SeamUiAllTests JUnit Tests
> ASSERT: The JUnit Tests are successfully passed

-- 
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