GWT-SL(1.2) JRebel(5)

[Tapan Mokha]

When using GWTHandler & GileadRPCServiceExporter, changes to the RPC wrapped service class causes JRebel to reload the service class, leading handlerMap emptying(size=0) in GWTHandler.

Any one else run into the same issue, if yes, how to resolve this.

Currently as a stopgap measure, on a request if the handlerMap is empty, we recall afterPropertiesSet(), causing the handler registration to reoccur.

[George Georgovassilis]

Hi Tapan,

handlerMap should normally not be empty if indeed only the service class is replaced since there is no reason to re-initialise a GWTHandler instance. The only way this map could be empty is if JRebel also reinitialised GWTHandler, in which case you should find more things empty/defaulted than just the map. I have not worked with JRebel but it seems that there is some provision which handles Spring configurations and takes care of correct initialisations:

http://zeroturnaround.com/software/jrebel/jrebel-spring-integration/

--
You received this message because you are subscribed to the Google Groups "gwt-sl" group.
To view this discussion on the web, visit https://groups.google.com/d/msg/gwt-sl/-/PwFYNHx1nbwJ.
To post to this group, send an email to gwt...@googlegroups.com.
To unsubscribe from this group, send email to gwt-sl+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/gwt-sl?hl=en-GB.

[Tapan Mokha]

I could not agree with you more, But  "if indeed only the service class is replaced" the service classes in context are not the @Service classes but proxied(GileadRPCServiceExporter) services. Will look into the GWTHandler being reinitialised.

Thanks for the link(will look into it)

Tapan