diff options
Diffstat (limited to 'tags/java/sca/1.5.1/vtest/assembly/ctypefile/src/test/java/org/apache/tuscany/sca/vtest/assembly/ctypefile/CompomnentTypeFileTestCase.java')
| -rw-r--r-- | tags/java/sca/1.5.1/vtest/assembly/ctypefile/src/test/java/org/apache/tuscany/sca/vtest/assembly/ctypefile/CompomnentTypeFileTestCase.java | 183 |
1 files changed, 183 insertions, 0 deletions
diff --git a/tags/java/sca/1.5.1/vtest/assembly/ctypefile/src/test/java/org/apache/tuscany/sca/vtest/assembly/ctypefile/CompomnentTypeFileTestCase.java b/tags/java/sca/1.5.1/vtest/assembly/ctypefile/src/test/java/org/apache/tuscany/sca/vtest/assembly/ctypefile/CompomnentTypeFileTestCase.java new file mode 100644 index 0000000000..d2d2257277 --- /dev/null +++ b/tags/java/sca/1.5.1/vtest/assembly/ctypefile/src/test/java/org/apache/tuscany/sca/vtest/assembly/ctypefile/CompomnentTypeFileTestCase.java @@ -0,0 +1,183 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. + */ + +package org.apache.tuscany.sca.vtest.assembly.ctypefile; + +import junit.framework.Assert; + +import org.apache.tuscany.sca.vtest.utilities.ServiceFinder; +import org.junit.AfterClass; +import org.junit.BeforeClass; +import org.junit.Test; + +/** + * + */ +public class CompomnentTypeFileTestCase { + + //protected static String compositeName = "typefile.composite"; + protected static AService aService = null; + protected static BService bService2 = null; + protected static CService cService = null; + protected static DService dService = null; + + //@BeforeClass + public static void init(String compositeName) throws Exception { + try { + System.out.println("Setting up"); + ServiceFinder.init(compositeName); + //aService = ServiceFinder.getService(AService.class, "AComponent/AService"); + //bService2 = ServiceFinder.getService(BService.class, "BComponent2/BService"); + } catch (Exception ex) { + ex.printStackTrace(); + } + } + + //@AfterClass + public static void destroy() throws Exception { + + System.out.println("Cleaning up"); + ServiceFinder.cleanup(); + + } + + /** + * Lines 435-439: + * <p> + * Step two covers the cases where introspection of the implementation is + * not possible or where it does not provide complete information and it + * involves looking for an SCA component type file. Component type + * information found in the component type file must be compatible with the + * equivalent information found from inspection of the implementation. + * <p> + * Lines 441-444: + * <p> + * In the ideal case, the component type information is determined by + * inspecting the implementation, for example as code annotations. The + * component type file provides a mechanism for the provision of component + * type information for implementation types where the information cannot be + * determined by inspecting the implementation. + */ + @Test + public void typeFile1() throws Exception { + init("typefile.composite"); + aService = ServiceFinder.getService(AService.class, "AComponent/AService"); + bService2 = ServiceFinder.getService(BService.class, "BComponent2/BService"); + Assert.assertSame("SomeStateFromB", aService.getState()); + destroy(); + } + + /** + * Lines 439-449: + * <p> + * The component type file can specify partial information, with the + * remainder being derived from the implementation. + * <p> + * The first test makes use of the reference to b which is provided by the + * type file. The second test makes use of the reference to b2 which is + * provided via annotation + */ + @Test + public void typeFile2() throws Exception { + init("typefile.composite"); + aService = ServiceFinder.getService(AService.class, "AComponent/AService"); + bService2 = ServiceFinder.getService(BService.class, "BComponent2/BService"); + Assert.assertSame("SomeStateFromB", aService.getState()); + Assert.assertSame("SomeStateFromB", aService.getState2()); + destroy(); + } + + /** + * Lines 450-451: + * <p> + * The componentType element can contain Service elements, Reference + * elements and Property elements. + */ + @Test + public void typeFile3() throws Exception { + init("typefile.composite"); + aService = ServiceFinder.getService(AService.class, "AComponent/AService"); + bService2 = ServiceFinder.getService(BService.class, "BComponent2/BService"); + Assert.assertEquals("compositeValue", aService.getBProperty()); + destroy(); + } + + public void typeFile31() throws Exception { + init("typefile.composite"); + aService = ServiceFinder.getService(AService.class, "AComponent/AService"); + bService2 = ServiceFinder.getService(BService.class, "BComponent2/BService"); + Assert.assertEquals("componentTypeValue", bService2.getSomeProperty()); + destroy(); + } + + /** + * Lines 2204-2205: + * <p> + * A constrainingType can be applied to an implementation. In this case, + * the implementation's componentType has a constrainingType attribute set to + * the QName of the constrainingType. + * <p> + * ASM40002 + * <p> + * If present, the @constrainingType attribute of a <componentType/> element + * MUST reference a <constrainingType/> element in the Domain through its QName. + * <p> + * Description of how the OSOA function differs from the OASIS function: + * <p> + * The OASIS spec explicitly requires the <constrainingType/> element, + * whereas the OSOA spec implies the <constrainingType/> element is needed. + * <p> + */ + @Test + public void ASM40002_positive() throws Exception { + System.out.println("Running ASM40002 positive test"); + init("constrainingtype.composite"); + cService = ServiceFinder.getService(CService.class, "CComponent/CService"); + cService.getSomeProperty(); + destroy(); + } + + /** + * Lines 2204-2205: + * <p> + * A constrainingType can be applied to an implementation. In this case, + * the implementation's componentType has a constrainingType attribute set to + * the QName of the constrainingType. + * <p> + * ASM40002 + * <p> + * If present, the @constrainingType attribute of a <componentType/> element + * MUST reference a <constrainingType/> element in the Domain through its QName. + * <p> + * Description of how the OSOA function differs from the OASIS function: + * <p> + * The OASIS spec explicitly requires the <constrainingType/> element, + * whereas the OSOA spec implies the <constrainingType/> element is needed. + * <p> + */ + @Test + public void ASM40002_negative() throws Exception { + System.out.println("Running ASM40002 negative test"); + init("noconstrainingtype.composite"); + dService = ServiceFinder.getService(DService.class, "DComponent/DService"); + dService.getSomeProperty(); + destroy(); + } + +} |