hello,
Unfortunately, your suggestion did not work. I've reduced the code in
the hope the problem could be solved. First of all, I removed all the
Spring stuff. The web.xml file only contains the Restlet stuff. I do not
think the problem is in web.xml. Please continue reading for my rationale.
I've added to the silly sample app the ability to create new resources
via POST. Instructions are same as before: unzip, exec 'ant run'.
http://www.cwinters.com/raw/RestSampleBook.zip
Have fun!
Chris
--
Chris Winters ([EMAIL PROTECTED])
Lead Software Developer
Vocollect Healthcare Systems
Jerome Louvel wrote:
In this case that would make sense. And the Restlet framework will support
this in a convenient way at the connector level. You will be able to pass
your "X-Subscribable" and "X-Subscriber" URIs either as call attributes or
as call properties (via a subclass of Call).
Great
Chris,
> For instance, say I wanted to implement a publish/subscribe
> system using
> HTTP. One way to do this uses header information to
> communicate between
> the publisher and subscriber -- the server may add
> 'X-Subscribable: URI'
> to any resource that can be subscribed to, the clien
Jerome Louvel wrote:
...
In your case, why would you need to manipulate headers manually? My
assumption is that most applications will not require direct access to
protocol headers. So, it is better to provide an higher-level view (via the
Call object) and leave the container and connectors deal
In beta 17, you could manipulate headers via the object returned by
Call.getConnectorCall(). In beta 18, I'll provide a new mechanism based on
Call Converters and maybe in addition connector parameters.
In your case, why would you need to manipulate headers manually? My
assumption is that most ap
Jerome Louvel wrote:
Sure you can, just set the call.redirectRef property. For the HTTP
connectors, it will be mapped to the "Location:" response header.
Great -- I didn't know that property had client-side visibility. (Still
some jumble in my head about References and how they're used.)
And
Hi Chris,
Sure you can, just set the call.redirectRef property. For the HTTP
connectors, it will be mapped to the "Location:" response header.
Best regards,
Jerome
> -Message d'origine-
> De : Chris Winters [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 14 août 2006 16:32
> À : discuss@r
(picking up a thread from a few days ago about retrieving client headers
...)
Jerome Louvel wrote:
...
That's exactly the plan, allow the creation of a custom Call (subclass if
necessary) from the ConnectorCall or the other way around for client
connectors.
So now I've hit the 'other way arou
Hi Marcel,
I've had a look at your case. The problem seems to be in this code snippet:
for ( ResourceMapping mapping : resourceMappings ) {
Map restletMap = mapping.getRestletMap();
for ( String key : restletMap.keySet() ) {
LOG.info(key + "/" + res
Hi all,
I'm considering two options for this Wiki request:
1) Install a Wiki engine on the Restlet.org machine: this will need to wait
until I migrate the machine to a new hosting service in December and until I
have some spare CPU cycles :)
2) Use the Wiki feature of Java.net
(http://wiki.java
11 matches
Mail list logo
