Hi all,
First of all, I love the RepresentationInfo. :) Thanks for adding
this. :)
Some comments against that release:
- I wonder how to create a RepresentationInfo since it is abstract;
for the time being I created my own RepresentationInfo class derived
from the abstract class.
- Wouldn't
Really need that full annotation syntax working to test it out ;0)
Regarding that, it does seem odd to have @Get(xml) but use
MediaType.TEXT_XML in the code.
@Get(TEXT_XML) ? Shame you can't have @Get(MediaType.TEXT_HTML). I
don't know.
Jerome Louvel wrote:
Hi Jonathan,
We would be
Jonathan Hall schrieb:
Shame you can't have @Get(MediaType.TEXT_HTML). I don't know.
Would it work to change MediaType from class to an enum? That could
work, but I'm not sure
best regard
Stephan
--
Stephan Koops schrieb:
Jonathan Hall schrieb:
Shame you can't have @Get(MediaType.TEXT_HTML). I don't know.
Would it work to change MediaType from class to an enum? That could
work, but I'm not sure
While sending the email I remembered: You can't add new MediaTypes this
way, so
On Apr 2, 2009, at 11:11 AM, Stephan Koops wrote:
Jonathan Hall schrieb:
Shame you can't have @Get(MediaType.TEXT_HTML). I don't know.
Would it work to change MediaType from class to an enum? That could
work, but I'm not sure
This would sacrifice the ability to create new MediaTypes in
An alternative would be to have a MimeType class which had String constant
values for all the common MediaTypes, then you would only need to use
strings if you had a non common media type.
One other thing I've noticed that in some places the mime type is shortened
(e.g. xml instead of text/xml).
On Thu, Apr 2, 2009 at 12:13 PM, Rhett Sutphin rh...@detailedbalance.netwrote:
On Apr 2, 2009, at 11:11 AM, Stephan Koops wrote:
Jonathan Hall schrieb:
Shame you can't have @Get(MediaType.TEXT_HTML). I don't know.
Would it work to change MediaType from class to an enum? That could work,
Hi i'm an italian student and i have to plan a restful architecture using
RESTLET.
The architecture have to implement a B2B message exchange in xml format powered
by GS1 XML.
-My problem is to understand how makes the client thet have to get or post a
resource to know resource's location and
A more general note:
Applications compiled with Java 5 typically run on Java 6 JVMs without
problems.
Applications compiled with Java 6 don't run on Java 5 JVMs- the Java 5
JVM detects that the bytecode version is higher and therefore rejects
it.
So, in theory, you don't need a Java 6
Do you mean, how can a client know what URIs to use when performing service
operations?
It really doesn't have anything to do with Restlet in particular, and I
could be wrong here, but I think this is a still-evolving aspect of REST.
For a while, WADL seemed to be gaining some momentum, but there
I also ran in to the issue of having a constructor that would throw a
ResourceException if the request was bad in some way, and now the
init() method doesn't declare any exceptions. Seems pretty reasonable
to just add this.
One other alternative would be to change ResourceException to be a
Dave,
Were you able to fix or workaround this issue? If not, you should enter a
defect report (a patch would be nice).
Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com
-Message
The
MetadataService is what you're talking about. It translates between
strings and other useful dimensions (in this case, MediaType
instances). Right now, though, it only supports "extensions" as the
strings, which mean to be filename extensions. So that's why we have
"txt" as the shorthand
Excellent summary, Stephen! Requiring a descriptor (in any format) to find
a service URI often just moves the problem -- making the next question what
is the best URI to publish the descriptor?
Still, it's needful to describe REST APIs, and this often seems unreasonably
hard to do. For me,
Hi Paul,
I've just added support for this by copying the Servlet's UserPrincipal into
the Request#clientInfo#subject#principals property.
Could you do some testing with latest trunk or next snapshot and let me know
if it works fine?
Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead
Hi there,
We have some pointer in this RFE:
Support end-to-end representation security
http://restlet.tigris.org/issues/show_bug.cgi?id=270
Definitely an area of contribution!
Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~
Hi Dustin,
I've just added a change to SVN trunk for Paul Davis that copies the
Servlet's UserPrincipal into the Request's clientInfo#subject property.
With that information, you could add matching Restlet's
UserPrincipal/RolePrincipal(s) and leverage the rest of the security API.
Best
Hi Matt,
Were you able to solve this? If not, could you enter a defect report and
attach your test case?
Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com
-Message d'origine-
De :
Anecdotally ... I proxy from http to https all the time using Redirector ...
the masking to an empty 200 status looks like that perennial Tomcat 5 issue
with no-entity responses.
On Thu, Apr 2, 2009 at 3:32 PM, Jerome Louvel jerome.lou...@noelios.comwrote:
Hi Matt,
Were you able to solve
hi, I just created new organization, user (login admin, pass admin),
and group using new security API (1.2 M2) . Bind user + group to
organization. Bind group to role ADMIN_ROLE. Set up authorizer
against this role + HTTP_BASIC Guard against appropriate resource (
/admin/*) with this role
Hi,
Does
someone have a grasp on what conditional mode is for and how it used?
It's
enabled by default, but I had to disable it for one of my resources to
work with PUT and POST. The issue is that it always calls doGetInfo
first, which for my particular resource will fail, and so calls to
Jerome Louvel wrote:
Hi Rickard,
Now that 1.2 M2 is out, I can get to your email!
I would suggest that you try out Restlet 1.2 M2 if you can. The
ClientResource class allows you to set the next Restlet. If can be a
Filter chain leading to the Context#clientDispatcher of your Application
Stephan Koops wrote:
Stephan Koops schrieb:
Jonathan Hall schrieb:
Shame you can't have @Get(MediaType.TEXT_HTML). I don't know.
Would it work to change MediaType from class to an enum? That could
work, but I'm not sure
While sending the email I remembered: You can't add new
But it's not clear to me why this code should use the
MetadataService at all. The mapping of file extensions to
MediaTypes is one of the web's irritating but hard to avoid dirty
shameful secrets. The only time we should stoop so low as to base a
MediaType calculation on an extension name is if
Hi Tal-
I've been struggling with that very question, as I, too had trouble
with POSTing to my new ServerResource subclass.
I also noticed that getPreferredVariant(Method.GET) is called during
processing of the POST request, and I couldn't figure out why.
At first I thought that was the cause
Hi
David,
I
agree that filename extensions are not the best way to go here, but I
see nothing wrong with supporting them in addition to MIME types. As
for supporting MIME types, it seems we already have a facility in
Restlet via MediaType.valueOf():
26 matches
Mail list logo
