Problem Product Name: VisiBroker for Java Product Version: 6.5 Product Component: IDL2JAVA compiler Platform/OS version: All JDK: 1.4.2_05 Patch Level: VisiBroker Service Pack 13 and below The VisiBroker idl2java compiler did not resolve to the most basic type for a complex idl datatype. The error scenario with a snippet of IDL, VisiBroker generated stub and expected output(compiled with JacORB) are described below. The error is highlighted in bold. IDL typedef NameValue Parameter; typedef NameValueSeq ParameterSeq; any action(in MOidpair mo,in ActionName name, inout ParameterSeq parameters, in Session session) raises (UnsupportedQoS, NotDefined, NotAccepted, SecurityViolation, ProcessingFailure); VisiBroker idl2java output public abstract Any action(MOidpair mo, String name, ParameterSeqHolder parameters, Session session) throws UnsupportedQoS, NotDefined, NotAccepted, SecurityViolation, ProcessingFailure; JacORB idl2java output public abstract Any action(MOidpair mo, String name, NameValueSeqHolder parameters , Session session) throws SecurityViolation, UnsupportedQoS, ProcessingFailure, NotDefined, NotAccepted; IDL2JAVA Specification Both IDL2JAVA 1.1 and 1.2 versions of specification have similar view with regard to the resolution of complex type. In version 1.2, it is on page 78, Chapter 1.18.2 In version 1.1, it is on page 74, Chapter 2.16.2 The specification states the following: Typedefs for types that are neither arrays nor sequences are "unwound" to their original type until a simple IDL type or user-defined IDL type (of the non typedef variety) is encountered. Holder classes are generated for sequence and array typedefs only. The "unwound" type"s Holder class is used for the other cases. No holder class is generated for a typedef of a typedef. Resolution A defect CR8956 has been filed. The fix is included in VisiBroker 6.5 Service Pack 14. References IDL2JAVA 1.1 Specification IDL2JAVA 1.2 Specification
↧