[
http://jira.jboss.com/jira/browse/JBIDE-2064?page=comments#action_12409825 ]
John Graham commented on JBIDE-2064:
------------------------------------
Re: repository or not
I've seen both attempted (just local file system/repository based) and my experience
is that it is better to start with a good editor for local resources, leveraging Eclipse
team support for easily available repositories (CVS, SVN) if users want. Next, if there is
enough call to make repository support a strong requirement, then (as mentioned in the
description), that could be a second level addition.
JBossESB graphical node/service designer
----------------------------------------
Key: JBIDE-2064
URL:
http://jira.jboss.com/jira/browse/JBIDE-2064
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Reporter: Mark Little
Fix For: 2.2.x, LATER
Attachments: SOA Tooling.pdf
Currently the ESB deployment descriptor is XML based but we need it to be graphically
oriented. Each ESB service is a collection of actions that are re-usable components. The
graphical tool would allow for the construction (within Eclipse) of a service from action
chaining. The action descriptions would be storable in a repository (though that is a
second level addition). We want to isolate the user from the XML as much as possible
because it is prone to errors. Plus, it makes service re-usability more problematical.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira