selpia / gwteventservice

Automatically exported from code.google.com/p/gwteventservice
Other
0 stars 2 forks source link

Don't receives events #45

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

I have a bean on server side (not Servlet) that fires events using method 
bellow:

public void addEvent(AppEventWrapper e){
 EventRegistry reg = eventRegistryFactory.getInstance().getEventRegistry();                                                          
 reg.addEvent(d, e);
 //reg.addEventUserSpecific(e.getClientId(), e); Doesn't work two
 log.info("Application event register "+e);
}

This bean is indirectly used by Message Driven Beans to notify client side 
about proccess progress.

On cliente side the code is:

aRemoteListener = new RemoteEventListener() {           
 @Override
  public void apply(Event anEvent) {
   if (anEvent instanceof AppEventWrapper){
    AppEventWrapper e = (AppEventWrapper) anEvent;
    AppEvent event = e.getRealEvent();
    if (event instanceof ReportStatusEvent){
       eBus.fireEvent(new ReportStatusServerPushEvent((ReportStatusEvent) event));
    }
   }
 } 
};

RemoteEventService service = 
RemoteEventServiceFactory.getInstance().getRemoteEventService();        
service.addListener(aDomain, aRemoteListener);  

What is the expected output? What do you see instead?

Server and client works fine. But the send events aren't received  by client.

What version of the product are you using? On what operating system?
I'm using the last version.

Please provide any additional information below.

Original issue reported on code.google.com by smt...@gmail.com on 20 Apr 2012 at 6:06

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I detected the problem!
The problem is that the server compress the response with GZIP.

How we solve the problem, without disable GZIP compress?

Original comment by smt...@gmail.com on 20 Apr 2012 at 8:01

GoogleCodeExporter commented 9 years ago
The server is only allowed to use GZIP compression (or any other compression 
algorithm for that matter) if the client specifies that it supports it. The 
client sends this information along in an HTTP header like so 
"Accept-Encoding=gzip, deflate". Use an HTTP monitor (like Firebug or HttpFox 
in Firefox) to see what your client sends.

Original comment by marcel@frightanic.com on 12 Jul 2012 at 2:30

GoogleCodeExporter commented 9 years ago
Hi,

thank you Marcel for the response to smtrad.

@smtrad: Could you solve/work-around the problem? Large responses are 
automatically compressed with gzip by GWT-RPC. This is not triggered by 
GWTEventService.

Original comment by sven.strohschein@googlemail.com on 16 Jul 2012 at 5:57

GoogleCodeExporter commented 9 years ago
Set to invalid because it isn't an issue of GWTEventService and there is no 
response since several months

Original comment by sven.strohschein@googlemail.com on 3 Oct 2012 at 8:42