I wrote it wrong, not the debug is the problem, I just want to run the enterprise application (EJB+Web) in Hosted Mode, I wrote debugging because hosted mode runs if I debug the web application.
If I understand correctly, the build-gwt.xml is responsible for the hosted mode. If I run the ent. app., the build.xml simply compiles the EJB and the Web project, makes an EAR package, and starts glassfish in debug mode. So how can I write a build file which runs the whole application in gwt hosted mode? This is a bottleneck in my development, because the deploy time is now more than 1 minute. If I could use as I wrote it, the hosted mode shows the changes in couple of seconds, and the autodeploy on the server side is just seconds. Bandesz On Dec 14, 5:49 pm, "olivier FRESSE" <[email protected]> wrote: > When you run in hosted mode, you have 2 java processes running. > The glassfish one, and the GWT shell. > Debugging the glassfish side is easy, it comes OOTB in Netbeans. > > Debugging the client side is quite easy too. > You just need to change the way the GWTShell is launched : > > java *-Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n > * -Xmx256M -cp > "$APPDIR/src:$APPDIR/bin:/home/ofe/dev/gwt-linux-1.5.3/gwt-user.jar:/home/ofe/dev/gwt-linux-1.5.3/gwt-dev-linux.jar" > com.google.gwt.dev.GWTShell -out "$APPDIR/www" "$@" > ext.test.MyAppli/MyAppli.html; > > next you can attach the netbeans debugger to the Shell. > > Is it what you're looking for ? > > O. > > 2008/12/14 Bandesz <[email protected]> > > > > > Thx for the answer, but I need an exact howto, how can I debug the > > whole J2EE application with Hosted Mode using Glassfish and Netbeans. > > > As I said, I searched a lot and haven't found a good description. > > > Bandesz > > > On Dec 8, 4:34 am, gregor <[email protected]> wrote: > > > couple of approaches > > > > 1) Simply use -noserver option. You need a build script to deploy your > > > RPC servlets and your EJB layer to Glassfish on demand and activate > > > remote debugging to make this work effectively, but lots of people do > > > it this way. See > > > >http://code.google.com/docreader/#p=google-web-toolkit-doc-1-5&s=goog... > > > > 2) You can run your RPC servlets in hosted mode Tomcat instance > > > leaving your session beans on Glassfish with a bit more work. You need > > > to use trad JNDI to try for a local reference to your session beans, > > > and if that fails go for the remote reference instead. I don't think > > > the new annotation stuff works for this.That way you get a local ref > > > in production and a remote one in dev from the same code. If you use > > > the ServiceLocator pattern it makes this easier. > > > > On Dec 7, 2:26 pm,Bandesz<[email protected]> wrote: > > > > > I'm developing a J2EE application with GWT using NetBeans 6.5, > > > > Glassfish v2. > > > > > If I debugging only the web project, I can't use any Session Beans > > > > from EJB project, becase I get "Cannot resolve reference Unresolved > > > > Ejb-Ref..." error. I tried in every way to make <ejb-local-ref> tags > > > > in web.xml (or in ejb-jar.xml), but the error stays. (I see now that > > > > it's a dead end) > > > > > If I debugging the enterpise project, everythings works except the > > > > hosted mode. > > > > > I searched a lot, but I can't make this work, please help. > > > > > Thanks, > > > > Bandesz > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
