[
https://jira.jboss.org/jira/browse/JBIDE-6065?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-6065:
------------------------------------------
Ok, stupid question... I'm trying to track down what the "gateway" listeners
are... Is it just HTTP Gateway and JCA Gateway that are the gateway listeners?
The issue with doing the check at "pre-deploy" time is that we don't
necessarily have a pre-deploy validation pass that allows user input. But we can look into
going that way.
We might be able to do something in the editor where if the user adds a gateway listener,
we prompt them (and give them an option to turn the dialog off in the future or always
default to Yes or No) to see if they want to set the inVMScope attribute to GLOBAL at that
point. If yes, we tweak the service config. If not, we leave it.
Burr? Thoughts?
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