hi:
i have a problem while using ijetty as a server on android to host
restlet service, the helloworld example. i try to access it from my laptop
and the android emulator web browser but both of them do not work. the
ijetty says that the service is unavailable. but if i deploy the service in
tom
Hi Nico,
UniformResource has two methods, doInit() and doRelease() that can be used
for this. However, be careful with your transaction strategy if your
representations need access to the DAO at writing time (after afterHandle()
is called, in the connector).You can used ServerResource#onSent callb
Hi,
i have a problem setting the challengescheme in the guard.
I've created a guard that decides authentication based on the cookie sent.
But when i use the following line:
MyGuard mGuard = new MyGuard (getContext(),ChallengeScheme.CUSTOM,
"Tradefields API Login");
In runtime i get: Challenge sc
Nicolas Rinaudo wrote:
>> Could you clarify what you mean by accept/ignore? I'm not sure what this
>> means in the context of Firefox/Safari.
>
> Right, sorry, that wasn't very clear.
>
> "Accept": the browser will load the page without complaint.
>
> "Refuse": the browser will fail to load the
> Could you clarify what you mean by accept/ignore? I'm not sure what this
> means in the context of Firefox/Safari.
Right, sorry, that wasn't very clear.
"Accept": the browser will load the page without complaint.
"Refuse": the browser will fail to load the page with an error message such as
Hello,
> Laurent,
>
> Thanks for quickly re-testing. I've entered a bug report:
>
> "Internal HTTP client slower than in 2.0 M6"
> http://restlet.tigris.org/issues/show_bug.cgi?id=1085
>
> As a workaround you can always add the org.restlet.ext.httpclient.jar and its
> dependencies (Apache HTTP
Hi Nicolas,
Nicolas Rinaudo wrote:
> Hey,
>
> We've just upgraded form RC 1 to RC 3 (we skipped RC 2 due to blocking
> issues), and there appears to have been some changes in the way SSL keystores
> are managed - our test self-signed certificate that worked perfectly with RC
> 1 now has issues
Hey,
We've just upgraded form RC 1 to RC 3 (we skipped RC 2 due to blocking issues),
and there appears to have been some changes in the way SSL keystores are
managed - our test self-signed certificate that worked perfectly with RC 1 now
has issues with RC 3.
The behaviour is a bit odd:
- Firef
Yes, I had thought about that, but a filter has a beforeHandle() and a
afterHandle() method, so I can easily set up a transaction before the
handling and easily perform a commit or a rollback in after the handling.
If I would use a BaseResource I would need to add these calls for each
extending cl
Hi Nico,
How about injecting your DAO on a BaseResource class and extending this in
every resource?
--
View this message in context:
http://restlet-discuss.1400322.n2.nabble.com/Restlet-and-DAO-tp4962381p4962395.html
Sent from the Restlet Discuss mailing list archive at Nabble.com.
Hi
I have a question about how to inject my DAO. I looked around a bit
(probably not long enough), and my guess at this point would be that I
implement a filter which places the DAO in the attributes of the Request
object. Is this the correct modus operandi? What about security? I'm not
very keen
If your method name is indeed createInboudRoot(), then you only have made a
small typo: there is a n missing in the word inbound. ;)
--
View this message in context:
http://restlet-discuss.1400322.n2.nabble.com/create-inbound-root-override-problem-tp4956547p4961436.html
Sent from the Restlet Disc
12 matches
Mail list logo