Petals SE KPI

enhance the subscribe filters and policies

Details

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

    ->allow to filter only on the interface namespace
    ->allow to filter only on the interface name
    ->allow to filter only on the service namespace
    ->allow to filter only on the service name
    ->add the operation filter (on the operation name and/or namespace of the exchange)
    ->add the processType filter (on the mandatory PROCESS_TYPE_KEY property into the exchange)
    ->add the operation policy (to add the operation to the notification)
    ->extends the process policy (to add the process type to the exchange and notification, instead of add it through the xsl transformation)

    Modified files:
    KeyProcessIndicatorService.java
    KpiServiceUnitManager.java

    It impacts the ws-notification-extension project into wsstar:
    ->extends the context policy : add the operation attribute (optional)
    ->extends the process policy : add the type attribute (optional)
    ->add the operation type
    ->add the element operation (of operation type)
    ->add the process type list type
    ->add the element process type list (of process type list type)
    ->add tests for the new types elements, and attributes

    Moreover:
    ->fix previous test payloads (not valid with their schema or not and/or bad values)

    Modified files:
    WSNotificationExtensionReader.java
    WSNotificationExtensionWriter.java
    WSNotificationExtensionFactory.java
    WSNotificationExtensionFactoryImpl.java
    WsnExtensionConstants.java
    ContextPolicyType.java
    ProcessPolicyType.java
    SOAParameterType.java
    ProcessPolicyTypeImpl.java
    SOAParameterTypeImpl.java
    WsnSpecificTypeHelper.java
    specificTypesForNotification.xsd
    ContextPolicy.xml
    ProcessPolicy.xml
    ResourcesUuid.xml
    SOAParameter.xml
    TransformPolicy.xml
    TerminationTime.xml
    wsdm-mows-events-with-supported-attr.xml
    stylesheetSample.xsl
    Operation.xml
    TestWSNotificationExtension.java
    ContextPolicyTypeImpl.java

    Show
    ->allow to filter only on the interface namespace ->allow to filter only on the interface name ->allow to filter only on the service namespace ->allow to filter only on the service name ->add the operation filter (on the operation name and/or namespace of the exchange) ->add the processType filter (on the mandatory PROCESS_TYPE_KEY property into the exchange) ->add the operation policy (to add the operation to the notification) ->extends the process policy (to add the process type to the exchange and notification, instead of add it through the xsl transformation) Modified files: KeyProcessIndicatorService.java KpiServiceUnitManager.java It impacts the ws-notification-extension project into wsstar: ->extends the context policy : add the operation attribute (optional) ->extends the process policy : add the type attribute (optional) ->add the operation type ->add the element operation (of operation type) ->add the process type list type ->add the element process type list (of process type list type) ->add tests for the new types elements, and attributes Moreover: ->fix previous test payloads (not valid with their schema or not and/or bad values) Modified files: WSNotificationExtensionReader.java WSNotificationExtensionWriter.java WSNotificationExtensionFactory.java WSNotificationExtensionFactoryImpl.java WsnExtensionConstants.java ContextPolicyType.java ProcessPolicyType.java SOAParameterType.java ProcessPolicyTypeImpl.java SOAParameterTypeImpl.java WsnSpecificTypeHelper.java specificTypesForNotification.xsd ContextPolicy.xml ProcessPolicy.xml ResourcesUuid.xml SOAParameter.xml TransformPolicy.xml TerminationTime.xml wsdm-mows-events-with-supported-attr.xml stylesheetSample.xsl Operation.xml TestWSNotificationExtension.java ContextPolicyTypeImpl.java
  • Environment:
    ESB 3.1.1, create from the trunk project exported the 04/02/2011

Attachments

  1. Zip Archive
    petals-se-kpi-1.2.1-SNAPSHOT-source.zip
    (50 kB)
    Frédéric Gardes
    Fri, 18 Feb 2011 - 15:06:09 +0100
  2. Zip Archive
    petals-se-kpi-1.2.1-SNAPSHOT.zip
    (19.31 MB)
    Frédéric Gardes
    Fri, 18 Feb 2011 - 15:06:09 +0100
  3. Zip Archive
    ws-notification-extension-1.2.2.1-SNAPSHOT-source.zip
    (82 kB)
    Frédéric Gardes
    Fri, 18 Feb 2011 - 15:02:24 +0100
  4. Java Archive File
    ws-notification-extension-1.2.2.1-SNAPSHOT.jar
    (51 kB)
    Frédéric Gardes
    Fri, 18 Feb 2011 - 15:02:24 +0100

Issue Links

Depends
 

Activity

Descending order - Click to sort in ascending order
Hide
Permalink
Frédéric Gardes added a comment - Thu, 21 Apr 2011 - 09:33:00 +0200

on test here...

Show
Frédéric Gardes added a comment - Thu, 21 Apr 2011 - 09:33:00 +0200 on test here...
Hide
Permalink
Frédéric Gardes added a comment - Fri, 18 Feb 2011 - 15:28:40 +0100

A sample of a su kpi with the new elements:
->a filter on the process type into the exchange
->a filter on the operation of the exchange
->a process policy to add the process type into the exchange (if not exists), and into the notifications (if not exists, to be compliant with the previous process type put into the xsl stylesheet)
->a context policy to add the operation (name and namespace) into the notifications

<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:MessageContentOperationDialect>http://www.ebmwebsourcing.com/wsnotification/operation</kpi:MessageContentOperationDialect>			<kpi:MessageContentOperationNamespace>http://orange.com/ros/services/newbrokerTSE/v1</kpi:MessageContentOperationNamespace>
        <kpi:MessageContentOperationName>createCustomer</kpi:MessageContentOperationName>

			<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>
                        <kpi:ProcessPolicyType>6</kpi:ProcessPolicyType>
		</jbi:consumes>
Show
Frédéric Gardes added a comment - Fri, 18 Feb 2011 - 15:28:40 +0100 A sample of a su kpi with the new elements: ->a filter on the process type into the exchange ->a filter on the operation of the exchange ->a process policy to add the process type into the exchange (if not exists), and into the notifications (if not exists, to be compliant with the previous process type put into the xsl stylesheet) ->a context policy to add the operation (name and namespace) into the notifications 
<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:MessageContentOperationDialect>http://www.ebmwebsourcing.com/wsnotification/operation</kpi:MessageContentOperationDialect>			<kpi:MessageContentOperationNamespace>http://orange.com/ros/services/newbrokerTSE/v1</kpi:MessageContentOperationNamespace>
        <kpi:MessageContentOperationName>createCustomer</kpi:MessageContentOperationName>

			<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>
                        <kpi:ProcessPolicyType>6</kpi:ProcessPolicyType>
		</jbi:consumes>
Hide
Permalink
Frédéric Gardes added a comment - Fri, 18 Feb 2011 - 15:02:24 +0100

The se-kpi used.
1) The source has been backported to the easy wsdl 2.3, instead of 2.4-SNAPSHOT, because of an inextricable error stack at the runtime under esb 3.1.1. So be careful on this new easy wsdl version during the integration. It's (I hope!) only due to bad downloaded snapshots (i.e. bad deployed snapshots today).
2) The snapshot version have a digit more, to isolate my developments.
3) The kpi JBI artifact is configured to be used with MySQL. The petals view files into the jar created is using c3p0 properties instead of jdbc properties too (curious..). So I "inject" manually this 4 files from the se-kpi 1.1.1 into this se-kpi 1.2.1-SNAPSHOT.

Show
Frédéric Gardes added a comment - Fri, 18 Feb 2011 - 15:02:24 +0100 The se-kpi used. 1) The source has been backported to the easy wsdl 2.3, instead of 2.4-SNAPSHOT, because of an inextricable error stack at the runtime under esb 3.1.1. So be careful on this new easy wsdl version during the integration. It's (I hope!) only due to bad downloaded snapshots (i.e. bad deployed snapshots today). 2) The snapshot version have a digit more, to isolate my developments. 3) The kpi JBI artifact is configured to be used with MySQL. The petals view files into the jar created is using c3p0 properties instead of jdbc properties too (curious..). So I "inject" manually this 4 files from the se-kpi 1.1.1 into this se-kpi 1.2.1-SNAPSHOT.

People

Dates

  • Created:
    Wed, 16 Feb 2011 - 14:01:05 +0100
    Updated:
    Thu, 21 Apr 2011 - 09:33:00 +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.