[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-5191) ESB Editor - linking in other editors where appropriate
[
https://jira.jboss.org/jira/browse/JBIDE-5191?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick updated JBIDE-5191:
-------------------------------------
Hi again...
I gained some additional information from Kevin Conner about the
org.jboss.soa.esb.actions.ContentBasedRouter action...
Looks like there's a couple of different flavors of this action.
One is the Drools version you've already seen... If cbrAlias is not present or maps to
"JBRules" or "Drools" (case insensitive) then it is the
JBossRulesRouter. So in this case, the "ruleSet" contains the path to a Drools
file, and should open the Drools editor.
The other one is the XPath version... If cbrAlias is "XPath" then it is the
XPathRouter, which it looks like you can use a properties file to define the XPath
routing... I'll append the info from Kevin below... If it's one of these xpath
properties files, it looks like we should simply open the file in a text editor.
On 18/11/09 11:55, Kevin Conner wrote:
<property name="ruleSet"
value="/org/jboss/soa/esb/actions/cbr/xpath/rules.properties"/>
The contents of this file is a normal property file containing the rules.
scat-blue=/order/header[@cat='blue']
scat-red=/order/header[@cat='red']
scat-green=/order/header[@cat='green']
The format of that file is
<destination>=<expression>
where destination defaults to category-name (the issue I thought we had)
and the destination is retrieved from the destinations. You can specify
a proper destination though, and should do.
So a proper config would look like the following.
<action class="org.jboss.soa.esb.actions.ContentBasedRouter"
name="ContentBasedRouter">
<property name="cbrAlias" value="XPath"/>
<property name="ruleSet" value="/xpathRuleSet"/>
<property name="destinations">
<namespace prefix="ord" uri="http://org.jboss.soa.esb/Order"
/>
<route-to service-category="BlueTeam" service-name="GoBlue"
destination-name="blue" />
<route-to service-category="RedTeam" service-name="GoRed"
destination-name="red" />
<route-to service-category="GreenTeam" service-name="GoGreen"
destination-name="green" />
</property>
</action>
and the contents of the xpathRuleSet resource would be something like
the following
blue=/ord:Order[@statusCode='0']
red=/ord:Order[@statusCode='1']
green=/ord:Order[@statusCode='2']
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
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