To me it seems there is a problem with your approach. It looks like
PadroesSession is a singleton class per entire server application, and
it holds only one request and session a time, while in a multi-client
application you will have a session for each client connection. This
means that:
- if
An serializable object from the persistence side.
On Wed, Jun 16, 2010 at 6:46 AM, Magnus alpineblas...@googlemail.comwrote:
What's PersonDTO?
Magnus
On 3 Jun., 22:36, Bruno Lopes bruno.lourenco.lo...@gmail.com wrote:
Then on the server side for the LoginService
public LoginResponse
What's PersonDTO?
Magnus
On 3 Jun., 22:36, Bruno Lopes bruno.lourenco.lo...@gmail.com wrote:
Then on the server side for the LoginService
public LoginResponse login(String username, String password) {
LoginPService loginService = ServiceLocator.getLoginService();
PersonDTO
Hi,
thank you for the code! I adopted it to my application.
So you authenticate the user via the remote service! But how do you
actually store the user context the app is running in? Do you do some
session management?
Thanks
Magnus
On Jun 2, 7:15 pm, Bruno Lopes bruno.lourenco.lo...@gmail.com
YES
on the server side I have something like this:
public class PadroesSession implements Serializable{
private static PadroesSession padroesSession=null;
public static PadroesSession getInstance(){
if(padroesSession == null){
padroesSession = new PadroesSession();
Then on the server side for the LoginService
public LoginResponse login(String username, String password) {
LoginPService loginService = ServiceLocator.getLoginService();
PersonDTO personDTO = null;
try {
personDTO = loginService.getUserByUsername(username);
Hi,
I cannot find a minimalistic example that shows how to realize a login/
logout functionality.
Could please someone point me to such an example?
I also wonder where to put the different things. For example, the code
that immediately reacts on the login button could be placed within
the client
Hi Alpine Bluster,
look at this code:
public void onModuleLoad() {
this.setLoginPanel();
loginButton = new Button(Login);
loginButton.addListener(new ButtonListenerAdapter() {
public void onClick(Button button, EventObject e) {
userAuthentication();
}
});
to show the login screen.
-Manolo
On Wed, Apr 7, 2010 at 8:17 PM, yccheok yancheng.ch...@gmail.com wrote:
Does anyone have a good code example, on how to implement login/logout/
remember me feature, using GWT, with concern on Cross-Site Request
Forgeries.
My plan is to use HttpOnly
Does anyone have a good code example, on how to implement login/logout/
remember me feature, using GWT, with concern on Cross-Site Request
Forgeries.
My plan is to use HttpOnly :
http://www.codinghorror.com/blog/2008/08/protecting-your-cookies-httponly.html
However, I am not sure whether
the GWT application it
has to ask the server via RPC to know if the user has the appropriate
cookies, if not you have to show the login screen.
-Manolo
On Wed, Apr 7, 2010 at 8:17 PM, yccheok yancheng.ch...@gmail.com wrote:
Does anyone have a good code example, on how to implement login/logout
if the user has the appropriate
cookies, if not you have to show the login screen.
-Manolo
On Wed, Apr 7, 2010 at 8:17 PM, yccheok yancheng.ch...@gmail.com wrote:
Does anyone have a good code example, on how to implement login/logout/
remember me feature, using GWT, with concern on Cross-Site
12 matches
Mail list logo
