× 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.


  1.  Home
  2. WDSCI-L
  3. March 2006

Re: QuantumDB Plugin for WDSCLite

I am running WDSc Lite 6.0.1.1.  I have attempted to get the QuantumDB
perspective to show and am not having any luck.  I've tried starting
with the -clean option, no luck.  I have verified that I do not have a
FAT file system.  I have put the QuantumDB 3.0 plugin folders in the
plugin folder in my WDSc directory as well as my WDSc lite directory, no
luck.

If anyone has successfully installed QuantumDB 3.0 in WDSc Lite 6.0.1.1
I would greatly appreciate some assistance.

Thank you,
Gregory Simmons

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of wdsci-l-request@xxxxxxxxxxxx
Sent: Wednesday, March 01, 2006 10:59 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: WDSCI-L Digest, Vol 4, Issue 125

Send WDSCI-L mailing list submissions to
        wdsci-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.midrange.com/mailman/listinfo/wdsci-l
or, via email, send a message with subject or body 'help' to
        wdsci-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
        wdsci-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of WDSCI-L digest..."


*** NOTE: When replying to this digest message, PLEASE remove all text
unrelated to your reply and change the subject line so it is meaningful.

Today's Topics:

   1. Re:        (Peter.Colpaert@xxxxxxxxx)
   2. Re: QuantumDB Plugin for WDSCLite (Fleming, Greg (ED))
   3. Re: QuantumDB Plugin for WDSCLite (Peter.Colpaert@xxxxxxxxx)
   4. /COPY member view oddity (mlazarus@xxxxxxxx)
   5. DEBUG source missmatch (Christen, Duane J.)
   6. Re: DEBUG source missmatch (Xuan Chen)
   7. Launching a servlet (Joe Pluta)
   8. Re: Launching a servlet (Gibbons, Michael)
   9. Re: Launching a servlet (Rahil Choonawala)


----------------------------------------------------------------------

message: 1
date: Wed, 1 Mar 2006 07:37:43 +0100
from: Peter.Colpaert@xxxxxxxxx
subject: Re: [WDSCI-L] QuantumDB Plugin for WDSCLite

Greg,

Very strange indeed, since I can't get the export working in the full 
version, no matter what I try...  (it's even in the forum over at 
sourceforge that this doesn't seem to work).

Maybe it's time to give it another try...

Thanks,

Peter Colpaert
Application Developer
PLI - IT - Kontich, Belgium
-----
Yoda of Borg are we.  Futile is resistance, assimilated will you be.
-----



"Fleming, Greg (ED)" <GFLEMING@xxxxxxxxxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
28/02/2006 16:35
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] QuantumDB Plugin for WDSCLite






Peter,

Now that you mention it, I was installing the 3.0.1 version of
quantumdb.
Strange, though, 3.0.1 works OK in the full version of WDSC, and even
exports Excel without problems, which you mentioned was buggy for you in
an earlier post.

For the lite version, though, it wasn't allowing me to display the
database bookmarks view, so I loaded the 3.0.0 version and that works in
Lite without trouble. 

Greg




------------------------------

message: 2
date: Wed, 1 Mar 2006 08:43:49 -0500
from: "Fleming, Greg \(ED\)" <GFLEMING@xxxxxxxxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] QuantumDB Plugin for WDSCLite

It seems to me like the issues may be related to the various versions of
all these bits we're trying to fit together.

There's the Quantumdb version, the org.eclipse.gef version, and the
org.eclipse.platform version.  

I saw in the release notes for QuantumDb that the 3.0.1 version requires
the gef plugin, so I downloaded the gef 3.1.1 plugin from eclipse and
installed it, which I think may have been a mistake.  It seems that my
full version of WDSC already had the 3.0.1 version of gef, so it wound
up with both versions of gef, and Lite (which originally didn't have the
gef at all) only wound up with the 3.1.1 version.

When I installed the Quantumdb 3.0.1 plugin on WDSC Lite, it gave me an
error that said the "3.1.1 gef requires org.eclipse.platform 3.1.0.
Results may be unpredictable".  I later looked at my platform version
and discovered that it was at 3.0.1. (After having ignored the message
and installed Quantumdb 3.0.1, with the aforementioned negative
results).

When I went to the eclipse site to look for this org.eclipse.platform
plugin, I found that the download related to it is called the "eclipse
SDK 3.1", which sounds like it might be more than a plugin, as the word
"platform" suggests. 

I guess I may not be clear on the relationships between eclipse and WDSC
and Rational Software Development Platform, but I'm guessing that maybe
WDSC is currently running on the 3.0.x version of eclipse, and I
probably shouldn't update to a newer version of eclipse myself, since
the Rational Product Software Updater doesn't seem to think I need any
more upgrades at the moment.  

I tried purging the 3.1.1 gef from WDSCLite, and installed the 3.0.1,
then reinstalled the Quantumdb 3.0.1, but still got the errors, so I
gave up and installed Quantum 3.0.0, which works fine in Lite.  I still
have Quantum 3.0.1 in the WDSC full version, and as I mentioned, it
hasn't given me any trouble.



|-----Original Message-----
|From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
|Behalf Of Peter.Colpaert@xxxxxxxxx
|Sent: Wednesday, March 01, 2006 1:38 AM
|To: Websphere Development Studio Client for iSeries
|Subject: Re: [WDSCI-L] QuantumDB Plugin for WDSCLite
|
|Greg,
|
|Very strange indeed, since I can't get the export working in the full
|version, no matter what I try...  (it's even in the forum over at
|sourceforge that this doesn't seem to work).
|
|Maybe it's time to give it another try...
|
|Thanks,
|
|Peter Colpaert
|Application Developer
|PLI - IT - Kontich, Belgium
|-----
|Yoda of Borg are we.  Futile is resistance, assimilated will you be.
|-----
|



------------------------------

message: 3
date: Wed, 1 Mar 2006 14:46:47 +0100
from: Peter.Colpaert@xxxxxxxxx
subject: Re: [WDSCI-L] QuantumDB Plugin for WDSCLite

I ended up deleting everyting Quantum, both from the full WDSC and from 
Lite, and installed 3.0.0 in both environments.   Life is good again.

Thanks,

Peter Colpaert
Application Developer
PLI - IT - Kontich, Belgium
-----
Yoda of Borg are we.  Futile is resistance, assimilated will you be.
-----



"Fleming, Greg (ED)" <GFLEMING@xxxxxxxxxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
01/03/2006 14:43
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] QuantumDB Plugin for WDSCLite






It seems to me like the issues may be related to the various versions of
all these bits we're trying to fit together.

There's the Quantumdb version, the org.eclipse.gef version, and the
org.eclipse.platform version. 

I saw in the release notes for QuantumDb that the 3.0.1 version requires
the gef plugin, so I downloaded the gef 3.1.1 plugin from eclipse and
installed it, which I think may have been a mistake.  It seems that my
full version of WDSC already had the 3.0.1 version of gef, so it wound
up with both versions of gef, and Lite (which originally didn't have the
gef at all) only wound up with the 3.1.1 version.

When I installed the Quantumdb 3.0.1 plugin on WDSC Lite, it gave me an
error that said the "3.1.1 gef requires org.eclipse.platform 3.1.0.
Results may be unpredictable".  I later looked at my platform version
and discovered that it was at 3.0.1. (After having ignored the message
and installed Quantumdb 3.0.1, with the aforementioned negative
results).

When I went to the eclipse site to look for this org.eclipse.platform
plugin, I found that the download related to it is called the "eclipse
SDK 3.1", which sounds like it might be more than a plugin, as the word
"platform" suggests. 

I guess I may not be clear on the relationships between eclipse and WDSC
and Rational Software Development Platform, but I'm guessing that maybe
WDSC is currently running on the 3.0.x version of eclipse, and I
probably shouldn't update to a newer version of eclipse myself, since
the Rational Product Software Updater doesn't seem to think I need any
more upgrades at the moment. 

I tried purging the 3.1.1 gef from WDSCLite, and installed the 3.0.1,
then reinstalled the Quantumdb 3.0.1, but still got the errors, so I
gave up and installed Quantum 3.0.0, which works fine in Lite.  I still
have Quantum 3.0.1 in the WDSC full version, and as I mentioned, it
hasn't given me any trouble.


------------------------------

message: 4
date: Wed, 1 Mar 2006 09:30:40 -0500
from: "mlazarus@xxxxxxxx" <mlazarus@xxxxxxxx>
subject: [WDSCI-L] /COPY member view oddity

 I ran across an oddity in the RSE Version: 6.0.1.  When right clicking
on
a /COPY statement in order to browse the source, if the code is in the
form
of:
/COPY FILE,MEMBER the editor assumes that the name to the left of the
comma
is a LIBRARY!  Changing the statement to read /COPY *libl/FILE,MEMBER
works.  This behavior is incorrect.  Is there a fix for this?

 -mark

--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .





------------------------------

message: 5
date: Wed, 1 Mar 2006 09:37:11 -0600 
from: "Christen, Duane J." <dchristen@xxxxxxxxxxxxx>
subject: [WDSCI-L] DEBUG source missmatch

I have a problem with the debugger displaying the incorrect source in
the
debug editor. This usually means I have not updated the PGM or SRVPGM,
which
is expected, so I update the object. Occasionally the object and module
are
in sync when this occurs and if I close WDSC and restart the correct
source
is displayed in the debugger. This is a pain, and I assume that there is
a
cache somewhere that gets cleared when WDSC is closed. If anyone can
tell me
what/where to clear this cache I would appreciate it. But this is not my
major problem, twice now I have had the debug editor "loose" a line of
code,
closing WDSC and even shutting down my PC has not helped. By loose I
mean
that a line of code does not show up in the debug editor, yet the line
number sequence does not skip the missing line. This throws off the rest
of
the source being debugged. When I debug the same PGM on a green screen
(strdbg), the source is correct, so it is not a problem with the object
or,
it seems, a cache. 
Anyone have any ideas?

Duane Christen   



NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named.  Any use,
copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via
e-mail.





------------------------------

message: 6
date: Wed, 1 Mar 2006 10:42:35 -0500
from: Xuan Chen <xuanchen@xxxxxxxxxx>
subject: Re: [WDSCI-L] DEBUG source missmatch

Duane,

Which version of WDSc you are using?  You mentioned debugger editor.  Is
the tab of the editor has a bug icon, instead of a pen icon?

Thanks,

Xuan Chen,  Problem Determination Tools for iSeries
(905) 413-3769 T/L 969-3769
xuanchen@xxxxxxxxxx




 

             "Christen, Duane

             J."

             <dchristen@mcleod
To 
             usa.com>                  "'Websphere Development Studio

             Sent by:                  Client for  iSeries'"

             wdsci-l-bounces@m         <wdsci-l@xxxxxxxxxxxx>

             idrange.com
cc 
 

 
Subject 
             03/01/2006 10:37          [WDSCI-L] DEBUG source missmatch

             AM

 

 

             Please respond to

                 Websphere

                Development

             Studio Client for

                  iSeries

 

 





I have a problem with the debugger displaying the incorrect source in
the
debug editor. This usually means I have not updated the PGM or SRVPGM,
which
is expected, so I update the object. Occasionally the object and module
are
in sync when this occurs and if I close WDSC and restart the correct
source
is displayed in the debugger. This is a pain, and I assume that there is
a
cache somewhere that gets cleared when WDSC is closed. If anyone can
tell
me
what/where to clear this cache I would appreciate it. But this is not my
major problem, twice now I have had the debug editor "loose" a line of
code,
closing WDSC and even shutting down my PC has not helped. By loose I
mean
that a line of code does not show up in the debug editor, yet the line
number sequence does not skip the missing line. This throws off the rest
of
the source being debugged. When I debug the same PGM on a green screen
(strdbg), the source is correct, so it is not a problem with the object
or,
it seems, a cache.
Anyone have any ideas?

Duane Christen



NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named.  Any use,
copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via
e-mail.



--
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.




------------------------------

message: 7
date: Wed, 1 Mar 2006 10:08:02 -0600
from: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
subject: [WDSCI-L] Launching a servlet

A while back I posted an issue I had with launching servlets.  In WDSC
5, I
could right-click on a JSP or a servlet in the Project Explorer and Run
and
Debug options would appear in the menu.  These brought me to a submenu
which
allowed me to Run or Debug on the server.  This basically launched a
browser
and fired off the JSP.

 

Since switching to WDSC 6, I can only launch JSPs with this method.  The
only options available for servlets are "JUnit Test" and "Run.".  Run.
brings up the dialog to set up a launch configuration, but none of the
configurations run on the WTE server.

 

I can get around this by running a JSP to bring up an internal browser
window and then modifying the URL to load the servlet instead, bur I was
hoping there was a better way.

 

Joe



------------------------------

message: 8
date: Wed, 1 Mar 2006 11:28:44 -0500 
from: "Gibbons, Michael" <bmis04@xxxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] Launching a servlet

Joe,

You first have to add the servlets to the web.xml file in the web-inf
folder. Then to run a servlet the expand the Deployment Descriptor and
you
should see servlets, expand that and you will see what you added to the
web.xml. You can now right click the servlet and say run on server. 

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On
Behalf Of Joe Pluta
Sent: Wednesday, March 01, 2006 11:08 AM
To: 'Websphere Development Studio Client for iSeries'
Subject: [WDSCI-L] Launching a servlet

A while back I posted an issue I had with launching servlets.  In WDSC
5, I
could right-click on a JSP or a servlet in the Project Explorer and Run
and
Debug options would appear in the menu.  These brought me to a submenu
which
allowed me to Run or Debug on the server.  This basically launched a
browser
and fired off the JSP.

 

Since switching to WDSC 6, I can only launch JSPs with this method.  The
only options available for servlets are "JUnit Test" and "Run.".  Run.
brings up the dialog to set up a launch configuration, but none of the
configurations run on the WTE server.

 

I can get around this by running a JSP to bring up an internal browser
window and then modifying the URL to load the servlet instead, bur I was
hoping there was a better way.

 

Joe

--
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.


------------------------------

message: 9
date: Wed, 1 Mar 2006 11:58:20 -0500
from: Rahil Choonawala <RahilChoonawala@xxxxxxxx>
subject: Re: [WDSCI-L] Launching a servlet


Joe,

      On WDSC 6.0 in the web perspective under navigator when you right
click on the servlet/jsp there are separate options to "run" and "debug"
with multiple choices under each one. I believe this is what you want to
debug a servlet.



 

             "Joe Pluta"

             <joepluta@plutabr

             others.com>
To 
             Sent by:                  "'Websphere Development Studio

             wdsci-l-bounces@m         Client for iSeries'"

             idrange.com               <wdsci-l@xxxxxxxxxxxx>

 
cc 
 

             03/01/2006 11:08
Subject 
             AM                        [WDSCI-L] Launching a servlet

 

 

             Please respond to

                 Websphere

                Development

             Studio Client for

                  iSeries

             <wdsci-l@midrange

                   .com>

 

 





A while back I posted an issue I had with launching servlets.  In WDSC
5, I
could right-click on a JSP or a servlet in the Project Explorer and Run
and
Debug options would appear in the menu.  These brought me to a submenu
which
allowed me to Run or Debug on the server.  This basically launched a
browser
and fired off the JSP.



Since switching to WDSC 6, I can only launch JSPs with this method.  The
only options available for servlets are "JUnit Test" and "Run.".  Run.
brings up the dialog to set up a launch configuration, but none of the
configurations run on the WTE server.



I can get around this by running a JSP to bring up an internal browser
window and then modifying the URL to load the servlet instead, bur I was
hoping there was a better way.



Joe

--
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 thread ...
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.