This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
I don't know exactly if I elaborated my question properly ...
I don't have any idea about how flex works but in the java classes flexSession is used and LoginCommand interface of flex.messaging.security is used.
I thought maybe it has something to do with these classes in java? If i want to develop flex free log in for the same application would it be out of these classes or I would have to still use these classes? because on client side any way i have actionscript flex, i.e .as files and mxml files etc...
Are you using Flex custom security? If you are then you need these. However, you can just have an unsecured flex application and deploy it in a secured web application (i.e. just use standard container managed security). If you do that Flex plays no part, though the requests it makes will be secure.
I am using flex based authentication, i have custom class which implements the LoginCommand interface and implements its methods ..
I use the Jboss security SimplePrincipal also and add this principal to the FlexContext
Session used is also FlexSession
So I have application which is using flex security with jboss.
I don't know how can i develop the login which can exclude the resources of flex to be loaded on the home page.. .and i just get the html login without loading all the .swf files or other flex resourses.
can you please elaborate the answer in detail if you can please, as i see you have good knowledge about it which i don't have for now.
What do you mean by "all the contents"? I've just checked a very slim Flex app we have that includes custom security any I'm not sure I'd list it as that big (bigger than HTML content, but still a relatively small 97Kb)
just load html or something and do the loading in the background
You can't use Flex security without loading the Flex application that uses it.
Sounds like my earlier comment is maybe relevant then. You need to partition your Flex application and load components on demand. For example, you could have a loader application that contains nothing more than your authentication view (i.e. a login dialog of some sort). This will download quickly is its a small application. After (or during) successful login you can load the next bit of your application - have a look at this.