File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Flex and the fly likes Flex and application server choices Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Frameworks » Flex
Bookmark "Flex and application server choices" Watch "Flex and application server choices" New topic
Author

Flex and application server choices

Paul Sturrock
Bartender

Joined: Apr 14, 2004
Posts: 10336

Hi Bernard and Jeremy. Does your book cover much about integrating with particular servlet containers or application servers? I've found fairly poor support for some fairly key architectural features of Flex if I'm using containers other than Tomcat that would have been great to know before trying to user them (and Adobe's documentation certainly leaves a gap in the market for someone to fill!). How much depth do you go into with things like their custom security model for example? Do you talk about more "enterprise" topics like Flex's behaviour on clustered servers etc?


JavaRanch FAQ HowToAskQuestionsOnJavaRanch
Jeremy Anderson
author
Ranch Hand

Joined: Apr 26, 2005
Posts: 32
Paul Sturrock wrote:Hi Bernard and Jeremy. Does your book cover much about integrating with particular servlet containers or application servers? I've found fairly poor support for some fairly key architectural features of Flex if I'm using containers other than Tomcat that would have been great to know before trying to user them (and Adobe's documentation certainly leaves a gap in the market for someone to fill!). How much depth do you go into with things like their custom security model for example? Do you talk about more "enterprise" topics like Flex's behaviour on clustered servers etc?



I'm not sure what you mean by integrating with a particular servlet container. I typically write portable applications that don't rely on any container specific integrations, and as far as I can tell BlazeDS is container agnostic. As far as security goes, we leverage Spring Security on the server side to authenticate and authorize the users and a simple login form in the Flex application.

Flex shouldn't behave any differently in a clustered environment than a non-clustered environment as the state should be maintained in the application itself and all calls back to the server should be stateless in nature.
Paul Sturrock
Bartender

Joined: Apr 14, 2004
Posts: 10336

Im mean the points where some container configuration is required (session replication, security etc). It's not my experience that BlazeDS is container agnostic (isn't there Tomcat code in its source, for example?) hence the question . Custom security requires, for example, a custom TomcatValve in order to function in Tomcat (or JBoss), and there is no equivalent in WebSphere, so custom security can't work in that particular container. I'm just curious if youre book touches on these sorts of integration points at all - because it would be a godsend if it did!
Bj Allmon
author
Greenhorn

Joined: Oct 23, 2010
Posts: 13
Paul Sturrock wrote:Im mean the points where some container configuration is required (session replication, security etc). It's not my experience that BlazeDS is container agnostic (isn't there Tomcat code in its source, for example?) hence the question . Custom security requires, for example, a custom TomcatValve in order to function in Tomcat (or JBoss), and there is no equivalent in WebSphere, so custom security can't work in that particular container. I'm just curious if youre book touches on these sorts of integration points at all - because it would be a godsend if it did!


We demonstrate using BlazeDS through the Spring security implementation which may hide many of these details. In our examples, we simply leverage the container's role based security. This allowed us to more quickly get to the development-side of securing and personalizing a Flex app. Yes, there will be administrative nuances on how to handle security between containers. Leveraging a non-container specific security framework is the way to lessen the pain.

I've never seen anything good come to those who use container specific implementations. Over time, it becomes painful.
 
 
subject: Flex and application server choices