Since you seem passionate about precise definitions for technical terms, maybe you could point us to third-party definitions which match your understanding? Start with sources for what "compilation" and "tokenization" mean as you understand them?

You are thinking of the typical design of a BASIC system in the 80's. Keywords were stored as "tokens" (numbers) but expressions were usually stored as space-stripped strings. There would be an edit-time syntax check (combined with the tokenization) to check if the expressions were syntactical and only in places where they were allowed). Some designs did use tokens for the expressions too.

There was almost no syntax involved and essentially zero compilation work.

Java compilers do a lot more than that. They actually compile to a real (abstract) machine and they do real compiler things (proper parsing, maintenance of namespaces, type checks). They usually don't do any optimization because that will happen at run-time anyway -- but that doesn't make them "not compilers".

> That's pretty much the definition of tokenized

Oh boy. It’s rare to see such confidence mixed with such nonsense.