connector to your classpath.
==
Any code change required? How could i build the war to be deployed onto Tomcat?
Thanks.
Best Regards,
Alex
Alex alexlam.hk at gmail.com writes:
Hi,
http://www.restlet.org/documentation/1.0/faq#02
Actually, i have followed the instruction above.
However, there are a number of queries in mind:
Why do we still need a main in a servlet container?
Why still need a port in the main
while
. The problem seems to be caused
by mismatching URL although nothing abnormal is found from the output of
com.noelios.restlet.LogFilter. Thanks.
Yours,
Alex
there is escape character in the URL, e.g.,
http://localhost:8081/MyFirstOc4j/dir/c%3a%5ctemp/afile/
I cannot even get into Application. Why and is there a standard method to cater
for escaped characters?
Yours,
Alex
automatically, right?
Thanks in advance for any assistance. If you need more info about my
implementation, I will happily provide it.
br,
Alex
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2991328
it be that Restlet 2.0.15 is not
handling smoothly SSL communication, and I would need to upgrade to 2.1 or
later?
Looking forward to hearing your suggestions. In case you'd like to get some
more info that could help, just ask me. :)
Thanks in advance,
Alex
--
View this message in context:
http://restlet
here, so any help would be much appreciated.
br,
Alex
--
View this message in context:
http://restlet-discuss.1400322.n2.nabble.com/Android-client-Restlet-2-0-15-cannot-connect-with-HTTPS-SSL-recoverable-error-1001-tp7578771p7578774.html
Sent from the Restlet Discuss mailing list archive
any suggetions. :)
br,
Alex
--
View this message in context:
http://restlet-discuss.1400322.n2.nabble.com/Android-client-Restlet-2-0-15-cannot-connect-with-HTTPS-SSL-recoverable-error-1001-tp7578771p7578778.html
Sent from the Restlet Discuss mailing list archive at Nabble.com
Hello Jerome,
thanks a lot for responding.
If gaving the org.restlet.ext.net.jar on your classpath is enough, then I've
already done what you're suggesting. As I stated on my first post, I'm not
using the internal http connector, but instead the apache httpclient.
In any case, I've even
This doesn't have the desired result either. :/
br,
Alex
On 6 Μαϊ 2013, at 6:08 μ.μ., Jerome Louvel-3 [via Restlet Discuss]
ml-node+s1400322n7578782...@n2.nabble.com wrote:
Alex;
You to put the connector in the first postion doing this:
Engine.getInstance().getRegisteredClients().add(0
you're doing on Restlet.
br,
Alex
--
View this message in context:
http://restlet-discuss.1400322.n2.nabble.com/Android-client-Restlet-2-0-15-cannot-connect-with-HTTPS-SSL-recoverable-error-1001-tp7578771p7578786.html
Sent from the Restlet Discuss mailing list archive at Nabble.com
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
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.
release, that I missed)? Thanks.
-Alex
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?
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
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
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.
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 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
On 2/22/07, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Alex,
Using the latest RC4 release, you can very easily handle this case using
URI
variables. Check this tutorial section for an example on how to define URI
templates and how to get the variable values extracted via the request
attributes
What is the relationship of the Restlet project to JSR 311: JavaTM API for
RESTful Web Services ?
http://www.jcp.org/en/jsr/detail?id=311
There are some of the same people involved.
--Alex Milowski
(application/xquery)) );
--Alex Milowski
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.
)) ...
So, what I am missing about how Reference is handled
when it is passed to a client helper?
--Alex Milowski
On 4/3/07, Jerome Louvel [EMAIL PROTECTED] wrote:
Alex,
The remaining part property is varying depending on the routing process.
When the routing starts, this property contains the whole URI for example.
In your client helper, you should use a more stable way of extracting the
interesting
If I need to get a Slug header, I can do:
Form headers =
getRequest().getAttributes().get(org.restlet.http.headers);
String slug = headers.getValues(Slug);
but is that Slug or slug or does it not matter? For a header, it
should be case-insensitive.
--Alex Milowski
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);
setup my routing
paths without a trailing slash so that I can re-use objects that contain
routers that start with a slash?
--Alex Milowski
) {
protected boolean checkSecret(String user,char [] password) {
...db lookup code...
}
};
and the guarded application is added through the setNext() method.
--Alex Milowski
() {
return getContext().getLogger();
}
public SeriesParameter getParameters() {
return getContext().getParameters();
}
};
but that seems like it might be useless if the context is shadowed somehow.
--Alex Milowski
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.
, but getting something basic running isn't so hard.
--Alex Milowski
as well.
The biggest issue in implementing the atom protocol is the storage
and retrieval of feeds. I'm using eXist to store the XML and Derby
to store relational metadata about them. That would have to be
abstracted out in a restlet-provided implementation.
--Alex Milowski
to this project except that it should be
easier to build now and it has an official home.
The code lets you run the embedded version of eXist and then access it
through Client
calls.
--Alex Milowski
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
On 7/1/07, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Alex,
Thanks for the detailed explanation on atomojo and for suggesting a merging
on the Atom client side. Your contribution in this area would be very
welcomed for Restlet 1.1.
The only problem is that my code relies upon my xml-infoset
or a trick
that I need to do to get this to work?
--Alex Milowski
On 7/7/07, Jerome Louvel [EMAIL PROTECTED] wrote:
Alex,
It looks fine to me at the Restlet level... In Component, the code looks ok:
public Server add(Protocol protocol, int port) {
Server result = new Server(getContext(), protocol, null, port,
getTarget
/O/myterm
I believe the problem is in Template.java but I haven't really dug
into the code yet.
--Alex Milowski
Turning on fine logging I get the following. It looks the route
handling is correct. Is it
possible that the Reference class is doing something bad ?
Jul 17, 2007 10:49:01 AM com.noelios.restlet.component.HostRoute beforeHandle
FINE: New base URI: https://localhost:8080
Jul 17, 2007 10:49:01
*sigh*
My bug. I take the remaining part and create a new Reference() instance along
the way. That explains everything.
At least I got to dig into the code and understand it a bit better. :)
--Alex Milowski
)this.connection;
+ https.setHostnameVerifier(HostnameVerifier.DEFAULT);
+}
+
// These properties can only be used with Java 1.5 and upper
// releases
--Alex Milowski
On 7/27/07, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Alex,
Thanks for teaching me new aspects of SSL :)
We have a RFE to improve SSL support in Restlet 1.1, I've updated it to
propose the addition of a connector parameter. See details here:
http://restlet.tigris.org/issues/show_bug.cgi?id
On 7/31/07, Jim Alateras [EMAIL PROTECTED] wrote:
Alex/Jerome,
I am also interested in incorporated APP client and server capabilities
in our application. I have a couple of questions more so for Alex than
Jerome.
1. From the little I've read on atomojo there seems to be a database
;
}
this.context = new Context(logName);
}
return this.context;
}
--Alex Milowski
a certain time has passed (in
Firefox I believe it's 30 seconds), another POST request will go through.
Was this ever resolved? I don't see an issue filed on this one.
I've been testing atomojo and found the same issue.
I suppose I should just switch from the simple framework to Jetty.
--Alex
and System.err uses in Base64.java that would be
better served as either an exception or being set to a Logger instance.
--Alex Milowski
header could remain and randomly allow another user into a resource
for which they
do not have access.
--Alex Milowski
and not available via
public methods
on the Component class.
I suggest this is filed as an enhancement to provide a way to reload
the virtual
hosts from the host list. It should be very easy to implement but
probably requires
a special method on Component.
--Alex Milowski
On 8/17/07, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Alex,
The serverAddress property indeed does comparisons based on the
numerical IP address. There are some convenience static methods on
VirtualHost:
- getLocalHostAddress()
- getIpAddress(String domain)
This should get clarified
-Cookie header is there?
[1] https://addons.mozilla.org/en-US/firefox/addon/3829
[2] https://addons.mozilla.org/en-US/firefox/addon/2691
--Alex Milowski
On 8/18/07, Jerome Louvel [EMAIL PROTECTED] wrote:
Alex,
The serverAddress property indeed does comparisons based on the
numerical IP address. There are some convenience static methods on
VirtualHost:
- getLocalHostAddress()
- getIpAddress(String domain)
This seems a bit
On 8/22/07, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Alex,
In the end, when you add the server the domain name resolves
to a single
IP address that is the bind address for the server. My only
suggestion is that
if I can use a name to set the bind address I should be able
to use
On 8/24/07, Sean Landis [EMAIL PROTECTED] wrote:
Alex,
Thanks for the patch. Unfortunately the build appears to be in a very bad
state. A unit test fails, so I had to run the rest of the targets by hand.
The resulting distro doesn't work at all.
I checked out a clean copy to fix the build
protocol is gong to
be much more useful. In the case of P2P computing, handling responses
asynchronously lets the sender continue to do useful work while waiting for
the response.
--Alex Milowski
?
Has anyone tried JRuby or Groovy with Restlets ?
--Alex Milowski
.
Maybe we need a new Finder called ClassResourceFinder such that you can do:
router.attach(/content,new ClassResourceFinder(MyApp.clas,content));
and get resources from getResource() calls against the ClassLoader.
--Alex Milowski
should be. Further, the
class loaded could use multiple jar files and so there isn't a way
to construct one URI.
All that complexity is avoided by using:
MyApp.class.getResourceAsStream(path);
I'm testing some code right now for this and I'll try to post an example later.
--Alex Milowski
)
{
if (getLogger().isLoggable(Level.FINE)) {
getLogger().info(Class resource: +path);
}
InputStream is = baseClass.getResourceAsStream(path);
if (is==null) {
return null;
} else {
return new InputRepresentation(is,type);
}
}
}
--Alex Milowski
On 9/23/07, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Alex,
This is different in that I need to use the ClassLoader associated
with a class instance. So, I need to pass MyApp.class and there is
no way to make a URI to that resource without reconstructing
the jar URL.
Agreed. You need
On 11/5/07, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Alex,
As you probably know, we already have a way to specify the type of each
variable in an URI template via the org.restlet.util.Variable class and the
Template.variables and Template.defaultVariable properties.
Could you describe
On 11/6/07, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Alex,
Thanks for sharing all the details.
1) For the root attachment issue, you can use this approach instead:
// To match only URIs that are strictly equal to /
Template template = router.attach(/, rootRestlet).getTemplate
On 11/8/07, xasima [EMAIL PROTECTED] wrote:
Hi, Jerome and Alex.
We can use http://smallx.dev.java.net or cocoon maps notation
(http://cocoon.apache.org/2.2/core-modules/core/2.2/853_1_1.html) to provide
info for the coordination of such a pipes / URI. I think that reasons to do
) { ... }
and that way someone like myself could override the forbid method on a Guard
instance to add a challenge.
This would fix the problem where Firefox et. al. remember the bad password
and require that I clear passwords before I get the challenge again.
--Alex Milowski
the
case where the 'write' method is never called for some reason.
--Alex Milowski
On 11/23/07, Alex Milowski [EMAIL PROTECTED] wrote:
I see there is a release() method on the Representation class but I can find
any
place in the trunk where this method is actually used.
I have a problem in that I'm using an OutputRepresentation instance to return
a resource from eXist
) to
describe the media types and their extensions. By default this could be
packaged in the org.restlet.jar file but could be overridden with a system
property that points to a different location to load.
--Alex Milowski
.
Currently, I've been doing this by recreating the authenticate method and then
calling my new checkSecret() method. That seems a bit clunky.
--Alex Milowski
two request to that web service, the current class works
fine because the authorize() method has the request and response as parameters.
--Alex Milowski
?
--Alex Milowski
set of resources with the trunk code.
It worked just fine!
--Alex Milowski
as:
Context appContext =
Engine.getInstance().createHelper(MyComponent.this).createContext(getLogger().getName());
This seems rather non-obvious :(
--Alex Milowski
returns with a
URI list. I've
tried turning content negotiation off but that doesn't seem to help.
I can easily write the Restlet to do what I want... but I thought I'd
use standard
objects rather than do that... :)
BTW, I'm using the trunk build as of yesterday.
--Alex Milowski
);
It seems to me that a service such as this:
* should be *OFF* by default
* shouldn't mess with the original information (e.g. leave the last
segment alone)
* should provide its information as an optional augmentation of the request.
--Alex Milowski
Sounds good to me.
.
To switch the extension tunnel off, you need
getTunnelService().setExtensionTunnel(false).
Thanks. I'll try that.
--Alex Milowski
On Wed, May 14, 2008 at 12:27 AM, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Alex,
I have fixed this potential NPE in SVN trunk.
Can't you directly pass your Component's context to the Application
constructor instead of having to recreate it manually via the internal
'createContext
of
whether such filters are enabled.
--Alex Milowski
On Mon, May 19, 2008 at 1:31 AM, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Alex,
Like Thierry, I have just checked the code again and in trunk the extensions
tunnel feature is now off by default.
The idea behind this feature is to have a very simple way for a user to
specify, for any
On Wed, May 21, 2008 at 3:38 AM, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Alex,
Thanks for sharing the Atomojo usage details.
The TunnelService has been turned on since 1.0 and nobody complained (yet)
about the default query parameters (method, charset, encoding,
language and media
) with a
virtual host?
--Alex Milowski
On Wed, Jul 2, 2008 at 7:45 AM, Bruno Harbulot
[EMAIL PROTECTED] wrote:
Hi Alex,
Any particular reason why you would need two pairs of private
key/certificates in the same keystore in practice? If you want to use two
certificates, you're going to have to configure two connectors anyway, so
virtual hosts on one server
I can associate the different SSL certificates with each host's connection.
Now, I can work around the IP address limitations by using additional addresses
on the server. Is this a Restlet limitation, a Jetty limitation, or a Java
SSL implemenation limitation?
--Alex
On Sat, Jul 12, 2008 at 5:51 AM, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Alex and Bruno,
My understanding is that Alex wants this:
- a single server socket accepting all HTTP requests
- several SSL certificates selected depending on the matching virtual host
I think this can't be done
On Wed, Jul 16, 2008 at 2:32 AM, Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Alex,
I have added a paragraph on Confidentiality in the Securing applications
page covering this topic:
http://wiki.restlet.org/docs_1.1/g1/13-restlet/29-restlet/99-restlet/46-rest
let.html
At some point, it might
sure if my experience is typical, but I think this
is a really good step forward even if it has causes a minor amount of pain
upgrading to the trunk.
--Alex Milowski
= rep.getMediaType();
String charset = type.getParmeters().getFirstValue(charset);
rep.setMediaType(MediaType.valueOf(rep.getMediaType().getName()));
rep.setCharacterSet(CharacterSet.valueOf(charset));
}
That seems rather onerous.
--Alex Milowski
You've got warnings in your log that say you are missing the file protocol.
You should add it to your component's list of client protocols:
getClients().add(Protocol.FILE);
Try that first.
On Fri, Dec 5, 2008 at 9:10 AM, Johnny Doe [EMAIL PROTECTED] wrote:
I've read old messages here
400
Bad request).
--Alex Milowski
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2379742
* a Javascript client for doing the same
* a web server component that uses configures itself using
atom feeds (a special wrap-up of Restlet)
* some other application components for building
web applications.
Much of this still needs documentation. :(
--Alex Milowski
The sample “First Step” application firstStepsServlet from version 2.0 does not
work with Tomcat
First I checked the “First Step” application from version 1.1.5 using both
building myself and the supplied war file. Both work fine.
Second I did the same with the version 2.0. Neither the source
()));
}
I have tried all kind of value combinations, but none showed the
Authorization header in Firebug. WHAT AM I MISSING here? PS: I don't need
a password set here, just a association between Authorization - Id in
headers map
Thanks, Alex
--
View this message in context:
http://n2.nabble.com/Setting
the code, I'm sure others
are not.
Maybe putting targeted how to code samples on the wiki would also
be helpful as well as back pointers from the javadoc to the online
documentation in the wiki?
Anyway, so far things are working pretty well and I haven't run into any
real issues yet.
--Alex Milowski
,
grizzly, etc).. It seems a little bit strange, but maybe there is a reason.
I like the way restlet is implemented, I would like to understand it better
and use it when I'll have an opportunity. My purpose is not to criticize,
but to help improve restlet.
Thank you for your work!
Alex
--
View
,
grizzly, etc).. It seems a little bit strange, but maybe there is a reason.
I like the way restlet is implemented, I would like to understand it better
and use it when I'll have an opportunity. My purpose is not to criticize,
but to help improve restlet.
Thank you for your work!
Alex
--
View
On Thu, May 20, 2010 at 8:31 AM, Jerome Louvel
jerome.lou...@noelios.com wrote:
Hi Alex,
1. This design was already in place for the older Finder, with the
findTarget() and createTarget() methods. The idea is that find() could
potentially reuse instances of ServerResource subclasses created
to be changed some (which is a lot).
Are there other gotchas I should be concerned about?
Is there somewhere that we are collecting such information?
--Alex Milowski
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId
of the connector in
use and these tests have all worked flawlessly in the past. I was using
the Jetty server connector in 1.1 and I'm now moving to Grizzly.
Is this a bug or an incorrect use of the client API?
[1] http://code.google.com/p/atomojo/
--Alex Milowski
This is somewhat an alpha release. It should stabilize soon, especially
as Restlet 2.0 and eXis 1.5 become official releases.
Feedback, comments, suggestions, etc. are all welcome.
--Alex Milowski
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId
-application can't refer to its using/parent application.
That probably should be described in more detail.
4. In general, there is very little about riap://application/...
and how it works and/or is to be used.
--Alex Milowski
--
http
1 - 100 of 133 matches
Mail list logo
