Hi Joscha,
Thanks for reporting this issue. It is a regression introduced just before 2.1 M6. We will fix it tomorrow and release a 2.1 M7 including the fix right after so people don’t have to wait for 2.1 RC1 next month or rely on snapshots. Best regards, Jerome -- Restlet ~ Founder and Technical Lead ~ <http://www.restlet.org/> http://www.restlet.org Noelios Technologies ~ <http://www.noelios.com/> http://www.noelios.com De : Joscha Feth [mailto:jos...@feth.com] Envoyé : mardi 23 août 2011 17:36 À : discuss@restlet.tigris.org Objet : Restlet 2.1-M6 and GWT 2.3.0 with "Unhandled exception type IOException" According to the release notes of Restlet 2.1-M6 (http://www.restlet.org/documentation/2.1/jse/changes) it should be compatible with GWT 2.3.0, however when using M6 together with 2.3.0 the generated *ProxyImpl.java classes contain two errors: -- 8< -- .... if(response.isEntityAvailable()){ if(MediaType.APPLICATION_JAVA_OBJECT_GWT.equals(response.getEntity().getMediaType())){ result = new ObjectRepresentation<org.xbeat.billbeat.model.transactions.ExchangeTransaction>( --> response.getEntity().getText(), (SerializationStreamFactory) ExchangeTransactionProxyImpl.this, false) .getObject(); } else { --> throw new IOException("Can't parse the enclosed entity"); } } .... -- 8< -- I marked the problems with "-->". one uncatched IOException from getText() and one thrown even though the "Uniform" interface does not allow for this. Anyone else seeing this problem? Kind regards, Joscha Feth ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2828949