-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andre,
On 9/21/2010 4:26 PM, Andre Juffer wrote: > I got it working now. It is really in the details. > > I always relied upon a PUT request like > > http://localhost:8888/equipment > > expecting to see the request method set to PUT. In fact, it was always GET. > > If, however, one employs > > http://localhost:8888/equipment/ > -------------------------------^ > > (Notice the forward slash at the end!) Wow! So, your server was issuing a redirect to the client? That usually only happens when you have something else going on. Is /equipment the context path of your webapp? If so, I think you have to have /something/ after the "/equipment", otherwise it's a request for no resource at all. Try confirming (say, with LiveHttpHeaders) that the PUT is being redirected by the server. > Requests parameters are not > available, at least not with Jetty 1.6.7 (and I would assume the same is > true for tomcat 6 and 7, did not check). I've got an enhancement request in for TC 7, and I'm working on a patch. I have it working -- I'm just working on the unit tests and documentation, now. > So, this leaves us with the issue with PUT not having the parameters > available, but at least the request method is now properly set. > > I was almost ready to switch to a different framework like > https://jersey.dev.java.net/. Almost .... Well, building a REST service on top of Cocoon seems like a mismatch: Jersey was created explicitly for REST services. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyZMVwACgkQ9CaO5/Lv0PCyiACgmprQv72BM35MiK5G7dN2t/lk GTkAn2O0wSCSvmaVH/R3EUlGUDrZN3Op =heIE -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
