ServerMarshallingFactoryImpl keeps being generated differently

[hilco]

Hi all,

I have separated the client and server code into different projects. Unfortunately, ServerMarshallingFactoryImpl is generated during the execution of gwt-maven-plugin when compiling the client code. It needs to be available to the server code, though, so it must be copied or the server code must depend on the client code. Having the server code depend on the client code would mean a substantial increase in build time when working on server code so I would like to avoid that.

So I thought I would simply detect any changes in ServerMarshallingFactoryImpl and abort the build so I could copy it (actually, the build does the copying :-) ). Most of the time there should be no changes so that would work well.

Except that ServerMarshallingFactoryImpl changes every time I run the build. :-( It seems to be just the order of the code at the top: the *Marshaller fields and the marshallers.put(...) lines. Is there any way to prevent this reordering from happening?

Cheers,

Hilco

[hilco]

I thought -Dgwt.compiler.localWorkers=1 might help, but no, the order still changes.

[csa]

Hi Hilco,

There's not currently a way to guarantee the ordering of fields in the emitted marshalling code. Can you create a JIRA for us? An alternative you have in the meantime is to use dynamic marshalling during development (depending on the Errai version you are using, dynamic marshalling should be active by default when running in GWT's DevMode).

You can activate it with the following system property: errai.marshalling.use_static_marshallers=false

This should at least free you from having to copy the ServerMarshallingFactoryImpl during fast development cycles. When compiling for production though we recommend to use static marshallers.

Cheers,

Christian

[hilco]

Done, see ERRAI-570.