Well, apparently the application's own jar file wasn't in the classpath for the run/debug profile. Once I manually added the jar to the classpath in the classpath tab, everything seems to work ok. I created a new run profile and verified that it wasn't adding it by default.
Is this expected or do you always need to manually add the app's own jar file to the classpath in the run/debug profile? I noticed that the application's project folder was automatically there. I would think it might add the jar file as well for you (and I guess I have always assumed that). I guess I was going on the assumption that since it found my application class, the jar was automatically on the classpath.
Sorry to take up time on a classpath issue if that isn't the case :-/
-Michael
JR Ruggentaler <j..pv.com> wrote:
> Try from eclipse Window->Show view->Debug
> Launch your app.
> Look at the debug window, right click the launch command (.../javaw.exe) select properties. This will show a dialog with the launch command and options. This should allow you to determine what's wrong perhaps you are missing a jar or something. You can copy the launch command and execute it on the command line and tweak it until it works then modify you run profile to use the same options.
>
> J.R.
>
> -----Original Message-----
> From: walker..bermind.com [mailto:walkerm@ubermind.com]
> Sent: Thursday, March 13, 2003 3:25 PM
> To: Ulrich Köster
> Cc: woproject-de..bjectstyle.org
> Subject: Re: 2 Questions (Debugging and Clean installs of jars)
>
>
> Thanks for the response Ulrich,
>
>
> I tried deleting all the WOLips launch profiles, restarted eclipse and then made a new one to no avail. It still seems to not find my local subclass of Session and seems to be searching the classpath for a "Session" class.
>
>
> java.lang.IllegalArgumentException:
>
> <com.our.package.Application> Class 'Session' exists (class
>
> javax.mail.Session) but is not a subclass of WOSession.
>
> at com.webobjects.appserver.WOApplication._sessionClass(WOApplication.java:1504)
>
> at com.webobjects.appserver.WOApplication.createSessionForRequest(WOApplication.java:1545)
>
> at com.webobjects.appserver.WOApplication._initializeSessionInContext(WOApplication.java:1687)
>
> at com.webobjects.appserver._private.WOComponentRequestHandler._dispatchWithPreparedApplication(WOComponentRequstHandler.java:309)
>
> at com.webobjects.appserver._private.WOComponentRequestHandler._handleRequest(WOComponentRequestHandler.java:358)
>
> at com.webobjects.appserver._private.WOComponentRequestHandler.handleRequest(WOComponentRequestHandler.java:432)
>
> at com.webobjects.appserver.WOApplication.dispatchRequest(WOApplication.java:1244)
>
> at com.webobjects.appserver._private.WOWorkerThread.runOnce(WOWorkerThread.java:167)
>
> at com.webobjects.appserver._private.WOWorkerThread.run(WOWorkerThread.java:248)
>
> at java.lang.Thread.run(Unknown Source)
>
>
>
> the javax.mail.Session class is from a jar that is included in one of the linked frameworks. If I take that jar out of the classpath I then just get the class cast exception I referred to in the original post since I am trying to cast a WOSession to my subclass then.
>
>
> There doesn't seem to be anything useful in the eclipse .log file either.
>
>
> Any further suggestions?
>
>
> -Michael
>
>
>
> =?ISO-8859-1?Q?Ulrich_K=F6ster?= <ulric..bjectstyle.org> wrote:
>
> > Hi Michael,
>
> >
>
> > 1.)
>
> > I`ll give it a try.
>
> >
>
> > 2.) I remember this problem. I thought it was fixed. Could you delete
>
> > your launch configuration and create a new WOApplication
>
> > LaunchConfiguration, just to make sure that this does not come from an
>
> > old launch config. If this fails, could you send me the log.
>
> >
>
> > Best regards
>
> >
>
> > Ulrich
>
> > Am Donnerstag, 13.03.03 um 20:11 Uhr schrieb walker..bermind.com:
>
> >
>
> > >
>
> > > Hello all,
>
> > >
>
> > > We are upgrading a WO 4.0 project to 5.2 and have been using
>
> > > Eclipse/WOLips. We've worked through alot of the transitions and
>
> > > learning curve of it and things are starting to smooth out. However I
>
> > > had a couple questions that maybe someone here could answer.
>
> > >
>
> > > 1.)We are building several frameworks into the normal install root for
>
> > > windows (<drive>:\Apple\Local\Libarary\Frameworks).
>
> > > However when we want to clean install these, Eclipse seems to have a
>
> > > lock on them and the ant script fails since it can't delete the
>
> > > previous install. We do have several applications in the workspace
>
> > > that include these frameworks and it seems that Eclipse keeps the lock
>
> > > for those. The only way to clean install the frameworks is to quit
>
> > > Eclipse, manually delete the frameworks, restart Eclipse and then
>
> > > build/install the new frameworks. While this works, it is pretty
>
> > > annoying since we are still making lots of tweaks to the frameworks
>
> > > and need to install fairly often. Is this a common problem people
>
> > > have, and if so is there an easy solution for it?
>
> > >
>
> > > 2.) I'm running into an issue where I can run the app from PB, run the
>
> > > app by just executing the lauch script outside of Eclipse, but when I
>
> > > try to run the app through the wolips launcher or debugger the app
>
> > > isn't using our custom Session class and is causing class cast
>
> > > exceptions where we are expecting our custom subclass but only getting
>
> > > a WOSession back. Since it works through PB and works through just
>
> > > using the launch script it would seem that the WOLips launch might be
>
> > > doing something to alter this. Any thoughts on what might be causing
>
> > > this?
>
> > >
>
> > > Using Eclipse 2.1 M5, WOLips 0.9.9, Win2k, WOF 5.2
>
> > >
>
> > > Thanks for any help,
>
> > > Michael
>
> >
>
This archive was generated by hypermail 2.0.0 : Thu Mar 13 2003 - 17:27:09 EST