on 12-02-2005 2:42 PM
Hi Group,
when you debug - how do you test your new changes?
When server is in state "debugging" i'm not able to deploy (deployment "hangs" till i "release from debugging")
So to debug the new CHANGES takes a lot of time..
When i set the flag "create and deploy archive" and press "debug" i get the exception "no connection to remote VM".
(Without the flag debugging works fine..)
Any ideas?
Thanks alot!
Simon
Hi Simon
It is strange that when the server is "debug ready" you are not able to deploy. This is usually not the case. How about
->switching off "create and deploy archive"
->deploy through the deploy function
->then launch debugging
Regards
Pran
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Simon,
I prefer not Web Dynpro Application debug profile type but following way:
1) Build and deploy new archive of wd project.
2) Create Remote Java Application debug profile. Specify your host, port and project. Set breakpoints etc.
3) Start debug
4) Select appropriate WD application and from context menu select Run
5) Debug. Find a bug. Stop debugging.
6) Make changes and repeat steps 1, 3, 4
Best regards, Maksim Rashchynski.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Simon,
Stopping is necessary because you need to synch running code and code in NWDS. Without stopping you can get inconsistemcy between running code and source code. The benefit is that you have 2 options to launch your application - from studio and from url, so it seems to be more flexible. Again, it is my personal opinion.
Best regards, Maksim Rashchynski.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.