Hmmm ... well, that would be a much more elegant solution certainly. I'm just
not sure if it's overkill for what I need to do. I mean, all I really need to
do is take data from a form, stick it in a PreparedStatement, execute a query,
and return some results.
Currently, it's not really a "separate webapp", it's only a servlet, and I've
put in a .jar with the other Magnolia dependencies, in the magnoliaAuthor and
magnoliaPublic webapps. Kind of ugly, but it more or less works.
The only problem I am having is that I stuck the results of my query in a
Request attribute (request.setAttribute("output",output) but when I then
forward to my .ftl (using RequestDispatcher.forward(request,response), as
recommended by Ruben, above) and try to print the results in my .ftl
(${output}) Magnolia says "output doesn't exist" or something like that, and
the page breaks.
How do you print out Request attributes in a .ftl?
If I can just figure out that bug everything would work. But I would like to
use the method you suggest. Th only problem is that I am [b]not[/b] using STK.
So when I make a Model class, what Magnolia class do I need to extend? Are
there any working example out there? I've been perusing the docs and can't find
any.
Thanks again for everyone for the helpful responses!
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=3f254fa9-4506-4830-8eee-44a5f18da5c4
----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
