|
Keep in mind that if you use the Servlet Wizard, the servlet mapping is established automatically. As far as debugging goes, if you use the Project Navigator view, Debug works as it always has.
-----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Joe Pluta Sent: Thursday, September 21, 2006 10:49 AM To: 'Websphere Development Studio Client for iSeries' Subject: Re: [WDSCI-L] Debugging web applications in IBM RationalSoftwareDevelopment Platform Version: 6.0... Mike! Hold on! Don't panic! I've complained about this particular issue before, and I never seemed
to
get anyone's attention. Maybe now that it's someone besides me,
they'll
listen <grin>. Anyway, the short answer is that WDSC V6 took this feature away. How
or
why, I don't know, but whereas in V5 you could launch a servlet using
a
simple right-click and debug on server, you can no longer do it in V6. The last time I brought the issue up, I got the response that I could map
the
servlet in my Deployment Descriptor and then launch it from there. The fact that this means I have to keep my descriptor open when I
didn't
have to before (not to mention having to map the servlet in the first place) didn't seem to make any impression. The fact that every other type of runnable item, from simple Java classes to HTML to JSP, could be
launched
using a right-click also didn't phase them. So, the long answer is that if you want to launch a servlet using a right-click, you must map it in your deployment descriptor (under Servlets) and then you can launch it from there, NOT from the source.
Otherwise,
you have to type the servlet address into the browser (or write an HTML
page
to launch it). Which brings up one other issue: does anyone know how to bring up a browser window inside of WDSC without actually launching anything? Sometimes
I
just want to type in an address to test something, and unless I already
have a
browser window up, I can't do it. I have to launch something. JoeFrom: Mike Burdette Hi all: Well, I made the move from WDSC 5.0 to WDSc 6 (Rational). Of course
I
burned all bridges and opened up my workspace with WDSc 6 without arecentbackup. After creating multiple workspaces and trying several different
ways, I
amunable to debug my web application in Rational at all. After
creating a
new workspace and importing my existing projects, when I select myservletand choose to "Debug on Server", I am told, "Could not find a server
to
run the selection." The next time I try to debug it, I am not given
the
"Debug on server" option, only "Debug". When I select this, I ampresentedwith the "Create, manage, and run configurations" dialog box. I
select
WAS6.0 under configurations and it looks like a new config is being set
up.
Iam told however that : " The Enterprise Application must contain atleastone Application Client." However the only option I am given under
the
Application Client module is the "Default" option, which is
apparently
notthe right answer, but it is the only answer you can choose. I am frustrated, and tired of trying the same thing over again with
the
same results (yes, I am living this definition of insanity). I have
used
WDSc 5.0 for 2 years, and thought I understood how it worked, but I
was
very wrong it appears. Does any of this sound familiar to anyone and can you offer any
help? I
have followed the steps in the help section and tutorials of WDSc,
but
amnot getting the results advertised.-- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.