I would agree with those mappings. My understanding from previous threads:
Restlet (and subclasses): part of the web application plumbing, long-lived,
must be thread safe.
Resource: ephemeral, created and destroyed on demand, need not be thread
safe. Maps to one instance of a class of addressab
Is there a guideline when one should extend Restlet vs. extens
Resource? My rationalization is that: if X represents some kind of
"physical" resource, the one should extend Resource; if X represents
some kind of service, e.g., a "search service," then one should
extend Restlet.
Opinions?
Hi Yousef,
Based on the stack trace, I tried to lookup the NPE at line 212 in Finder.
It doesn't correspond to the latest in SVN trunk nor to the latest in 1.0
branch.
Could you test again with the latest version?
Best regards,
Jerome
> -Message d'origine-
> De : news [mailto:[EMAIL
3 matches
Mail list logo