× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Joe:

lol ... well, I certainly feel a LOT better if this contraption has 
frustrated even Joe Pluta ... whew ... though I do not think I will be 
writing any WDSC books any time soon.
AND I have also wondered how you would launch a browser in the view 
without actually running something....good question!

I believe I have my servlet configured in my deployment descriptor. Here 
is my web.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 
2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd";>
<web-app id="WebApp">
        <display-name>ebpps</display-name>
        <servlet>
                <servlet-name>Main</servlet-name>
                <display-name>Main</display-name>
                <servlet-class>com.mccinc.ads.taskdriver.Main</
servlet-class>
                <init-param>
                        <param-name>INIPATH</param-name>
                        <param-value>/myApp/ini/ebpps.ini</param-value>
                </init-param>
        </servlet>
                <servlet-mapping>
                <servlet-name>Main</servlet-name>
                <url-pattern>/Main</url-pattern>
        </servlet-mapping>
        <welcome-file-list>
                <welcome-file>index.html</welcome-file>
                <welcome-file>index.htm</welcome-file>
                <welcome-file>index.jsp</welcome-file>
                <welcome-file>default.html</welcome-file>
                <welcome-file>default.htm</welcome-file>
                <welcome-file>default.jsp</welcome-file>
        </welcome-file-list>
</web-app>

Does this look OK? Now how would you launch it from the deployment 
descriptor? I tried right clicking on web.xml and that did not work.

Thanks, Joe!



NOTICE: This message contains information which may be confidential. If 
the reader is neither the intended recipient nor a person responsible for 
delivering the message to the intended recipient, you are notified that 
any distribution, copying or retention of this communication is strictly 
prohibited. If you have received this communication in error, please 
notify us immediately by return e-mail, telephone or facsimile. Thank you.



"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
09/21/2006 10:48 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"'Websphere Development Studio Client for iSeries'" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] Debugging web applications in IBM Rational 
SoftwareDevelopment 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.

Joe



From: 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 a 
recent
backup.

After creating multiple workspaces and trying several different ways, I 
am
unable to debug my web application in Rational at all. After creating a
new workspace and importing my existing projects, when I select my 
servlet
and 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 am 
presented
with the "Create, manage, and run configurations" dialog box. I select 
WAS
6.0 under configurations and it looks like a new config is being set up. 
I
am told however that : " The Enterprise Application must contain at 
least
one Application Client." However the only option I am given under the
Application Client module is the "Default" option, which is apparently 
not
the 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 
am
not getting the results advertised.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.