Thank you, Gregor. This is good counsel. I have found there is a "- noserver" arg in the nbproject/build-gwt.xml file, in target "debug- connect-gwt-shell". There is also a target "debug-connect-gwt-shell- hosted" which seems not to include this arg, but I cannot figure out how to run that target either from within NB nor from the command line.
I will peel off to go over to the gwt4nb forums to get into discussions there about this issue. Before I do, can you now assure me that my code seems correct to you for implementing a standard GWT RPC setup and call? Thanks very much for your time and good counsel. I will come back to this topic later to report - hopefully - a successful conclusion. On Feb 15, 5:16 pm, gregor <[email protected]> wrote: > It looks like NB might be setting things up to run GWT hosted mode > with -noserver option deploying to glassfish. In that case you have to > make sure everything is set up properly for deployment to glassfish > (i.e. as external server), including web.xml etc. Normally one would > not recommend running -noserver option unless you had to, for example > if you are using EJB's or a non-java back end. It may be NB does this > because it is easier to debug hosted mode server code using glassfish > + -noserver. > > Probably simplest thing is to consult NB forums for clues on how to > stop NB doing this, i.e. get it to run hosted mode normally using > embedded Tomcat server. There should be a script somewhere you can > edit, or a way to install your own. The script you are looking for > should have "com.google.gwt.dev.GWTShell" in it after a long classpath > statement and one of the switches following should be -noserver as > well as -style and -out etc if this theory is correct. > > What IDE's do is simply write versions of standard GWT start up > scripts for you inserting their own choice of parameters, hiding the > details. They are trying to be helpful, but often it just causes > problems.The trick is to find out how to edit these scripts and take > control of them. > > Same is true of deploying your app in web mode to production/test > server IMO. It is much easier in the long run if you write your own > ant script to build a WAR rather than let your IDE do it for you. This > is especially true in team situation where different IDE settings can > cause all sorts of problems otherwise. > > On Feb 15, 12:51 am, BobM <[email protected]> wrote: > > > When I run in web mode, NB starts Firefox. Both hosted mode and web > > mode run against "localhost:8080/GWTwHibernate", so I think both are > > running using the application deployed to glassfish. > > . > > > On Feb 14, 6:22 pm, BobM <[email protected]> wrote: > > > > Yes. It certainly seems to be a glasfish message, but it is hosted > > > mode. I am using netbeans 6.5 and glassfish v3 prelude. When I click > > > "Debug main project" in NB, it deploys to glassfish but brings up the > > > hosted mode shel and runs the app in a sub shell. > > > > On Feb 14, 5:28 pm, gregor <[email protected]> wrote: > > > > > That looks like a glassfish message? Are we talking about hosted mode > > > > here or web mode? > > > > > On Feb 14, 8:07 pm, BobM <[email protected]> wrote: > > > > > > This is how the service is called: > > > > > > selectionSearchService.findAllLikeThis(serviceProvider, > > > > > selectionSearchCallBack); > > > > > > How the service is setup in the module xml file: > > > > > > <servlet path="/selectionSearchService" > > > > > class="org.bcs.server.SelectionSearchServiceImpl" /> > > > > > > this is the report from caught.getMessage(): > > > > > !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" > > > > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";><html><head><title>GlassFish/v3 > > > > > - Error report</title><style type="text/css"><!--H1 {font- > > > > > family:Tahoma,Arial,sans-serif;color:white;background- > > > > > color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans- > > > > > serif;color:white;background-color:#525D76;font-size:16px;} H3 {font- > > > > > family:Tahoma,Arial,sans-serif;color:white;background- > > > > > color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans- > > > > > serif;color:black;background-color:white;} B {font- > > > > > family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} > > > > > P {font-family:Tahoma,Arial,sans- > > > > > serif;background:white;color:black;font-size:12px;}A {color : black;} > > > > > HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 404 - </ > > > > > h1><hr/><p><b>type</b> Status report</p><p><b>message</b></ > > > > > p><p><b>description</b>The requested resource () is not available.</ > > > > > p><hr/><h3>GlassFish/v3</h3></body></html> > > > > > > There are no log entries showing on the hosted mode shell window; it > > > > > is clear. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
