I'm homing in on the 9008 failure, and someone may be able to help me
shortcut my understanding.
The expected output of the test is ...
config.output[0] = "JCA_9008 request service1 operation1
invoked getService" +
" expected IllegalArgumentException
received for 0..n ref" +
" expected IllegalArgumentException
received for invalid businessInterface" +
" expected IllegalArgumentException
received for invalid reference name" +
" expected null Service for unwired
0..1 reference" +
" expected non-null Service for wired
1..1 reference" +
" service2 operation1 invoked"
but I see deviation from this output here in Service1CCgetServiceImpl
at line 69
where the call to getService erroneously succeeds instead of entering
the catch block
try {
componentContext.getService(Service2.class, "requiredRef");
responseAccumulator += " did not get
IllegalArgumentException
for invalid businessInterface";
} catch ( IllegalArgumentException e ) {
responseAccumulator += " expected
IllegalArgumentException received
for invalid businessInterface";
} catch ( Exception e ) {
responseAccumulator += " other unexpected exception
received for
invalid businessInterface: " + e.toString();
} // end try
Kelvin.
On Mon, Jul 19, 2010 at 11:57 AM, kelvin goodson
<[email protected]> wrote:
> After my second reboot of the morning I see a better picture on the
> JCA tests ...
>
> Failed tests:
> testDummy(client_javacaa.JCA_9013_TestCase)
> testDummy(client_javacaa.JCA_9016_TestCase)
> testDummy(client_javacaa.JCA_9011_TestCase)
> testDummy(client_javacaa.JCA_3013_TestCase)
> testDummy(client_javacaa.JCA_9009_TestCase)
> testDummy(client_javacaa.JCA_7006_TestCase)
> testDummy(client_javacaa.JCA_11010_TestCase)
> testDummy(client_javacaa.JCA_11009_TestCase)
> testDummy(client_javacaa.JCA_9006_TestCase)
> testDummy(client_javacaa.JCA_9010_TestCase)
> testDummy(client_javacaa.JCA_7004_TestCase)
> testDummy(client_javacaa.JCA_11012_TestCase)
> testDummy(client_javacaa.JCA_7005_TestCase)
> testDummy(client_javacaa.JCA_8011_TestCase)
> testDummy(client_javacaa.JCA_11015_TestCase)
> testDummy(client_javacaa.JCA_7002_TestCase)
> testDummy(client_javacaa.JCA_8007_TestCase)
> testDummy(client_javacaa.JCA_9012_TestCase)
> testDummy(client_javacaa.JCA_7003_TestCase)
> testDummy(client_javacaa.JCA_11011_TestCase)
> testDummy(client_javacaa.JCA_11014_TestCase)
> testDummy(client_javacaa.JCA_10013_TestCase)
> testDummy(client_javacaa.JCA_7001_TestCase)
> testDummy(client_javacaa.JCA_9008_TestCase)
> testDummy(client_javacaa.JCA_11013_TestCase)
> testDummy(client_javacaa.JCA_3014_TestCase)
> testDummy(client_javacaa.JCA_11016_TestCase)
> testDummy(client_javacaa.JCA_10006_TestCase)
>
> Tests run: 214, Failures: 28, Errors: 0, Skipped: 107
>
> And 11017 wasn't amongst the failures
>
>
> This morning I ran the ASM tests and got a huge number of failures,
> which after a reboot reduced to just 3 IIRC. My environment seems
> quite fragile. A second run of the JCA tests gives the same results,
> so it doesn't seem to be that the after-effect issues are a direct
> result of running the tests themselves.
>
> Kelvin.
>
>
> On Mon, Jul 19, 2010 at 11:53 AM, ant elder <[email protected]> wrote:
>> On Mon, Jul 19, 2010 at 11:15 AM, kelvin goodson
>> <[email protected]> wrote:
>>> I'm trying to look into these, and currently seeing a 10 minute + hang
>>> on JCA_11017 with ...
>>>
>>
>> I don't see any hang in JCA_11017
>>
>> I've fixed an incorrect error message in the JCI tests and that suite
>> all passes ok for me now, and the WS suite is passing cleanly too. For
>> the others I'm seeing lots of fails in JCA and Policy as have already
>> been posted to this thread, and down to just 4 fails in Assembly, two
>> look like policy things (8014 and 12006) and two are interface
>> matching (12007 and 12008). I'll go look at the interface matching
>> ones.
>>
>> 8014 org.oasisopen.sca.ServiceRuntimeException:
>> [Composite: {http://docs.oasis-open.org/ns/opencsa/sca/200912},
>> Component: TestComponent2, Service: Service1] -
>> The intent
>> {http://docs.oasis-open.org/ns/opencsa/sca/200912}confidentiality.transport
>> associated with policy subject
>> (@24981262)Endpoint: URI =
>> TestComponent2#service-binding(Service1/Service1) has no matching
>> policy set
>>
>> 12006
>> org.oasisopen.sca.ServiceRuntimeException: [Composite:
>> {http://docs.oasis-open.org/ns/opencsa/sca/200912}, Component:
>> TestComponent1, Service: Service1] - The intent
>> {http://docs.oasis-open.org/ns/opencsa/scatests/200903}Fred associated
>> with policy subject (@8374450)Endpoint: URI =
>> TestComponent1#service-binding(Service1/Service1) has no matching
>> policy set
>>
>> 12007
>> org.oasisopen.sca.ServiceRuntimeException: [Composite:
>> {http://docs.oasis-open.org/ns/opencsa/sca/200912}, Component:
>> TestComponent1, Composite:
>> {http://docs.oasis-open.org/ns/opencsa/scatests/2009032}TestComposite5,
>> Component: TestComposite5TestComponent1] -
>> [ASM50004,JCA30002,JCI80001] Component service interface incompatible
>> with implementation service interface: Component =
>> TestComposite5TestComponent1 Service = Service1 Operations called
>> operation2 are not compatible Operation argument types source =
>> {http://www.w3.org/2001/XMLSchema}int target =
>> {http://www.w3.org/2001/XMLSchema}string don't match for output types
>>
>>
>> 12008
>> org.oasisopen.sca.ServiceRuntimeException: [Composite:
>> {http://docs.oasis-open.org/ns/opencsa/sca/200912}, Component:
>> TEST_ASM_12008TestComponent1, Composite:
>> {http://docs.oasis-open.org/ns/opencsa/scatests/2009032}TestComposite5,
>> Component: TestComposite5TestComponent1] -
>> [ASM50004,JCA30002,JCI80001] Component service interface incompatible
>> with implementation service interface: Component =
>> TestComposite5TestComponent1 Service = Service1 Operations called
>> operation2 are not compatible Operation argument types source =
>> {http://www.w3.org/2001/XMLSchema}int target =
>> {http://www.w3.org/2001/XMLSchema}string don't match for output types
>>
>> ...ant
>>
>
