Thanks much, Jerome.
I used the boilerplate example on the wiki, and it seems to be working
well.
Mark
On Oct 17, 2008, at 3:13 AM, Jerome Louvel wrote:
Hi Mark,
Thanks for this feed-back. We realize that the Spring extensions
still lack
a comprehensive documentation. We even have a RFE for that where
I've just
added your comments:
"Improve Spring documentation"
http://restlet.tigris.org/issues/show_bug.cgi?id=614
I won't make any promise but we are currently working on improving
the wiki
structure and content for the launch. We still have a long way to go
and
need help from the community on this front (any wiki author
candidate out
there ?).
One thing that will help is the upcoming merging of
"com.noelios.restlet.ext.spring" into "org.restlet.ext.spring" in
Restlet
1.2. This will give a more unified view of the Spring support in
Restlet.
Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com
-----Message d'origine-----
De : Mark Petrovic [mailto:[EMAIL PROTECTED]
Envoye : jeudi 16 octobre 2008 17:16
A : [email protected]
Objet : Re: Spring configuration example using
com.noelios.restlet.ext.spring package
I took a look at the javadoc for both org.restlet.ext.spring and
com.noelios.restlet.ext.spring and conclude that the method outlined
here, based on org.restlet.ext.spring,
http://wiki.restlet.org/docs_1.1/13-restlet/g2/59-restlet.html
is the most viable approach.
Having read through that example, I'm still left with the impression
that the example contains a mix of specific and general treatments of
the subject. For example, I don't understand why this point is raised
"In this example, the last URI pattern has to be customized to accept
complete URIs (possibly including slashes) as the last component of
the pattern. We use Spring's nested properties to drill into the
configuration of the URI pattern along with Spring's mechanism for
accessing a static field in a class."
And by "don't understand" I do not mean "I object to the point
raised", but rather "what, in my lack of understanding, is this really
trying to tell me, and does it matter in my case?". The Spring
lookup-
method reference strikes me the same way: is this central to restlet
configuration with Spring, or is it an advanced idiom that I can do
without for now?
I'm not asking for a clarification of this particular point, but
instead for someone to offer a second standalone example of how to
configure a simple restlet-based app using Spring. Many, many times
in my study of a thing I resort to second and third and fourth
references on the subject to gain an understanding of what is
fundamental to a subject's elucidation, vs. what is specific in the
course of that illustration. This is one of those times, and I'm sure
others routinely resort to this same approach.
Would someone be kind enough to post some non-proprietary code showing
how they configured their restlet app using Spring? The example would
configure an app no more complex than the FirstResouce app found
elsewhere on the site.
Thanks much. Hopefully posterity will benefit from my supplications
as much as I do now.
Mark
On Oct 15, 2008, at 1:57 PM, Mark Petrovic wrote:
Good day.
I notice that both the FAQ and Wiki have sections treating the use
of the org.restlet.ext.spring package to manage a restlet app in a
Spring container.
Is there a similar example someone might offer on using the
com.noelios.restlet.ext.spring package to manage a restlet app in
the same way? The FAQ says such a configuration option exists, and
I'd like to read about it.
Thanks.
Mark
