When I work from a very large IDL schema, the Java code generated includes a schema JSON literal that exceeds the length of the maximum allowed literal string (65535 characters).
This creates weird Maven errors like: [ERROR] ...FooProtocol.java:[13,89] constant string too long.
It might seem a little crazy, but a 64-kilobyte JSON protocol isn't outrageous at all for some of the more involved data structures, especially if we're including documentation strings etc.
I believe the fix should be a bit more sensitivity to the length of the JSON literal (and a willingness to split it into more than one literal, joined by +), but I haven't figured out where that change needs to go. Has anyone else encountered this problem?