Do you happen to have this working in combination with Blossom? I'm mostly confused about how to configure everything so I can use Blossom and a standard Spring DispatcherServlet for some non-Blossom controllers...
Tom On Feb 23, 2011, at 1:38 PM, Kimmo Björnsson wrote: > > Hi Tom. We are running a DispatcherServlet (actually multiple) > alongside Magnolia for ajax-requests. It works perfectly. If you have > any questions or want some code to put you in the right direction I > might be able to help also. I feel it's the right way for you to go > too. > > On Tue, Feb 22, 2011 at 3:37 PM, Thomas Duffey <[email protected]> wrote: >> Hi Tobias, >> Thanks for the response -- I have wondered for a while if I can run a >> standard Spring DispatcherServlet alongside Blossom. We have some Blossom >> Templates + Magnolia Pages that are "real" Magnolia pages and some that are >> used only for providing actions as you describe below. I will give it a >> shot. >> Tom >> On Feb 22, 2011, at 7:42 AM, Tobias Mattsson wrote: >> >> Hi Thomas, >> It should be possible to hide those pages without going into security by >> customizing the tree control used by the website tree. >> In case those pages are mainly used for providing actions, like processing >> POST requests and returning JSON or redirects you might be better off to >> simply use a plain Spring DispatcherServlet sitting along side Magnolia and >> taking care of those requests on its own. You can set up such a solution >> either by having the DispatcherServlet running in the Magnolia filter chain, >> just add it to your module descriptor, or by adding it to web.xml. If you >> add it to web.xml use InstallationAwareDispatcherServlet available in >> Blossom 1.2 which defers initialization of the servlet until Magnolia has >> completed its update/install -phase. Also, when adding it in web.xml you >> might need to add the Magnolia context filter in front of it to access the >> repositories. >> In case you use the actual pages, maybe for configuration of the actions, >> then another approach might be to read that configuration from >> config:/modules/<yourModule>/some/path. With Blossom 1.2 its possible to >> have such configuration beans read with content2bean and made available for >> dependency injection / autowiring. >> // Tobias >> On Feb 18, 2011, at 9:50 PM, Thomas Duffey wrote: >> >> Will, >> Perhaps I just don't know the proper ACL settings for this. Suppose I have >> the following pages: >> /page >> + /page/active >> + /page/addSubpage >> Those last two are using Blossom Templates for processing. I need editors >> to be able to POST data to those pages, which I thought meant I had to grant >> read-only access to /page and its subpages. This is what I have done and it >> is working great but what would be even better would be to have a way to >> prevent that entire tree of pages from showing up in Admin Central unless >> you are the superuser or something. >> Make sense? Is there a way to make this happen using ACLs? >> Tom >> On Feb 18, 2011, at 2:19 PM, Will Scheidegger wrote: >> >> I guess I'm missing a point here. ACL does not work for you? >> >> -will >> >> On 18.02.2011, at 20:55, Thomas Duffey wrote: >> >> I'm wondering if these is a way to hide pages in Admin Central, either on a >> page-by-page basis or based on some rule like not showing any pages that are >> read-only. We're using Blossom a lot these days and have pages tied to >> Spring controllers that we'd like to keep out of sight from our content >> editors. They do need read-only access to these pages to be able to use >> their functionality (A lot of them provide handlers for Ajax requests used >> on the author side) but I haven't found a way to keep them out of the tree. >> >> >> >> ________________________________ >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <[email protected]> >> ---------------------------------------------------------------- >> > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > -- Tom Duffey [email protected] 414-915-3915 ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
