I'm just checking in on the status of Atom integration. Has it been integrated
into the 1.1 source yet, or is it still on the todo list? Thanks.
-Alex
Now that 1.0 is out, is there any word on when Atom support will be brought back
in? We'd like to be able to have a search feed, and Atom will, needless to say,
make this much easier.
The way I got the bug was as follows:
String request = http://localhost:1234/;;
for(int i=0;i5*1024;i++)
request += a;
Component component = new Component();
Server server = component.getServers().add(Protocol.HTTP, 1234);
component.start();
Client client = new Client(Protocol.HTTP);
If you do a GET on a URI that is too big (4k by default), the response status
will be 'null (-1)'. A quick look at the standard HTTP codes says that it
should be 'Request URI too long (414)'. Something to incorporate.
In RC1 we indeed removed the per-application access log in favor of a shared
access log attached to the Component. This service only logs server-side
accesses to the component (via server connectors) and writes them in an
Apache-like format. The logger name used for this purpose it something
Run into a bit of an issue: It seems that if I create an Application and attach
it to a Component, the Application no longer makes use of the Component's access
logger. I'm guessing this dates back to RC1 and the deprecation of
Application's logService, but if this is the case, how do I go about
In the function detach, it calls the default route to see if it is equal to the
target that you are removing, and set the default route to null. However, if
you've never set the defaultRoute and try to detach something, you get a null
pointer error. It seems that this should be checked for.
Ok, remember when I said I had a hack to change the context logger? Well,
that's come around to bite me now. If I call
Component.getContext().getDispatcher(), by default I get a nice
TemplateDispatcher. However, because I have to create a new Context to set the
logging in, calling
Ok, so then how do I differentiate between Access log name and Context log name?
I use two different logs for the both of them in my program
Hi, I'm upgrading my codebase from beta 20 to RC4, and I've noticed that my
LogService can no longer deal with a ContextLogger (i.e.
get/setContextLoggerName have been removed). Is this true, or has the
functionality simply been moved elsewhere in a previous release?
(Currently using beta 20)
I am having a little bug with the DomRepresentation class. When I instantiate
it with a Document {new DomRepresentation(MediaType.APPLICATION_XML,
myDocument)}, the DomRepresentation object does not store the size of the
Document, which means that if I want to find it
Hey Jerome,
Unfortunately, this doesn't quite make the cut. Right now what I'm trying to do
is to serve a static file with my Application. According to the tutorial,
however (http://www.restlet.org/tutorial#part06) I basically need a Component to
set up the Protocol.FILE client connector.
Update:
I've tried it with beta 23, and it seems to work as expected now. Looks like
I'll have to upgrade.
I would like to put in a feature request, though. Ideally, I would want to be
able to do something like the following:
Application app = new Application(new Context()){
public
13 matches
Mail list logo
