gmane.comp.java.restlet

Re: java.lang.AbstractMethodError: org.restlet.util.Engine.fireContextChanged

Rhett Sutphin — 2008-12-01T19:08:55

Hi Ian, You need to upgrade the com.noelios.restlet dependencies to 1.1.1, too. Rhett On Dec 1, 2008, at 11:58 AM, Ian Clarke wrote:

Re: java.lang.AbstractMethodError: org.restlet.util.Engine.fireContextChanged

Ian Clarke — 2008-12-01T17:58:21

Hi Thierry, Just checked, the file com.noelios.restlet-1.0.11.jar is in my classpath (put there by Maven). com.noelios.restlet.ext.httpclient-1.0.11.jar is also there. Not sure quite what you mean about the context, but here is the code that seems to cause the error: < at >BeforeClass public void beforeClass() { client = new Client(Protocol.HTTP); client.getContext().getParameters().add("converter", "com.noelios.restlet.http.HttpClientConverter"); client.getContext().getParameters().add("connectionManagerTimeout", "100"); urlPrefix = "http://127.0.0.1:" + LISTEN_PORT + "/"; } Hope that is helpful, let me know if there is anything else I can tell you. Ian. On Mon, Dec 1, 2008 at 3:18 AM, Thierry Boileau noelios.com> wrote:

Re: java.lang.AbstractMethodError: org.restlet.util.Engine.fireContextChanged

Thierry Boileau — 2008-12-01T09:18:02

Hello Ian, it looks the com.noelios.restlet.jar is not in the classpath. Can you check it? Can you give more details about your context? Best regards, Thierry Boileau -- Restlet ~ Core developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com

java.lang.AbstractMethodError: org.restlet.util.Engine.fireContextChanged

Ian Clarke — 2008-12-01T05:44:06

Just upgraded to Restlet 1.1.1 (using Maven), and I'm seeing the following error when I attempt to call a unit test that worked previously, any ideas? :- Caused by: java.lang.AbstractMethodError: org.restlet.util.Engine.fireContextChanged(Lorg/restlet/Restlet;Lorg/restlet/Context;)V at org.restlet.Restlet.(Restlet.java:90) at org.restlet.Connector.(Connector.java:83) at org.restlet.Client.(Client.java:82) at org.restlet.Client.(Client.java:101) at org.restlet.Client.(Client.java:121)

Re: after POST with a response of type DomRepresentation clienthangs on getting response?

Eugeny N Dzhurinsky — 2008-11-29T22:24:01

I was able to resolve the issue - I am having ould implementation of Xerces library, which doesn't provide some methods for the XML serialization. So I was able to solve the problem with providing the new version of xercesImpl (2.9.1) and everything worked.

after POST with a response of type DomRepresentation client hangson getting response?

Eugeny N Dzhurinsky — 2008-11-29T21:40:00

Hello there! I just started to learn RESTlet framework and I am facing some strange issue I can't handle. I've created the simple resource, which verifies if such user exists and if so - returns the unique hash for the user. I also wrote the simple test case, which starts the REST service and then sends the request to authenticate the user. At this point there is the strange issue appearing: when DomRepresentation is used, the test simply hangs on valid user (when the response is sent), but when StringRepresentation is used - everything works fine. The code for the Service: ============================================================================================ import org.apache.log4j.Logger; import org.restlet.Context; import org.restlet.data.Form; import org.restlet.data.MediaType; import org.restlet.data.Request; import org.restlet.data.Response; import org.restlet.data.Status; import org.restlet.resource.DomRepresentation; import org.restlet.resource.Representation; import org.restlet.resource.Resource; import org.restlet.resource.ResourceException; import org.restlet.resource.Variant; import org.w3c.dom.Document; import org.w3c.dom.Element; public class SignIn extends Resource { private static final Logger log = Logger.getLogger(SignIn.class); private CredentialsDao dao; private HashGeneratorInterface hashGenerator; /** * < at >see org.restlet.resource.Resource#init(org.restlet.Context, * org.restlet.data.Request, org.restlet.data.Response) */ < at >Override public void init(final Context context, final Request request, final Response response) { super.init(context, request, response); setModifiable(true); getVariants().add(new Variant(MediaType.TEXT_XML)); } /** * < at >see org.restlet.resource.Resource#acceptRepresentation(org.restlet.resource.Representation) */ < at >Override public void acceptRepresentation(final Representation entity) throws ResourceException { final Form form = new Form(entity); final String username = form.getFirstValue("username"); final String password = form.getFirstValue("password"); final Credentials credentials = dao.loadCredentialsByUsername(username); final Response response = getResponse(); try { if (credentials != null && credentials.getPassword().equals( hashGenerator.generateHash(credentials.getUuid() .toString(), password))) { final DomRepresentation representation = new DomRepresentation( MediaType.TEXT_XML); final Document document = representation.getDocument(); final Element uuid = document.createElement("uuid"); uuid.setTextContent(credentials.getUuid().toString()); document.appendChild(uuid); document.normalizeDocument(); response.setEntity(representation); response.setStatus(Status.SUCCESS_OK); } else response.setStatus(Status.CLIENT_ERROR_UNAUTHORIZED); } catch (final Exception e) { log.error(e, e); response.setStatus(Status.SERVER_ERROR_INTERNAL); } } public void setDao(final CredentialsDao dao) { this.dao = dao; } /** * < at >param hashGenerator * the hashGenerator to set */ public void setHashGenerator(final HashGeneratorInterface hashGenerator) { this.hashGenerator = hashGenerator; } } ============================================================================================ The code for the test: ============================================================================================ import junit.framework.Assert; import org.dbunit.dataset.xml.FlatXmlDataSet; import org.dbunit.operation.DatabaseOperation; import org.junit.AfterClass; import org.junit.Before; import org.junit.BeforeClass; import org.junit.Test; import org.restlet.Client; import org.restlet.Component; import org.restlet.data.Form; import org.restlet.data.Protocol; import org.restlet.data.Reference; import org.restlet.data.Response; import org.restlet.resource.Representation; import org.springframework.context.ApplicationContext; import org.springframework.context.support.ClassPathXmlApplicationContext; public class TestRestImplementation { private static Component server; < at >BeforeClass public static void startupContainer() throws Exception { // TODO setup the REST container here DBUnitDatabaseAdapter.initSqlMapClient(); final ApplicationContext ctx = new ClassPathXmlApplicationContext( new String[] { "applicationContext-server.xml" }); server = (Component) ctx.getBean("top"); server.start(); } < at >Before public void cleanupDatabase() throws Exception { DBUnitDatabaseAdapter.cleanDatabase(); } < at >Test(timeout = 5000) public void testSignin() throws Exception { final Client client = new Client(Protocol.HTTP); final Reference itemsUri = new Reference( "http://localhost:3000/users/signin"); DatabaseOperation.INSERT.execute(DBUnitDatabaseAdapter.connection, new FlatXmlDataSet(TestRestImplementation.class .getResourceAsStream("/dbunit/credentials.xml"))); // incorrect password goes here Form form = new Form(); form.add("username", "username"); form.add("password", "123456789"); Representation rep = form.getWebRepresentation(); Response response = client.post(itemsUri, rep); Assert.assertTrue(response.getStatus().toString(), response.getStatus() .isError()); // correct password goes here form = new Form(); form.add("username", "username"); form.add("password", "123456"); rep = form.getWebRepresentation(); response = client.post(itemsUri, rep); Assert.assertFalse(response.getStatus().toString(), response .getStatus().isError()); } < at >AfterClass public static void shutdownContainer() throws Exception { server.stop(); } } ============================================================================================ Can somebody please explain what am I missing here? Thank you in advance!

RE: Well HTTPS

Jerome Louvel — 2008-11-29T16:51:49

Hi Ben, Excellent! Let us know if you need help regarding the wiki edition. You can also check editing instructions here: http://wiki.restlet.org/about/2-restlet.html Best regards, Jérôme Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -----Message d'origine----- De : Ben Johnson [mailto:ben.johnson< at >jandpconsulting.co.uk] Envoyé : samedi 29 novembre 2008 16:57 À : discuss< at >restlet.tigris.org Objet : Re: Well HTTPS Hi Jérôme Sure, I'll try to put it together next week - I'd like to refine the certificate / key store instructions so it's clear what needs to be done on a server versus what needs to be done on a client. Regards Ben -------------------------------------------------- From: "Jerome Louvel" noelios.com> Sent: Friday, November 28, 2008 2:12 PM To: restlet.tigris.org> Subject: RE: Well HTTPS

Re: Well HTTPS

Ben Johnson — 2008-11-29T15:57:02

Hi Jérôme Sure, I'll try to put it together next week - I'd like to refine the certificate / key store instructions so it's clear what needs to be done on a server versus what needs to be done on a client. Regards Ben -------------------------------------------------- From: "Jerome Louvel" noelios.com> Sent: Friday, November 28, 2008 2:12 PM To: restlet.tigris.org> Subject: RE: Well HTTPS

RE: Guard suggestion

Jerome Louvel — 2008-11-28T15:22:09

Hi all, I agree that having a 'guest' (or better 'anonymous') principal would be useful as default access rights/permissions could be assigned to it. Best regards, Jérôme Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -----Message d'origine----- De : Stephan Koops [mailto:Stephan.Koops< at >web.de] Envoyé : jeudi 27 novembre 2008 16:31 À : discuss< at >restlet.tigris.org Objet : Re: Guard suggestion Hi Bruno, while now thinking about it: If the role checking logic is accesible via the principal, than a guest principal is useful. best regards Stephan http://jguard.xwiki.com/xwiki/bin/view/Doc/Faq#HAccessFilterautomaticallytriestologmeinas27guest27Whyshouldtherebea22default22userin jGuard3FIsn27tthatasecurityissue3F _________________________________________________________________________ Sensationsangebot nur bis 30.11: WEB.DE FreeDSL - Telefonanschluss + DSL für nur 16,37 Euro/mtl.!* http://dsl.web.de/?ac=OM.AD.AD008K13805B7069a

RE: Restlet "Directory" suggestion

Jerome Louvel — 2008-11-28T14:51:47

Hi Cliff, Ok, good idea for the XML representation. There is a related RFE that I've just updated: "Provide an XML directory listing representation" http://restlet.tigris.org/issues/show_bug.cgi?id=420 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 : Cliff Binstock [mailto:cliff.binstock< at >coyotereporting.com] Envoye : mercredi 26 novembre 2008 23:50 A : discuss< at >restlet.tigris.org Objet : RE: Restlet "Directory" suggestion Jerome, Inline ... Yes, the directory listing. While quite obtuse, in Tomcat there is a built-in XML directory listing to which you can apply a stylesheet. Perhaps you could automatically return different variants? The basic guard isn't friendly enough. If I have users 'John', 'Fred', and 'Alice', I'd like to have /user/John; /user/Fred; /user/Alice. Each person has access only to their own directory (or perhaps some other complex authorization like groups). Cliff

RE: Posting a form with a file

Jerome Louvel — 2008-11-28T14:32:30

Hi Jérémy, That sounds like the right approach. On the server-side, you will probably have to use the FileUpload extension for Restlet in other to save the file sent. Let us know how it goes! Best regards, Jérôme Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -----Message d'origine----- De : Jérémy Bogatirsky [mailto:jbogatirsky< at >gmail.com] Envoyé : mercredi 26 novembre 2008 18:55 À : discuss< at >restlet.tigris.org Objet : Re: Posting a form with a file I respond to myself :-) I'm going to use a classic FormPanel in GWT to send the file. Restlet in server-side should be able to understand it, I mean it's designed to. I'll let you know ! Jérémy 2008/11/26 Jérémy Bogatirsky gmail.com>:

RE: Well HTTPS

Jerome Louvel — 2008-11-28T14:12:15

Hi all, I think that Ben's step-by-step tutorial (with Bruno's remarks) would be a great addition to Restlet's User Guide! There is now a shell page "Configuring HTTPS", crying for such content: http://wiki.restlet.org/docs_1.1/13-restlet/27-restlet/46-restlet/213-restle t.html Ben, I saw that you already registered an account on the wiki and now you have edition rights (like all registered users). Would you be open to contributing the content of your post to this page? Best regards, Jérôme Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -----Message d'origine----- De : Ben Johnson [mailto:ben.johnson< at >jandpconsulting.co.uk] Envoyé : vendredi 21 novembre 2008 18:51 À : discuss< at >restlet.tigris.org Objet : Re: Well HTTPS Thanks for the feedback Bruno; I'm still learning about certificates and Restlet, and I appreciate your clarifications! Regards Ben -------------------------------------------------- From: "Bruno Harbulot" manchester.ac.uk> Sent: Friday, November 21, 2008 2:54 PM To: restlet.tigris.org> Subject: Re: Well HTTPS -Djavax.net.ssl.trustStore=JKS

Re: Getting the Client address from request

Tamás Cservenák — 2008-11-27T16:51:35

Hi there, thanks for asking, but... I would like to, but currently at Sonatype we are very focused on the upcoming release, so i cannot participate currently :( ~t~ On Wed, Nov 26, 2008 at 4:23 PM, Jerome Louvel noelios.com> wrote:

Re: Guard suggestion

Stephan Koops — 2008-11-27T15:30:46

Hi Bruno, while now thinking about it: If the role checking logic is accesible via the principal, than a guest principal is useful. best regards Stephan _________________________________________________________________________ Sensationsangebot nur bis 30.11: WEB.DE FreeDSL - Telefonanschluss + DSL für nur 16,37 Euro/mtl.!* http://dsl.web.de/?ac=OM.AD.AD008K13805B7069a

Re: Guard suggestion

Bruno Harbulot — 2008-11-27T12:56:11

Hi Stephan, Stephan Koops wrote: I don't think it's very significant. I was simply referring to what jGuard does: http://jguard.xwiki.com/xwiki/bin/view/Doc/Faq#HAccessFilterautomaticallytriestologmeinas27guest27Whyshouldtherebea22default22userinjGuard3FIsn27tthatasecurityissue3F Best wishes, Bruno.

Re: No available xxx connector supports the required protocols

Raif S. Naffah — 2008-11-27T09:47:53

hello Thierry, On Thursday 27 November 2008 08:38:17 pm Thierry Boileau wrote: no worries. cool. i might have a go at implementing it and submitting a patch. cheers; rsn

Re: No available xxx connector supports the required protocols

Thierry Boileau — 2008-11-27T09:38:17

Hello Raif, Actually, there is no documentation about this element... It simply adds key/value pairs into the list of parameters of the component's context. I've added an RFE for this issue => http://restlet.tigris.org/issues/show_bug.cgi?id=670 Best regards, Thierry Boileau -- Restlet ~ Core developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com

Re: Guard suggestion

Stephan Koops — 2008-11-27T08:31:09

Hi Bruno, why not use null as "guest principal"? What is the advantage of an object for it? best regards Stephan

RE: Restlet "Directory" suggestion

Cliff Binstock — 2008-11-26T22:49:53

Jerome, Inline ... Yes, the directory listing. While quite obtuse, in Tomcat there is a built-in XML directory listing to which you can apply a stylesheet. Perhaps you could automatically return different variants? The basic guard isn't friendly enough. If I have users 'John', 'Fred', and 'Alice', I'd like to have /user/John; /user/Fred; /user/Alice. Each person has access only to their own directory (or perhaps some other complex authorization like groups). Cliff

Re: ServletServlet example

Mark Rosenthal — 2008-11-26T20:29:38

Beautiful! Thanks Thierry. Thierry Boileau wrote:

Re: No available xxx connector supports the required protocols

Raif S. Naffah — 2008-11-26T19:04:05

salut Jerome, On Thursday 27 November 2008 01:43:31 am Jerome Louvel wrote: that's fine as long as IMO it's consistent across the different configuration mechanisms. there probably are/will be cases where one would want to share some parameters between Applications in a Component. as a side-note, i see in the Component schema a "parameter" element in the "ComponentType" type. where can i find more documentation about this element? what's the difference between programmatically doing this versus a mechanism that would allow me to do the same through a configuration file? one thing i can think of would be more flexibility (in terms of object's type) of the parameter value. one easy way to allow this could be to add a sequence of "init-param" (or "context-param") elements of type "ParameterType" to the "AttachType". it sure does help me get further in understanding the API. thank you and Thierry for your help. btw. the more i get to know the toolkit the more i like how you guys have designed it! in time i hope i'll be able to contribute to the code. cheers; rsn