-Original Message-
From: Adam Taft [mailto:[EMAIL PROTECTED]
It should be either one of two ways:
a) bean id=fooResource scope=request class=FooResource /
b) bean id=fooResource scope=prototype class=FooResource /
-a- should theoretically work in a servlet environment (like
he's
I used the factory approach too. See my post from 9/5/2007 yet
another way to add spring to restlets, any opinions?
On 9/14/07, Adam Taft [EMAIL PROTECTED] wrote:
Interesting. I'm using lookup-method in production without any problems.
But, there are no transactions and no other proxies so
Hi-
In a quest to improve the springyness of the current spring/restlet
integration I'm using, I've been playing around with some of the new
Spring related classes in the 1.1 development trunk. I think I've
managed to achieve a better fit than I had before, so I thought I'd
share it and get some
Tom McGee wrote:
Should this in the appicationContext.xml:
bean id=fooResource scope=request class=FooResource /
be this:
bean id=fooResource scope=request class=FooResource
scope=prototype/
It should be either one of two ways:
a) bean id=fooResource scope=request class=FooResource /
b)
If not me, than I'm sure others would benefit. There's obviously a lot
of ideas on how to do Spring integration with Restlet. I think there is
even an RFE or two kicking around with some additional ideas.
More ideas the merrier (IMHO)!
Adam
Tom McGee wrote:
I have an approach that uses
5 matches
Mail list logo
