Using a 502 project using OTDs generated from XSDs that have xs:any nodes give compilation errors in 503 because of some node names that are incorrect. Also produces a codegen error when trying to access the class name in package.

(Doc ID 1028370.1)

Last updated on JUNE 16, 2004

Applies to:

Sun SeeBeyond Integrated Composite Application Network (ICAN) - Version: 5.0.3 and later
Information in this document applies to any platform.

Symptoms

Using a 502 project using XSDs that have xs:any nodes give compilation errors in 503 because of some node names that are incorrect. Also produces a codegen error when trying to access the class name in package. This is from the ide.log file..
ICAN5.[12 Apr 2004 16:05:07,588] WARN (AntTasksWrapperImpl.java:182) - [CODEGEN_COMPILE] C:\ican503\edesigner\temp\jcdMark_DPTest4_1081811086127\newjcd1_ejb\jcdMark\newjcd.java:16: cannot resolve symbol
ICAN5.[12 Apr 2004 16:05:07,808] WARN (AntTasksWrapperImpl.java:182) - [CODEGEN_COMPILE] symbol : class AES
ICAN5.[12 Apr 2004 16:05:07,808] WARN (AntTasksWrapperImpl.java:182) - [CODEGEN_COMPILE] location: package svcRequestBDP

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms