Sorry, I should clarify - there doesn't appear to be a way to know what classpath is being used, modify it, etc. It's a black box we have little control over.
- Tim -----Original Message----- From: Bessie, Timothy [mailto:tim.bes...@mckesson.com] Sent: Monday, January 15, 2018 14:32 To: Velocity Developers List <dev@velocity.apache.org> Subject: RE: Problem in Eclipse with JBoss's java2ws using velocity - "The specified logger class org.apache.velocity.runtime.log.NullLogSystem does not implement the org.apache.velocity.runtime.log.LogChute interface" >> Claude Brisson: Most probably, you have several instances of Velocity in >> your classpath, an 1.7 and an older one somewhere else. > That's what I suspected at first as well; I testing by removing all but a > single instance of Velocity 1.7 (I renamed all other instances - I'm not sure > if I have direct control over the classpath that this plugin uses, or if I do > I'm not sure how to modify it, as I don't think it uses the project classpath > directly). Got the same stacktrace, unfortunately. I think it's worth spending some time finding out which classpath is JBoss using. Since I'm not using it personally I can't help you on this, sometimes it's just as simple as printing the CLASSPATH environment variable. I'm not sure if that's possible - this is the classpath being used by the WebService wizard plugin; I see no way to modify its default behavior. We're going to lodge a support ticket with Red Hat to see if they can advise. - Tim
