Re: Restlet & GWT: ignore fields?

2011-08-23 Thread Joscha Feth 
The answers are here:
http://code.google.com/intl/hu-HU/webtoolkit/doc/latest/DevGuideServerCommunication.html#DevGuideSerializableTypesand
here:
http://gwt-code-reviews.appspot.com/47807 and here:
http://timepedia.blogspot.com/2009/04/google-appengine-and-gwt-now-marriage.html

In short: JDO enhanced classes with detachable=true can not be received
correctly by GWT without additional ugly workarounds, even if the Restlet
GWT Converter provides the "correct" representation.

On Wed, Aug 24, 2011 at 07:06, Joscha Feth  wrote:

> 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  wrote:
>
>> 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 type javax.jdo.identity.StringIdentity and this can
>> not be deserialized on the client side...
>>
>> Kind regards,
>> Joscha Feth
>>
>
>

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2829300

Re: Restlet 2.1-M6 and GWT 2.3.0 with "Unhandled exception type IOException"

2011-08-23 Thread Joscha Feth 
Awesome! Thank you very much Jerome!


On Tue, Aug 23, 2011 at 17:36, Joscha Feth  wrote:

> 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,
>

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2829285

Re: Restlet & GWT: ignore fields?

2011-08-23 Thread Joscha Feth 
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  wrote:

> 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 type javax.jdo.identity.StringIdentity and this can
> not be deserialized on the client side...
>
> Kind regards,
> Joscha Feth
>

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2829284

Restlet & GWT: ignore fields?

2011-08-23 Thread Joscha Feth 
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 type javax.jdo.identity.StringIdentity and this can
not be deserialized on the client side...

Kind regards,
Joscha Feth

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2829260

sslServerAlias use?

2011-08-23 Thread Alex Milowski 
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 properly, everything worked the
way I thought it would.

During my experimentation, I tried setting "sslServerAlias" as a
parameter and got this exception:

   Javax.net.ssl.SSLHandshakeException: no cipher suites in common

I wouldn't expect that to happen.  In fact, since the keystore has
only one alias, it shouldn't matter whether the sslServerAlias is set
or not as long as when it is set, it matches the alias.

This seem like a bug.

--Alex Milowski

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2829012

RE: Restlet 2.1-M6 and GWT 2.3.0 with "Unhandled exception type IOException"

2011-08-23 Thread Jerome Louvel 
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.o​rg
Noelios Technologies ~   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(
-->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

Restlet 2.1-M6 and GWT 2.3.0 with "Unhandled exception type IOException"

2011-08-23 Thread Joscha Feth 
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(
-->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=2828931

StackOverflow error in org.restlet.ext.servlet.internal.ServletWarEntity

2011-08-23 Thread Joscha Feth 
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 ErrorCaused by:java.lang.StackOverflowError
at java.io.UnixFileSystem.list(Native Method)
at java.io.File.list(File.java:973)
at
org.eclipse.jetty.util.resource.FileResource.list(FileResource.java:320)
at
org.eclipse.jetty.server.handler.ContextHandler.getResourcePaths(ContextHandler.java:1434)
at
org.mortbay.jetty.plugin.JettyWebAppContext.getResourcePaths(JettyWebAppContext.java:253)
at
org.eclipse.jetty.server.handler.ContextHandler$Context.getResourcePaths(ContextHandler.java:1714)
at
org.restlet.ext.servlet.internal.ServletWarEntity.(ServletWarEntity.java:111)
at
org.restlet.ext.servlet.internal.ServletWarEntity.(ServletWarEntity.java:119)
at
org.restlet.ext.servlet.internal.ServletWarEntity.(ServletWarEntity.java:119)
at
org.restlet.ext.servlet.internal.ServletWarEntity.(ServletWarEntity.java:119)
...and so on
-- 8< --

I am not able to completely pinpoint why this happens (my code has not
changed much since yesterday), but I suspect some entries in the PATH are
problematic and it loops infinitely. It looks like
the same issue found in 2009:
http://www.mail-archive.com/discuss@restlet.tigris.org/msg07005.html however
according to the post this should have been fixed by now.

I will further investigate, but is anyone else seeing this or has an idea
where this might come from?

Kind regards,
Joscha Feth

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2828918

RE: RFC - Roadmap for Restlet version 2.2

2011-08-23 Thread Jerome Louvel 
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 enhancements. 

 

Best regards,
Jerome
--
Restlet ~ Founder and Technical Lead ~   
http://www.restlet.o​rg
Noelios Technologies ~   http://www.noelios.com

 

 

De : Jerome Louvel [mailto:jerome.lou...@noelios.com] 
Envoyé : lundi 22 août 2011 16:51
À : Restlet Discuss (discuss@restlet.tigris.org)
Objet : RFC - Roadmap for Restlet version 2.2

 

Hi all,

 

Over the past days, I’ve been working on a draft roadmap document for version 
2.2. In order to announce it when releasing version 2.1 RC1, which is planned 
for the end of September, I would like to give everyone a first opportunity to 
comment and weight in: http://wiki.restlet.org/developers/175-restlet

 

This is time to express your expectations and concerns! We are also looking at 
new contributors, for fixing existing bugs, taking over passive extensions such 
as the JAX-RS one and writing better documentations.

 

Best regards,
Jerome
--
Restlet ~ Founder and Technical Lead ~   
http://www.restlet.o​rg
Noelios Technologies ~   http://www.noelios.com

--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2828851