Without looking at the Restlet code, i'm having problems with this simple
configuration. I'm using Spring 2.5.
value1
value2
and run the corresponding Spring test case.
@Test
public void
Hi Florian,
Thanks the contribution and for moving this extension forward. I've
integrated your extension into SVN trunk but not in the build process yet.
The plan is still to have it distributed in 1.2 as part of a more modular
distribution process.
NOTE: I haven't received your JCA yet. Coul
Hi Paul,
> I switched to using Jetty and I had the same problem -- the process
> didn't terminate. So I figured out that it was my fault by
> creating a deadlock. I removed that and now the process terminates when
> calling System.exit(0). So then I went and tried Simple again and it
> too
Hi Steve,
> Is there a way to do a POST with an "Expect:" header in Restlet?
> To use Expect you construct your POST except you leave off the
> body and stick in an "Expect: 100-continue". If the server is
> happy to receive your POST he returns status 100 and the client
> sends the normal
Hi Rob,
> The Restlet project sort of gives the message (by the example
> of restlet.org etc.) that Simple is the best thing to run
> Restlet servers on top of, when -- at least in my opinion --
> in fact it's really not.
I like the Simple because it has a small footprint and very good
scal
Hi Rob,
You are right to make this precision: no particular persistence technology
is favored by the Restlet API.
Here are some possibilities for resources:
- object database (such as db4o)
- XML database (such as eXist)
- manual JDBC calls
- EJB / JPA technology
- Hibernate (transparent O
I shyly point out that Restlet is very capable of interacting with simple
relational databases without requiring an object-relational mapping layer.
You definitely want the ORM layer if your application domain objects need to
be mapped to a complex multi-table relational structure.
On 1/12/08, Jer
Hi Raj,
[...]
> Basically i am trying to build a base URI says /servers/ then
> every server say
> server1 server2 etc forms the remainder of the URI like
> servers/server1.This
> URI in turn leads to accessing other URIs to collect data
> about server1.
OK.
> Need to make GET requests
8 matches
Mail list logo