Someone had this same problem just recently. Check the archives for the topic "Classloading problems." They were using Eclipse WTP also.
-----Original Message----- From: Michael D [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 02, 2006 6:51 PM To: [email protected] Subject: RE: Proxy troubles on service start Thanks James That sounds reasonable actually. At the moment Im running it inside an Eclipse plugin that deploys the app to an internal Jetty instance. Eventually it will be depolyed to a remote Tomcat server. This is on XP Pro SP2. Java 5. I would have thought that only a single classloader was being used but after 6+ hrs yesterday changing interfaces, methods etc I finally got it running by changing the package of the service. I have a Eclipse project with several services that is exported to JAR which is then included in the build path of another Eclipse project - the main project which is run directly from the projects 'out' folder. As long as the service was in the main project it would not run. If it is a classloader issue, is there a workaround to trick the classloader(s)? or should i just consider thats how it is and move on. We can live with it as it is now but ideally, the service should belong in the main project and we have a couple more services to add. What do you reckon? Cheers Michael -- View this message in context: http://www.nabble.com/Proxy-troubles-on-service-start-t1535673.html#a4201217 Sent from the Hivemind - User forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
