[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6065) Default Invm Scope to GLOBAL - Usability

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-6065:
------------------------------------

I am woefully unprepared to be playing around with the actual *content* of ESB projects, but, I am by nature against hte idea of having the server adapter change files before deploying. 

This should all be done in the editor or during the creation of actions / services that may require refactorings. And since I'm not at all sure how to replicate the situation (since I'm unfamiliar with ESB workflows and the 1-2-3 step at the top is a bit vague) I think it's unlikely I would have any ideas to solve this particular issue at this time. 

> Default Invm Scope to GLOBAL - Usability
> ----------------------------------------
>
>                 Key: JBIDE-6065
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-6065
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: esb
>    Affects Versions: 3.0.0.GA
>            Reporter: Burr Sutter
>            Assignee: Rob Stryker
>             Fix For: 3.2.next
>
>         Attachments: INVM_Scope.png
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> I have found that I normally forget to set the INVM Scope to GLOBAL when creating a new service.  Forgetting to set this attribute results in a runtime error message upon deployment.
> It is very common to forget the attribute because of is placement - at the service level instead of the listener level.  
> User will tend to follow these steps:
> - Add a Service
> - Add a HTTP Listener with a urlpattern
> - Add a SOAPProxy Action
> and forget to go back to the Service screen and flip INVM scope to Global
> see screen shot

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