/******************************************************************************
 * Copyright (c) ETSI 2017.
 *
 * This file is subject to copyrights owned by ETSI. Non-exclusive permission
 * is hereby granted, free of charge, to copy, reproduce and amend this file
 * under the following conditions: It is provided "as is", without warranty of any
 * kind, expressed or implied.
 * 
 * ETSI shall never be liable for any claim, damages, or other liability arising
 * from its use or inability of use.This permission does not apply to any documentation
 * associated with this file for which ETSI keeps all rights reserved. The present
 * copyright notice shall be included in all copies of whole or part of this
 * file and shall not imply any sub-license right.
 *
 * Modified by: Adrien Kirjak
 *
 ** @version  0.0.1
 ** @purpose  1:6.2.9, Verify that an error is generated when a message port type definition contains no message types
 ** @verdict  pass reject
 *****************************************************************/

// The following requirements are tested:
// Each port type definition shall have one or more lists indicating the allowed collection of 
// (message) types ... with the allowed communication direction.

module NegSem_060209_CommunicationPortTypes_004 {

	type record MyType1 {
        integer f1,
        charstring f2
    }

	type record MyType2 {
	    integer g1,
	    charstring g2
	}

	type record MyType3 {
	    boolean h1,
        MyType3 h2 optional
	}
	
    type port MyMessagePortTypeOne message {
       // address MyType1;
       // map param (in integer p1, inout MyType2 p2);
       // unmap param (in MyType3 p1, out integer p2);
    } with {extension "internal"}

}
