Re: J2EE and debug in hosted mode

2008-12-17 Thread olivier
Well the GWT module isn't loaded at all... I use seam remoting instead of GWT Servlets. RPC works fine, the issue is that GWTSehll doesn't see the GWT modules in the page... On 15 déc, 18:02, jos jot...@gmail.com wrote: Bandesz, Gregor is pointing you in the right direction w/ option #1,

Re: J2EE and debug in hosted mode

2008-12-15 Thread olivier FRESSE
I don't think so... -noserver only removes the GWT embedded tomcat which manages the GWT RPC mechanism. I'm afraid you'll still have 2 java processes. One for the client, one for the server... In fact, the GWTShell plays the role of the browser. I'don't see how it could be possible to embed the

Re: J2EE and debug in hosted mode

2008-12-15 Thread jos
Bandesz, Gregor is pointing you in the right direction w/ option #1, and the link he gives is enough to eventually get you there, but there is one thing you have to do in your GWT code or it will never work. Your RPC servlets all have a setServiceEntryPoint() call that is made to tell them where

Re: J2EE and debug in hosted mode

2008-12-14 Thread Bandesz
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 greg.power...@googlemail.com wrote: couple of approaches

Re: J2EE and debug in hosted mode

2008-12-14 Thread gregor
Well, that depends on your IDE and your app server, and unfortunately I use Intellij and JBoss. In JBoss the magic command is: set JAVA_OPTS=-Xdebug - Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n %JAVA_OPTS % which is in the JBoss startup script. I then set up a debug session

Re: J2EE and debug in hosted mode

2008-12-14 Thread Bandesz
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.

Re: J2EE and debug in hosted mode

2008-12-14 Thread gregor
The simplest is to run hosted mode with the -noserver flag. Then you deploy your EAR with your Ant script once and run debug your GWT client code in hosted mode just hitting the refresh button as you go. On Dec 14, 5:01 pm, Bandesz band...@blog.hu wrote: I wrote it wrong, not the debug is the

J2EE and debug in hosted mode

2008-12-07 Thread Bandesz
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

Re: J2EE and debug in hosted mode

2008-12-07 Thread gregor
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