[jbosstools-issues] [JBoss JIRA] (JBIDE-11479) Creating new eap6 / as71 server fails in empty workspace, stack blown away by npe

Rob Stryker (JIRA) jira-events at lists.jboss.org
Wed Apr 4 23:15:47 EDT 2012


    [ https://issues.jboss.org/browse/JBIDE-11479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681885#comment-12681885 ] 

Rob Stryker commented on JBIDE-11479:
-------------------------------------

This fails because our working copies of the runtimes aren't updated every time a user updates a widget. The WC is updated on exit() of the runtime page, however, exit() on the runtime page is called AFTER the new page is created. This means when the server page is being created, the runtime still has default values (such as a home dir of /usr/local/whatever/jboss) and will not find an accurate server version and then will NPE.  
                
> Creating new eap6 / as71 server fails in empty workspace, stack blown away by npe 
> ----------------------------------------------------------------------------------
>
>                 Key: JBIDE-11479
>                 URL: https://issues.jboss.org/browse/JBIDE-11479
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 3.3.0.Beta3
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 3.3.0.Beta3
>
>
> The stack gets blown away when trying to discover if a given server type should show the 'bind to all ports' checkbox. Somehow, the runtime location is not fully recognized at this point in the page. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list