Hi, I think the intention here is to store the most required attribute values in one common object and add it to session(there are some attributes that we always need when accessing application related data) and refer it when required. When trying to retrieve that object and if null we should create the object and add it to session, so would solve the problem of entering URL by hand without navigating through app home.
On Tue, Sep 3, 2013 at 11:58 AM, Danushka Fernando <[email protected]>wrote: > > On Tue, Sep 3, 2013 at 11:34 AM, Danushka Fernando <[email protected]>wrote: >> >>> Hi >>> Is Logged in user related to an appfactory application? I don't think so. >>> >> Y not, there are many places we need logged in user in the application. >> > Still this is not related to APPLICATION_INFO > >> And for other things we could have this object in application space >>> rather than session space I think. WDYT? >>> >> Earlier, I thought the same thing. But if we are gonna include >> application owners , we need to do it in the application scope. >> >> IMO, It is like this, when application home is loaded for a particular >> application APPLICATION_INFO object is created and put to the session with >> details I mentioned in the first mail of this thread. >> So every time switch applications ,relevant APPLICATION_INFO object is in >> the session. WDYT? >> > +1 for this idea. > > But what happens if user paste some url other than home page. How do we > detect that application is changed? We need to have some check before > loading each page then. > >> >>> >> Thanks & Regards > Danushka Fernando > Software Engineer > WSO2 inc. http://wso2.com/ > Mobile : +94716332729 > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Thanks & Regards, Ashansa Perera Software Engineer WSO2, Inc
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
