[sea_shankar]

Ahhh I see.  For our use case, we wanted to avoid creating the .proto files and the registering for each new "regular" pojos as we have a lot of custom Pojos.  I understand the need to do the .proto (+ registering) if we are doing some custom server tasks and the server needs to understand what these are (like in the swiss data grid example)  But is there a way to have compatibility mode on( which is required to do the server tasks with "custom" pojos) and still have other pojos (that doesn't require them to have all the proto stuff and registering because we aren't doing anything special with them, simply putting them in cache) be serialized to bytes as it would on compatibility off? I don't care to have "regular" pojos stored as pojos on the server.  I wrongly thought the stock marshaller would do this automatically.  Not sure if this makes sense.

[galder.zamarreno]

Hmmm, guess you mean if there's a way for compatibility mode to be lazy instead of eager? Compatibility mode is currently eager and it's not configurable. This is likely to change.

If you want to keep other POJOs working as if compatibility was off, the easiest thing would be to store them in a separate cache where compatibility mode is disabled.

[sea_shankar]

Yes, exactly!