RE: Re: About XTC (Facelets port)
I'm happy to hear that XTC has actually been used in production. That's enough for me to try to use it myself. I suppose the whole integration shouldn't be so difficult altogether. All that there really is to do, is to override AbstractUrlBasedView which amounts to implementing a single method: void renderMergedOutputModel(MapString, Object model, HttpServletRequest request, HttpServletResponse response) throws Exception; after which the whole layout should be outputed to the response stream object. Inside the method, the path to rendered page template is available. The model parameter associates names of variables with their interpretations. If those interpretations are some compound types, their components should be available through var.somePropertyName or var[123], etc. Are there some important incompatibilities? From the projects' trac it seems the implementation is pretty complete when it comes to features that are applicable in a RESTful approach. If I see correctly, you don't mention ui:fragment / tag on your wiki. Is it available? Well, in the end I would really like to say: thank you, thank you, thank you. I really spent a gazillion hours looking for some decent templating solution that is previewable and isn't using some home-brew domain specific language or isn't tightly coupled with some crappy stateful web framework. Julek -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2664817
RE: Re: Security and GAE
Thank you very much Stephan! Yiannis -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2664784
RE: Accept Header not working
Hello, I've juste tried using firefox and a Restlet client, and I get the right list of accepted media types on server side. Could you precise the kind of clietn are you using, and maybe give more details about the servier side? Best regards, Thierry Boileau -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2664857
RE: Determinism in content negotiation
Hello,
well, in your case, the conversion of Blah objects to Representation is taken
into account by a JSON converter. From the point of view of converters, there
is not difference between the two annotated methods, because they both return a
Blah object. And as they are two methods that are able to generate json
representations, the algorithm choose the first declared one.
As a general rule it's better to put specific methods before the generic ones.
I wonder why the are two distinct methods. Do they generate distinct objects?
I can see a reason to use a specific method when you control the way to
generate the json representation and don't want to rely on converter. In this
case, if you remove the JSON converter and change the method so that it returns
a Representation, the content negotiation happens correctly:
@Get(json)
public Representation retrieve2() {
//return a JSON Representation according to your own serialisation algorithm.
}
I don't argue to reply plainly to your request, so feel free to ask for more
details!
Best regards,
Thierry Boileau
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2664862
