[Catalyst] Catalyst and Java
I have a handful of java servlets that I would like to 'front-end' with my Catalyst application, essentially using Catalyst to provide authentication/authorization before passing along the browser requests to the servlet. I don't need session information in the servlet, and I'm willing to leave the servlet unsecured on an obscure port (network protected, of course) in order to allow Catalyst to more easily interact with it. In my mind, I see Catalyst behaving as a proxy, managing the entire conversation, but I'd also be open to some kind of redirection solution. Does anyone have experience with doing something like this? I'd appreciate any insight or direction. -Tim ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Catalyst and Java
On Wed, Oct 31, 2012 at 3:50 AM, Tim Anderson tja...@gmail.com wrote: I have a handful of java servlets that I would like to 'front-end' with my Catalyst application, essentially using Catalyst to provide authentication/authorization before passing along the browser requests to the servlet. I don't need session information in the servlet, and I'm willing to leave the servlet unsecured on an obscure port (network protected, of course) in order to allow Catalyst to more easily interact with it. In my mind, I see Catalyst behaving as a proxy, managing the entire conversation, but I'd also be open to some kind of redirection solution. Does anyone have experience with doing something like this? I'd appreciate any insight or direction. -Tim ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/ This would be fairly do-able if you used REST for inter-app communication. Or something like Message::Passing, which allows you to send a message to a queue, which could be subscribed to from both ends, thus allowing the apps to talk to each other. If the Catalyst app is acting as a proxy to the servlets, I would think you could do a pretty regular authentication/authorization/session set up with it and just pass along whatever other info you need to the servlets via the aforementioned means. -- Devin Austin http://www.dhoss.net 9702906669 - Cell ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Catalyst and Java
On Wed, Oct 31, 2012 at 8:41 AM, Devin Austin devin.aus...@gmail.com wrote: On Wed, Oct 31, 2012 at 3:50 AM, Tim Anderson tja...@gmail.com wrote: I have a handful of java servlets that I would like to 'front-end' with my Catalyst application, essentially using Catalyst to provide authentication/authorization before passing along the browser requests to the servlet. Does anyone have experience with doing something like this? I'd appreciate any insight or direction. This would be fairly do-able if you used REST for inter-app communication. Or something like Message::Passing, which allows you to send a message to a queue, which could be subscribed to from both ends, thus allowing the apps to talk to each other. If the Catalyst app is acting as a proxy to the servlets, I would think you could do a pretty regular authentication/authorization/session set up with it and just pass along whatever other info you need to the servlets via the aforementioned means. Another approach worth considering is to wrap the servlets up in a model. This often takes a bit longer and more thinking in the set-up phase but will give you code that is easier to reuse in other places. I've done this kind of problem both ways and either is fine but I'd lean to the model. You would end up with something you could run with Catalyst/Flea/Mojolicious/in-line-plack-with-auth-middleware/command-line/whatever. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Catalyst and Java
Thank you both for your suggestions. Creating my own model is along the lines of what I was thinking, but I know in advance that this is going to really stretch my abilities. Another possibility that has occurred to me since my original post is that I could remove the authentication to Apache (using Catalyst::Authentication::Credential::Remote). If the authentication is at that level, I know I can get it to protect both resources and provide a seamless experience to the user. Somehow, though, creating my own model seems like the more appealing option -Tim On Wed, Oct 31, 2012 at 12:22 PM, Ashley Pond V a...@sedition.com wrote: On Wed, Oct 31, 2012 at 8:41 AM, Devin Austin devin.aus...@gmail.com wrote: On Wed, Oct 31, 2012 at 3:50 AM, Tim Anderson tja...@gmail.com wrote: I have a handful of java servlets that I would like to 'front-end' with my Catalyst application, essentially using Catalyst to provide authentication/authorization before passing along the browser requests to the servlet. Does anyone have experience with doing something like this? I'd appreciate any insight or direction. This would be fairly do-able if you used REST for inter-app communication. Or something like Message::Passing, which allows you to send a message to a queue, which could be subscribed to from both ends, thus allowing the apps to talk to each other. If the Catalyst app is acting as a proxy to the servlets, I would think you could do a pretty regular authentication/authorization/session set up with it and just pass along whatever other info you need to the servlets via the aforementioned means. Another approach worth considering is to wrap the servlets up in a model. This often takes a bit longer and more thinking in the set-up phase but will give you code that is easier to reuse in other places. I've done this kind of problem both ways and either is fine but I'd lean to the model. You would end up with something you could run with Catalyst/Flea/Mojolicious/in-line-plack-with-auth-middleware/command-line/whatever. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/ ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
