Hi Ian,
Yeah doing that now, its still hanging a lot
I don't know whats the problem. I guess the last option would be to
reinstall gwt

On Aug 28, 11:14 am, Ian Bambury <ianbamb...@gmail.com> wrote:
> I don't think that the problem is there, but try commenting out just that
> call and running the rest of the app. If the problem goes away, then I'm
> wrong :-)
> Ian
>
> http://examples.roughian.com
>
> 2009/8/28 Rahul <coolrahul18...@gmail.com>
>
>
>
> > Hi,
> > This is my code:
>
> > Client side, i am calling an RPC service to connect to sqlserver2005.
> > Its an simple login(very basic)
>
> > greetingService.greetServer3(username,password, new
> > AsyncCallback<Integer>()
> >                                                {
>
> >                                                       �...@override
> >                                                        public void
> > onFailure(Throwable caught) {
> >                                                                // TODO
> > Auto-generated method stub
>
> >                                                        }
>
> >                                                       �...@override
> >                                                        public void
> > onSuccess(Integer result) {
> >                                                                // TODO
> > Auto-generated method stub
> >                                                                if (result
> > == 1)
>
> >  Window.alert("log on successful");
> >                                                                else
>
> >  Window.alert("Please check the username and password");
> >                                                        }
>
> > My implementation on server side is
>
> >  public Integer greetServer3(String str, String str1) {
> >                                // TODO Auto-generated method stub
>
> >                                 try
> >                                    {
> >                                      Class.forName
> > ("com.microsoft.sqlserver.jdbc.SQLServerDriver").newInstance();
> >                                      conn =
> > DriverManager.getConnection("jdbc:sqlserver://
> > STI1121081:1433;database=Sql-obtv", "username", "password");
> >                                      stm =
> > ((java.sql.Connection)conn).createStatement();
>
> >                                      System.out.println("Values of string
> > name"+str+"value of
> > pass"+str1);
> >                                      rs = stm.executeQuery("select * from
> > Password");
>
> >                                      while (rs.next())
> >                                      {
> >                                          user =rs.getString("Username");
> >                                          pass = rs.getString("Pass");
> >                                                               }
> >                                      conn.close();
> >                                    } catch (Exception e) {
> >                                     connString = e.getMessage();
>
> >                                    }
>
> >                                   user =user.replaceAll("\\s+$", "");
> >                                   pass = pass.replaceAll("\\s+$", "");
>
> >                                    if (str.equals(user)&&
> > str1.equals(pass))
> >                                        return 1;
>
> >                                    else
> >                                        return 0;
>
> >                        }
>
> > Also I am not using the Google Application engine as i am integrating
> > with sqlserver2005. I have seen similar problems whenever i try
> > integrating with sqlserver2005. I am using jdbc4 driver.
>
> > On Aug 27, 8:49 pm, Ian Bambury <ianbamb...@gmail.com> wrote:
> > > I don't think you'll find it there Rahul, That was only really a
> > suggestion
> > > for next time :-)
> > > It sounds like a strange problem, but if you can provide some code, that
> > at
> > > least means that other people can have a play - sometimes it happens that
> > > the code people provide works OK for other people - it all helps to pin
> > it
> > > down though.
>
> > > Ian
>
> > >http://examples.roughian.com
>
> > > 2009/8/27 Rahul <coolrahul18...@gmail.com>
>
> > > > Hi Ian,
> > > > I did try to cut out the call tired to find it out, but i was not
> > > > successful in getting the answer whats causing the problem
>
> > > > Sorry for my ignorance but i did not knew anything about the issue
> > > > tracker. I would look at issue tracker first and if i am not able to
> > > > get solution to that problem ill paste my code here.
>
> > > > On Aug 27, 5:29 pm, Ian Bambury <ianbamb...@gmail.com> wrote:
> > > > > Hi Rahul,
> > > > > Why don't you cut out the call and find out?
>
> > > > > :-)
>
> > > > > It's very hard to answer questions like this when there is no code to
> > > > look
> > > > > at.
>
> > > > > There are no blindingly desperate problems with GWT that I know of
> > that
> > > > do
> > > > > this. Since the server side is not anything to do with GWT, then that
> > is
> > > > > very probably not a GWT problem (although connecting to the server
> > might
> > > > > be).
>
> > > > > In this kind of situation, I'd say that the first stop is the issue
> > > > tracker.
> > > > > Pretty much everything major has been picked up and even when there
> > is a
> > > > new
> > > > > release, the chances are that someone else will find it before you do
> > > > > (unless you are the most up-to-date, active and comprehensive user of
> > GWT
> > > > > out of the 20,000 of us here - I'm not, so I check the issue
> > tracker).
>
> > > > > Coming up with a simple example to demonstrate your problem is the
> > next
> > > > > step. If you take a copy of your problem project and cut it down step
> > by
> > > > > step will a) mean you end up with a good, reproducible example of the
> > > > > problem. But if your experience is anything like mine, you'll cut out
> > one
> > > > > bit which can't possibly cause the problem and discover that the
> > problem
> > > > > goes away. And then you have a Peter Glaze 'Doh!' moment (don't worry
> > if
> > > > you
> > > > > didn't get that 'Peter Glaze' reference reference, I'd be surprised
> > if
> > > > > anyone does). Anyway, you might well look at a bit of code that you
> > > > hadn't
> > > > > considered before.
>
> > > > > If you *do* get it down to a 10-50-line example, then you definitely
> > have
> > > > a
> > > > > problem, but then it is one that we can all reproduce and play about
> > > > with.
>
> > > > > So ... I don't have an answer for you, but if you can come up with a
> > demo
> > > > of
> > > > > it, I'll have a look.
>
> > > > > There used to be a problem like this where clicking on the screen
> > allowed
> > > > > the app to continue (something to do with multiple css files if I
> > > > remember
> > > > > correctly) but I'm sure that was fixed in about 1.3.
>
> > > > > Just my 2p worth.
>
> > > > > Ian
>
> > > > >http://examples.roughian.com
>
> > > > > 2009/8/27 Rahul <coolrahul18...@gmail.com>
>
> > > > > > Hi,
> > > > > > This is been happening a lot lately with me.
> > > > > > Whenever i am running the hosted mode, the hosted mode just hangs 4
> > > > > > out of 10 times. At the left end of window, it shows that
> > "Connecting
> > > > > > to site 127.0.0.1"
> > > > > > and if i just close it and start it again the application works or
> > it
> > > > > > just says the same message again as above. After a few tries it
> > starts
> > > > > > working.
> > > > > > This never happens when i am running on IE. Also my application
> > > > > > connects to sqlserver2005, is tht wht is causing this problem?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to