[jbosstools-issues] [JBoss JIRA] (JBIDE-14339) The JBoss WS Runtime Location is NULL. Please set the location on JBoss WS preferences page.

[Brian Fitzpatrick (JIRA)]

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

Brian Fitzpatrick commented on JBIDE-14339:
-------------------------------------------

Is the project you're creating the WS client in a Dynamic Web Project? If so, is the JBoss Web Services Core facet enabled in the Project Facets for the project? To check, right-click on the Properties and select Project Facets, select JBoss Web Services Core in the list.

The issue appears to be the fact that the Preference default isn't being picked up. The workaround is to select the JBoss Web Services Core facet, look to the right in the tabs - Details & Runtimes, and select your runtime in the Runtimes list. 

Definitely a weird issue. But that seems to be the workaround. We'll see if we can find a way to fix that however, probably by finding the workbench default (set in the preferences).
                
> The JBoss WS Runtime Location is NULL. Please set the location on JBoss WS preferences page.
> --------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-14339
>                 URL: https://issues.jboss.org/browse/JBIDE-14339
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Webservices
>            Reporter: Mustafa Musaji
>             Fix For: 4.1.0.Beta1
>
>         Attachments: JBDS_WS_Error.png, JBDS_WS_Error_config.png
>
>
> Using the Web Services Tools to generate client stubs etc I always seem to get the error "The JBoss WS Runtime Location is NULL. Please set the location on JBoss WS preferences page."
> See attached screen shots which shows I have it configured (correctly from what I can tell)

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