2025-11-24 04:22:12
Topic starter
Notifications
Clear all
0
Hello all,
I’m running into a strange compilation issue during bootstrap on AZ-neo-3.12q.
Only on my local, the generated code is giving me char[] instead of byte[] for patternDefinition, and that leads to these errors:
The errors come from:
-
RecurringDataHelper -
SimpleRecurrencePatternHelper -
and the model rows (
SiteRecurrenceDataRow,SiteRsrcRecurrenceDataRow)
What’s confusing is — my teammates don’t see this issue. Their codegen still produces byte[], but mine suddenly switched to char[].
Has anyone seen this before?
Is there some local codegen/XSD/JAXB cache or config that could cause datatype differences during generation?
Any pointers on where to check or what to clean/reset would really help. 🙏
here are the logs
injectCode:
compile:
[javac] Compiling 6030 source files to C:\views\AZ-neo-3.12q\tomcat\deploy\one\WEB-INF\one_modules\one.jar
[javac] C:\views\AZ-neo-3.12q\server\src\com\transcendsys\platform\server\vc\helper\RecurringDataHelper.java:177: error: incompatible types: char[] cannot be converted to byte[]
[javac] patternDefinition = siteRecurrenceDataRow.getPatternDefinition();
[javac] ^
[javac] C:\views\AZ-neo-3.12q\server\src\com\transcendsys\platform\server\vc\helper\RecurringDataHelper.java:553: error: incompatible types: byte[] cannot be converted to char[]
[javac] row.setPatternDefinition(getSimpleRecurrencePatternBytes(simpleRecurrencePattern));
[javac] ^
[javac] C:\views\AZ-neo-3.12q\server\src\com\transcendsys\platform\server\timeline\populator\SimpleRecurrencePatternHelper.java:42: error: incompatible types: char[] cannot be converted to byte[]
[javac] byte[] xmlBytes = row.getPatternDefinition();
[javac] ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use or override a deprecated API that is marked for removal.
[javac] Note: Recompile with -Xlint:removal for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] Note: Some messages have been simplified; recompile with -Xdiags:verbose to get full output
[javac] 3 errors
BUILD FAILED
C:\views\INSTAN~1\ib-branches\Neo3.10-rb\build.xml:1340: The following error occurred while executing this line:
C:\views\INSTAN~1\ib-branches\Neo3.10-rb\build.xml:1361: The following error occurred while executing this line:
C:\views\AZ-neo-3.12q\install-staging\build.xml:1422: The following error occurred while executing this line:
C:\views\AZ-neo-3.12q\install-staging\build.xml:2827: The following error occurred while executing this line:
C:\views\AZ-neo-3.12q\install-staging\build.xml:2874: The following error occurred while executing this line:
C:\views\AZ-neo-3.12q\server\build.xml:211: The following error occurred while executing this line:
C:\views\AZ-neo-3.12q\server\build.xml:217: The following error occurred while executing this line:
C:\views\AZ-neo-3.12q\server\build.xml:993: The following error occurred while executing this line:
C:\views\AZ-neo-3.12q\server\PlatformCoreModels\build.xml:168: The following error occurred while executing this line:
C:\views\AZ-neo-3.12q\install-staging\build-macros.xml:43: Compile failed; see the compiler error output for details
-------------------------
FAILED
-------------------------
javamk Topic starter
2025-12-04 08:17:19
Just an update I tried multiple approaches, and as a workaround I used an already compiled jar. It worked initially but later broke some functionality. Finally, I reinstalled Oracle and bootstrapped again, which resolved the issue.
1 Answer
0
2025-11-24 13:48:29
@javamk - Have you performed a clean build to test whether that fixes the issue? You can also try "Get Revision" then "Force Operation" on both of these files. Then attempt to build again. This will ensure you have the latest file from Perforce. If it still fails, I would look to perform a clean build from root. There should not be any local codegen/XSD/JAXB cache or config that is causing this issue and there hasn't been a change to these files in quite sometime, so something odd definitely is causing an issue.
@jcourter Thanks for the suggestions. Yes, I’ve already tried a clean build multiple times, including removing all generated folders. I also did a Get Revision and Force Operation on the affected files to make sure I have the latest versions from Perforce. I also performed a full clean build from root, but the issue still persists only on my local setup. Other teammates are not seeing this problem, which makes it more confusing. We even tried a fresh bootstrap and created a new build spec, but the same type-mismatch error (char[] vs byte[]) appears each time. After more debugging, it looks like the root cause is that somehow the BLOB column is getting created as CLOB in my local database, and because the platform generates DAO getters/setters directly from the DB, the generated code ends up with char[] instead of byte[]. That mismatch is causing the compilation failures. I’m still not sure why only my local DB is creating it as CLOB, but that seems to be the source of the issue.
