11:15 a.m.
[
https://jira.jboss.org/jira/browse/JBIDE-5199?page=com.atlassian.jira.plu...
]
Brian Fitzpatrick commented on JBIDE-5199:
------------------------------------------
My biggest concern with adding the 4.7 functionality is that it won't be available in
4.6 or 4.4...
Do we have any way of only adding particular functionality based on the ESB level
specified for the runtime associated with the project?
Or is this an "all or nothing" effort where they get everything and have to know
what's 4.7 functionality if they're working on 4.6, etc...?
ESB Editor - Changes for ESB 4.7
--------------------------------
Key: JBIDE-5199
URL: https://jira.jboss.org/jira/browse/JBIDE-5199
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
To support ESB 4.7, we have several new actions, providers, and so on that should be
available in the ESB editor.
1- new provider/bus
<http-provider name="HTTP-PROVIDER">
<http-bus busid="HTTP-BUS"
transportGuarantee="CONFIDENTIAL">
<allowed-roles>
<role name="friend" />
</allowed-roles>
</http-bus>
</http-provider>
2- new gateway: http-gateway (shown in webservice_proxy_security)
<listeners>
<http-gateway name="HTTP-GATEWAY"
busidref="HTTP-BUS"
urlPattern="ProxyWS/*" />
</listeners>
3- new action: org.jboss.soa.esb.actions.soap.proxy.SOAPProxy - (shown
in quickstarts\webservice_proxy_basic)
<action name="proxy"
class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy">
<property name="wsdl"
value="https://localhost:8443/webservice_proxy_security/HelloWorldWS?wsdl"/>
<property name="endpointUrl"
value="https://localhost:8443/webservice_proxy_security/HelloWorldWS"/>
<property name="file"
value="/META-INF/httpclient-8443.properties"/>
</action>
4- security changes (shown in webservice_proxy_security):
<globals>
<!-- Security setting for all http-providers and all EBWSs in
this jboss-esb.xml file.-->
<war-security method="BASIC" domain="JBossWS" /> <!--
uname:
"kermit" pw: "thefrog" -->
</globals>
5- new action: xsltaction (shown in webservice_proxy_versioning) - this one should allow
opening the templateFile with the XSLT editor now included in JBT/JBDS and browsing for
the file
<action name="proxy-transform-old-to-new"
class="org.jboss.soa.esb.actions.transformation.xslt.XsltAction">
<property name="templateFile"
value="/Proxy_Versioning_RequestTransform.xsl"/>
<property name="failOnWarning"
value="true"/>
<property name="resultType"
value="STRING"/>
</action>
6- changes to the ContentBasedRouterAction (shown in the ESB4.7 fun_cbr)
<action class="org.jboss.soa.esb.actions.ContentBasedRouter"
name="ContentBasedRouter">
<property name="cbrAlias" value="Regex"/>
<property name="ruleSet"
value="/regex-rules.properties"/>
<property name="ruleReload"
value="true"/>
<property name="destinations">
<route-to destination-name="blue"
service-category="BlueTeam" service-name="GoBlue" />
<route-to destination-name="red"
service-category="RedTeam" service-name="GoRed" />
<route-to destination-name="green"
service-category="GreenTeam" service-name="GoGreen" />
</property>
</action>
and
<action class="org.jboss.soa.esb.actions.ContentBasedRouter"
name="ContentBasedRouter">
<property name="cbrAlias" value="XPath"/>
<property name="destinations">
<namespace prefix="ord"
uri="http://org.jboss.soa.esb/Order" />
<route-to service-category="BlueTeam"
service-name="GoBlue"
expression="/ord:Order[@statusCode='0']" />
<route-to service-category="RedTeam"
service-name="GoRed"
expression="/ord:Order[@statusCode='1']" />
<route-to service-category="GreenTeam"
service-name="GoGreen"
expression="/ord:Order[@statusCode='2']" />
</property>
</action>
--
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