Hi all,
For those who already reviewed the version from yesterday, I’ve updated the
document again, trying to reduce the scope for 2.2 to a maximum to really have
a shorter release cycle this time (6 months) and mention aspects I forgot such
as the Guice extension and NIO connector
Hello list,
I am using Restlet 2.1-M5 (as I need GWT support and 2.0.8 does not have
support for GWT 2.2.0 and 2.1-M6/SNAPSHOT seems to be broken for GWT
entirely).
Until yesterday everything worked out fine, but I am hitting some nasty
stack overflows today:
-- 8 --
Server Error/pre/ph3Caused
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 --
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
As always, SSL configuration is always an adventure. I was testing a
configuration UCC certificate (multiple subdomains) with a
Restlet-based application and after quite a bit of struggles, I was
able to get it to work. The trouble turned out to be with the
certificate and once it was generated
Hello list,
is there any way to ignore a specific field (like the @*JsonIgnore *annotation
in Jackson) of an entity or use a different serializer with additional
options when using GWT serialization?
When detaching an object from JDO there is an jdoDetachedState added which
contains an Object of
Even if I factor out an interface without the annotations and return this in
the according ServerResource, it seems as if the GWT serializer still
serializes protected fields on the implementation. Has anyone else seen
this?
Cheers,
Joscha
On Wed, Aug 24, 2011 at 04:47, Joscha Feth
7 matches
Mail list logo
