:
x.gwtlogin.server.GwtLoginServiceImpl
...
This actually makes more sense than the previous behaviour,
GwtLoginServiceImpl is not in the project.
On 8 abr, 18:52, Ivan M supertra...@gmail.com wrote:
Sorry, too fast. I made it work including x.gwtlogin in x.dt as a
module with no entry point. I
Could you (or somebody) be more specific about this?. I can't run the
project in hosted mode, I get the following error:
java.lang.IllegalStateException: No such servlet: GwtLoginService
The service is in another project and it looks like it isn't started
when starting the main project. I have
Hello all,
I'm facing my first GWT development. I had the idea of developing a
project with a module which I have called x.gwtlogin. The server of
this module can perform queries on a LDAP server. My idea is to have
an instance of this module running in the application server and use
its server
Sorry, too fast. I made it work including x.gwtlogin in x.dt as a
module with no entry point. I didn't need to copy the server classes,
so I have a single server as I wanted.
On 8 abr, 17:28, Ivan M supertra...@gmail.com wrote:
Hello all,
I'm facing my first GWT development. I had the idea
On 31 mar, 11:34, Thomas Broyer t.bro...@gmail.com wrote:
On 31 mar, 12:55, Ivan M supertra...@gmail.com wrote:
Every request has to be secured and verified on the server side.
Whether you pass a login/password pair or a ticket (that could be
your session ID, managed transparently by your
Being a newbie I can't fully understand the superiority of the client-
side approach over Magius' session solution. As far as I understand,
keeping the user's credentials in the client means they must be sent
to the server and this must verify them in every service request.
However, with Magius'
