Is it necessary to keep BlazeDS jars always in WEB-INF/lib. When using Websphere can we add BlazeDS jars as shared libraries?
I am running into ClassLoader issues by keeping Flex libs in WEB-INF/lib and application libs in shared libraries.
Whatever approach (putting flex libs in WEB-INF/lib or shared libraries) I use I keep getting ClassNotFound errors. When I added flex libs in shared libraries, I get ClassNotFound for class that is in my WEB-INF/classes folder. How to solve this ClassLoader puzzle?
Is there anything that I do not know or it is just that Flex and BlazeDS are not good for production applications?
Well you can, but it is probably a far better fix to correct the class loader configuration issue you have rather than working around it. WebSphere has fairly extensive documentation about how class loaders work, I'd have a read of them.