[
https://issues.apache.org/jira/browse/TUSCANY-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash updated TUSCANY-1500:
--------------------------------
Attachment: patch2
Here is patch2 for this JIRA. It enables the callback-id test in the build and
gets it working. Here's a very brief summary of the changes in this patch.
1. Rename CallBackIdTestCaseFIXME.java to CallBackIdTestCase.java. (NOTE: This
must be done manually before applying the patch, which contains an update to
CallBackIdTestCase.java.)
2. Change the class name for the test from CallBackIdTestCaseFIXME to
CallBackIdTestCase.
3. Change the test code where it was not using the correct spec APIs.
4. Various runtime changes to enable the correct passing of the callback ID on
requests
I am looking at the other failing callback tests and I will post further
patches to get them working.
> Many callback tests don't run
> -----------------------------
>
> Key: TUSCANY-1500
> URL: https://issues.apache.org/jira/browse/TUSCANY-1500
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-Next
> Environment: Windows XP
> Reporter: Simon Nash
> Assignee: Simon Nash
> Fix For: Java-SCA-Next
>
> Attachments: patch1, patch2
>
>
> The following itests are currently disabled in the build. If they are
> enabled by changing the name of the test class from xxxTest to xxxTestCase,
> they fail with various errors.
> callback-api
> callback-complex-type
> callback-id
> callback-set-callback
> callback-set-conversation
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
