Tuscany
  1. Tuscany
  2. TUSCANY-3482

OASIS fixes to make JCA_8005 and JCA_8007 work

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: Java-SCA-2.0-M4
    • Fix Version/s: Java-SCA-2.x
    • Labels:
      None
    • Environment:
      All

      Description

      testDummy(client_javacaa.JCA_8005_TestCase)
      SEVERE: = Unable to match the endpoint reference
      (@1135890)EndpointReference: URI =
      TEST_JCA_8005Component1#reference(reference2) WIRED_TARGET_NOT_FOUND
      Target = (@31992690)Endpoint: URI = TEST_JCA_8005Component3
      [Unresolved] with the policy of the service to which it refers,
      matching process was Match policy of (@1135890)EndpointReference: URI
      = TEST_JCA_8005Component1#reference(reference2) WIRED_TARGET_NOT_FOUND
      Target = (@31992690)Endpoint: URI = TEST_JCA_8005Component3
      [Unresolved] to (@28138822)Endpoint: URI =
      TEST_JCA_8005Component3#service-binding(Service1/Service1) No match
      because there are unresolved intents
      [

      {http://docs.oasis-open.org/ns/opencsa/scatests/200903}

      testIntent2]

      testDummy(client_javacaa.JCA_8007_TestCase)
      SEVERE: = Unable to match the endpoint reference
      (@19896612)EndpointReference: URI =
      TEST_JCA_8007Component1#reference(reference1) WIRED_TARGET_NOT_FOUND
      Target = (@32453138)Endpoint: URI = TEST_JCA_8007Component2
      [Unresolved] with the policy of the service to which it refers,
      matching process was Match policy of (@19896612)EndpointReference:
      URI = TEST_JCA_8007Component1#reference(reference1)
      WIRED_TARGET_NOT_FOUND Target = (@32453138)Endpoint: URI =
      TEST_JCA_8007Component2 [Unresolved] to (@12612903)Endpoint: URI =
      TEST_JCA_8007Component2#service-binding(Service5Intents/Service5Intents)
      No match because there are unresolved intents
      [

      {http://docs.oasis-open.org/ns/opencsa/scatests/200903}

      testIntent4]

      CAA otest doesn't define a policy set for these intent. It only provides policy sets to intents 3 and 5 (possibly on purpose). It looks like the builder is not promoting intents properly. Needs more investigation.

        Activity

        Hide
        ant elder added a comment -

        After all the recent changes this is now working

        Show
        ant elder added a comment - After all the recent changes this is now working
        Hide
        ant elder added a comment -

        Add tuscany has that change but JCA_8007 is still failing for some reason

        Show
        ant elder added a comment - Add tuscany has that change but JCA_8007 is still failing for some reason
        Hide
        ant elder added a comment -

        JAVA-196 resolved with the following:
        [15:44] Mike Edwards: Mike Edwards moves to resolve Issue 196 by adding the following to the definitions.xml file in the Contribution JCA_General_POJO:
        Mike Edwards: <policySet name="PolicySet4" provides="test:testIntent4" appliesTo="//binding.ws">
        <!-- This policy intentionally left blank -->

        </policySet>

        Show
        ant elder added a comment - JAVA-196 resolved with the following: [15:44] Mike Edwards: Mike Edwards moves to resolve Issue 196 by adding the following to the definitions.xml file in the Contribution JCA_General_POJO: Mike Edwards: <policySet name="PolicySet4" provides="test:testIntent4" appliesTo="//binding.ws"> <!-- This policy intentionally left blank --> </policySet>
        Hide
        Simon Laws added a comment - - edited

        Today I spotted that the rutime code to process the @costrains attribute on an intent is not present. I added it and 8005 now passes. it interesting that OASIS created a test where an intent is attached to reference in the various allowable ways but the intent only constrains sca:implementation. The runtime now removes the intent and the test passes. Need to further raise this with OASIS.

        Show
        Simon Laws added a comment - - edited Today I spotted that the rutime code to process the @costrains attribute on an intent is not present. I added it and 8005 now passes. it interesting that OASIS created a test where an intent is attached to reference in the various allowable ways but the intent only constrains sca:implementation. The runtime now removes the intent and the test passes. Need to further raise this with OASIS.
        Hide
        Simon Laws added a comment -

        Change JIRA title as OASIS issues have now been opened

        Show
        Simon Laws added a comment - Change JIRA title as OASIS issues have now been opened
        Hide
        Simon Laws added a comment -
        Show
        Simon Laws added a comment - 8005 issue raised as http://www.osoa.org/jira/browse/JAVA-195 8007 issue raised as http://www.osoa.org/jira/browse/JAVA-196
        Hide
        Raymond Feng added a comment -

        Please note that OASIS need to change the namespace to be:

        http://docs.oasis-open.org/ns/opencsa/scatests/200912

        Show
        Raymond Feng added a comment - Please note that OASIS need to change the namespace to be: http://docs.oasis-open.org/ns/opencsa/scatests/200912
        Hide
        Simon Laws added a comment -

        Change to be in the OASIS change required category

        Show
        Simon Laws added a comment - Change to be in the OASIS change required category
        Hide
        Simon Laws added a comment -

        I'm changing my mind about this one. There seems to be several problems with the test (8005 at least) itself.

        1/ The comment at the top of the test case (JCA_8005_TestCase) is wrong as it's apparently a +ve test

        • This testcase is expected to fail

        2/ The three references of service1GoodIntent are all defined with testIntent2 and this intent doesn't have a policy set so out runtime raises an error

        3/ If were to provide a policy set then we have a position where the reference has an intent/policy set but the service to which it is wired does not. If our policy set has no policies in it then I guess we could judge that this does intersect with the lack of policy sets on the service. But I feel I'm on shaky ground here.

        Show
        Simon Laws added a comment - I'm changing my mind about this one. There seems to be several problems with the test (8005 at least) itself. 1/ The comment at the top of the test case (JCA_8005_TestCase) is wrong as it's apparently a +ve test This testcase is expected to fail 2/ The three references of service1GoodIntent are all defined with testIntent2 and this intent doesn't have a policy set so out runtime raises an error 3/ If were to provide a policy set then we have a position where the reference has an intent/policy set but the service to which it is wired does not. If our policy set has no policies in it then I guess we could judge that this does intersect with the lack of policy sets on the service. But I feel I'm on shaky ground here.

          People

          • Assignee:
            Unassigned
            Reporter:
            Simon Laws
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development