[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
Brian Fitzpatrick (JIRA)
jira-events at lists.jboss.org
Tue Dec 1 17:24:29 EST 2009
[ https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fitzpatrick updated JBIDE-5191:
-------------------------------------
Attachment: ESB.Example.XML2POJO2.zip
Max, here's an example project that takes advantage of a couple of linked files...
If you drill into the Service's actions list, you'll see a number of actions. Three of these link to other editors:
1) displayBeforeTransformer links to the action class (click on "Class:" which is underlined)
2) discover-message-origin links to a groovy script (click on "Script:" which is underlined) - if the Groovy editor is installed it will open in it, otherwise it just opens it as a text file
3) transform links to a Smooks config (click on "Smooks Config:" which is underlined) and opens in the Smooks Configuration editor
There are also some new actions in JBIDE-5199 that should be added, but we're waiting on info from Kevin Conner. I've asked Slava to add the XsltAction, which is one we know is new.
> ESB Editor - linking in other editors where appropriate
> -------------------------------------------------------
>
> Key: JBIDE-5191
> URL: https://jira.jboss.org/jira/browse/JBIDE-5191
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: esb
> Affects Versions: 3.1.0.M4
> Reporter: Brian Fitzpatrick
> Assignee: Viacheslav Kabanovich
> Fix For: 3.1.0.CR1
>
> Attachments: ESB.Example.XML2POJO2.zip, new-resource-selector.jpg
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> New JIRA to deal with requirement "Developer Tools: Linking Editors" in the SOA-P PRD.
> From the ESB editor, depending on the action used, the user has to currently open any associated editor manually to edit particular files, such as jboss-smooks.xml from the SmooksAction. This is a usability hit.
> It would be nice if, like in the Eclipse Plug-in/Manifest editor, the text beside the field for the file would show up as a hyperlink that the user could click to open the file in the associated editor. So in the SmooksAction case, the "Smooks Config:" label would become a hyperlink that would open the Smooks editor for the file referenced in the field.
> Product management is looking to link:
> Smooks editor
> Drools editor
> jPDL editor
> XSLT editor (once it gets added)
> Groovy editor (if added by the end-user)
>
> Would this be possible for JBDS 3?
--
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
More information about the jbosstools-issues
mailing list