Petals View

enhance the flow with the operation of the exchange

Details

  • Type: Improvement Request Improvement Request
  • Status: New New
  • Resolution: Unresolved
  • Affects Version/s: 1.2
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    Now the notifications from the esb have got the operation of the exchange:

    <wsnebm:NotifyContent xmlns:wsnebm="http://www.ebmwebsourcing.com/WS-BaseNotification/NotifyContent" xmlns:ebm="http://www.ebmwebsourcing.com/wsnotification/specificTypes" correlationId="petals:uid:D78B43CE50F7E74691464192412521834" endpoint="BrokerEndpoint" interface="{http://orange.com/ros/services/newbrokerTSE/v1}Broker" meuuid="petals:uid:E2EC1F101B2180A0C04697117315218441" notifDate="1298035077141" operation="{http://orange.com/ros/services/newbrokerTSE/v1}deleteCustomer" processPath="petals:uid:D78B43CE50F7E74691464192692621835" processType="1" service="{http://orange.com/ros/services/newbrokerTSE/v1}BrokerService" status="0">                <wsnebm:params/>            </wsnebm:NotifyContent>

    To get this new xml attribute, we just have to put the context policy operation option:

    <jbi:consumes interface-name="wsn-br:NotificationBroker" service-name="notification:NotificationBrokerService">
			<!-- CDK specific fields -->
			<petalsCDK:operation>Subscribe</petalsCDK:operation>
			<petalsCDK:mep>InOut</petalsCDK:mep>
			<!-- Component specific elements -->
			<!-- Subscription to process on init : -->
			<kpi:TopicExpressionDialect>http://docs.oasis-open.org/wsn/t-1/TopicExpression/Full</kpi:TopicExpressionDialect>
			<kpi:TopicExpressionNamespace>http://petals.ow2.org/topic</kpi:TopicExpressionNamespace>
			<kpi:TopicExpressionPrefix>petals</kpi:TopicExpressionPrefix>
			<kpi:TopicExpressionContent>petals:component/cdk/producer/in[@wstop:topic='true']</kpi:TopicExpressionContent>
			<kpi:MessageContentSOADialect>http://www.ebmwebsourcing.com/wsnotification/soaparameter</kpi:MessageContentSOADialect>
			<kpi:MessageContentSOAInterfaceNamespace>http://orange.com/ros/services/newbrokerTSE/v1</kpi:MessageContentSOAInterfaceNamespace>
			<kpi:MessageContentSOAInterfaceName>Broker</kpi:MessageContentSOAInterfaceName>
			<kpi:MessageContentProcessTypeDialect>http://www.ebmwebsourcing.com/wsnotification/processtype</kpi:MessageContentProcessTypeDialect>
			<kpi:MessageContentProcessTypeList>1|2|3|4|5</kpi:MessageContentProcessTypeList>
			<kpi:TransformPolicy>/newBroker-orchestrator-in.xsl</kpi:TransformPolicy>
			<kpi:ContextPolicyCorrelationId>true</kpi:ContextPolicyCorrelationId>
			<kpi:ContextPolicyInterface>true</kpi:ContextPolicyInterface>
			<kpi:ContextPolicyEndpoint>true</kpi:ContextPolicyEndpoint>
			<kpi:ContextPolicyMeuuid>true</kpi:ContextPolicyMeuuid>
			<kpi:ContextPolicyNotifDate>true</kpi:ContextPolicyNotifDate>
			<kpi:ContextPolicyService>true</kpi:ContextPolicyService>
			<kpi:ContextPolicyStatus>true</kpi:ContextPolicyStatus>
			<kpi:ContextPolicyOperation>true</kpi:ContextPolicyOperation>
			<kpi:ProcessPolicyAction>create</kpi:ProcessPolicyAction>
		</jbi:consumes>

    So now, we would like to update petals view to:
    ->store into flowstep the operation with the others attributes
    ->store into the flow step ref the operation to identify the step on the interface namespace, the service namespace...and the operation namespace .

    Show
    Now the notifications from the esb have got the operation of the exchange: 
    <wsnebm:NotifyContent xmlns:wsnebm="http://www.ebmwebsourcing.com/WS-BaseNotification/NotifyContent" xmlns:ebm="http://www.ebmwebsourcing.com/wsnotification/specificTypes" correlationId="petals:uid:D78B43CE50F7E74691464192412521834" endpoint="BrokerEndpoint" interface="{http://orange.com/ros/services/newbrokerTSE/v1}Broker" meuuid="petals:uid:E2EC1F101B2180A0C04697117315218441" notifDate="1298035077141" operation="{http://orange.com/ros/services/newbrokerTSE/v1}deleteCustomer" processPath="petals:uid:D78B43CE50F7E74691464192692621835" processType="1" service="{http://orange.com/ros/services/newbrokerTSE/v1}BrokerService" status="0">                <wsnebm:params/>            </wsnebm:NotifyContent>
    To get this new xml attribute, we just have to put the context policy operation option: 
    <jbi:consumes interface-name="wsn-br:NotificationBroker" service-name="notification:NotificationBrokerService">
			<!-- CDK specific fields -->
			<petalsCDK:operation>Subscribe</petalsCDK:operation>
			<petalsCDK:mep>InOut</petalsCDK:mep>
			<!-- Component specific elements -->
			<!-- Subscription to process on init : -->
			<kpi:TopicExpressionDialect>http://docs.oasis-open.org/wsn/t-1/TopicExpression/Full</kpi:TopicExpressionDialect>
			<kpi:TopicExpressionNamespace>http://petals.ow2.org/topic</kpi:TopicExpressionNamespace>
			<kpi:TopicExpressionPrefix>petals</kpi:TopicExpressionPrefix>
			<kpi:TopicExpressionContent>petals:component/cdk/producer/in[@wstop:topic='true']</kpi:TopicExpressionContent>
			<kpi:MessageContentSOADialect>http://www.ebmwebsourcing.com/wsnotification/soaparameter</kpi:MessageContentSOADialect>
			<kpi:MessageContentSOAInterfaceNamespace>http://orange.com/ros/services/newbrokerTSE/v1</kpi:MessageContentSOAInterfaceNamespace>
			<kpi:MessageContentSOAInterfaceName>Broker</kpi:MessageContentSOAInterfaceName>
			<kpi:MessageContentProcessTypeDialect>http://www.ebmwebsourcing.com/wsnotification/processtype</kpi:MessageContentProcessTypeDialect>
			<kpi:MessageContentProcessTypeList>1|2|3|4|5</kpi:MessageContentProcessTypeList>
			<kpi:TransformPolicy>/newBroker-orchestrator-in.xsl</kpi:TransformPolicy>
			<kpi:ContextPolicyCorrelationId>true</kpi:ContextPolicyCorrelationId>
			<kpi:ContextPolicyInterface>true</kpi:ContextPolicyInterface>
			<kpi:ContextPolicyEndpoint>true</kpi:ContextPolicyEndpoint>
			<kpi:ContextPolicyMeuuid>true</kpi:ContextPolicyMeuuid>
			<kpi:ContextPolicyNotifDate>true</kpi:ContextPolicyNotifDate>
			<kpi:ContextPolicyService>true</kpi:ContextPolicyService>
			<kpi:ContextPolicyStatus>true</kpi:ContextPolicyStatus>
			<kpi:ContextPolicyOperation>true</kpi:ContextPolicyOperation>
			<kpi:ProcessPolicyAction>create</kpi:ProcessPolicyAction>
		</jbi:consumes>
    So now, we would like to update petals view to: ->store into flowstep the operation with the others attributes ->store into the flow step ref the operation to identify the step on the interface namespace, the service namespace...and the operation namespace .

Activity

Ascending order - Click to sort in descending order
Frédéric Gardes made changes - Fri, 18 Feb 2011 - 15:44:56 +0100
Field Original Value New Value
Attachment flowstep-view.png [ 10533 ]
Attachment flowstep-update.png [ 10534 ]

People

Dates

  • Created:
    Fri, 18 Feb 2011 - 15:33:04 +0100
    Updated:
    Thu, 19 May 2011 - 16:49:43 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.