[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6065) Default Invm Scope to GLOBAL - Usability
[
https://jira.jboss.org/jira/browse/JBIDE-6065?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBIDE-6065:
-------------------------------------
There are down sides to using InVM so this should really be a deliberate choice,
especially as this exception is only raised if the user has decided not to enable InVM as
the global default. This is the way it is handled in the server so it would be better if
the tooling followed suit.
A better solution may be to have pre-deployment check whereby the user can be prompted if
there are only gateway listeners. In this way the user is aware of what is going on and
can make the decision.
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: Brian Fitzpatrick
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