[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5199) ESB Editor - Changes for ESB 4.7

Viacheslav Kabanovich (JIRA) jira-events at lists.jboss.org
Thu Nov 26 12:28:29 EST 2009


    [ https://jira.jboss.org/jira/browse/JBIDE-5199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12496874#action_12496874 ] 

Viacheslav Kabanovich commented on JBIDE-5199:
----------------------------------------------

I have implemented all features listed above for ESB 4.7 (schema 1.2.0), so I think this issue may be put to resolved as feature request.
Still there are some questions that I tried to resolve in a 'default' way which may result in bug issues:

1. SmooksAction: In which versions properties excludeNonSerializables, messageProfile are still used? - now I left them as is.

2. BpmProcessor: what is correct property name: 'process-definition-name' or 'processdefinition'? - now I used 'processdefinition'.

3. HttpRouter and SOAPProxy: Does property 'file' exist, or it shoud be set by http-client-property child element of endpoitUrl property? - now I use the child element.

4. EmailRouter and EmailWiretap: usage of attachment is not clear; that remains unimplemented.

5. ContextBasedRouter: Should element <namespace> be a child of "namespaces" or "destinations" property? - now I resolved in favour of "namespaces".

6. One more question is if some of features (by my list of Nov 18) should be implemented for ESB 4.6?

7. Finally, I expect your feedback and comments as to what is done.

So, please reopen this issue or create new bug issue when you have data to move on.


> 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
>            Priority: Critical
>             Fix For: 3.1.0.CR1
>
>         Attachments: jbossesb-1.2.0.xsd, ProgrammersGuideESB4.7.pdf
>
>   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

        


More information about the jbosstools-issues mailing list