When you launch in Eclipse you get the classpath as set in the lancher
configuration. When you launch from the command line (double click or
in deployment) it uses a classpath that WOBootStrap.jar creates. It
sounds like when you added frameworks to the project they did not get
added to the launch config. Open the Run... window and update the
classpath for the launch config.
Chuck
On Mar 4, 2005, at 6:44 AM, Des Oates wrote:
I have a problem running my WebServices server project within Eclipse.
It is reproducible on Mac and Windows. (Machine Specs given below) I
think its a classpath /version conflict problem but need some help
identifying where this conflict can be resolved.
This is only a development problem. I'm using the incremental build
option within WOLips and that itself seems to be fine. It does build a
valid server woa file. which, if I double click, will launch and run
perfectly. Furthermore, if I 'install' the application using the
WOLips context menu option, it also will install and run fine under
"/System/Library/WebObjects/Applications/" (or Windows equivalient)
and can control as you would expect using Monitor.
However, if I try to run it from within Eclipse as a WOApplication I
get an error. I did notice that this error never occurred until I
added the Web Services frameworks to my project. and I don't get the
problem with XCode, but we have several Windows only developers, so
the Eclipse solution is what we need.
The error log is :
...
[2005-03-04 14:28:53 GMT] <main> Creating LifebeatThread now with:
server 50343 deslaptop.local 1085 30000
Welcome to server !
Initializing WebServices... <--- this is mine
[2005-03-04 14:28:55 GMT] <main> A fatal exception occurred:
com.webobjects.webservices.support.WOXMLProvider.getRoles()Ljava/util/
List;
[2005-03-04 14:28:55 GMT] <main> java.lang.AbstractMethodError:
com.webobjects.webservices.support.WOXMLProvider.getRoles()Ljava/util/
List;
at
org.apache.axis.AxisEngine.refreshGlobalOptions(AxisEngine.java:479)
at
com.webobjects.webservices.support.WOXMLProvider.doConfigureEngine(WOXM
LProvider.java:85)
at
com.webobjects.webservices.support.WOXMLProvider.configureEngine(WOXMLP
rovider.java:99)
at org.apache.axis.AxisEngine.init(AxisEngine.java:162)
at org.apache.axis.AxisEngine.<init>(AxisEngine.java:146)
at org.apache.axis.server.AxisServer.<init>(AxisServer.java:87)
at
com.webobjects.appserver._private.WOWebService.initServer(WOWebService.
java:113)
at
com.webobjects.appserver._private.WOWebService.registerService(WOWebSer
vice.java:147)
at
com.webobjects.appserver.WOWebServiceRegistrar.registerWebService(WOWeb
ServiceRegistrar.java:144)
at Application.initWebServices(Application.java:32)
at Application.<init>(Application.java:20)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
This looks to me like a version conflict related to Axis libraries but
if this is the case, then why do I not get this conflict in
deployment?
Anyone got any suggestions?
TIA
Des
System info
Mac
G4 17" PowerBook
OS X v 10.3.7
WO v5.2.2
Eclipse: 3.0.1
WOLips: 1.1.0.90
Win
<Various Hardware Configs>
Win XP SP2
WO v5.2.2
Eclipse: 3.0.1
WOLips: 1.1.0.90
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development problems. http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
