You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Bessie, Timothy" <Ti...@McKesson.com> on 2018/01/12 02:05:32 UTC
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"
Hi all...
I'm attempting to use Eclipse/JBoss to generate web service artefacts from an implementation class. Everything appears to proceed smoothly, but then we get the below stacktrace. Researching this, it appears to be related to Velocity 1.7 and its use of classloaders and default class implementations. Does anyone know a smart way around this? Given that this is part of the JBoss plugins for Eclipse, I don't have a lot of control over how it works, so the couple of clever ways around this I've found online aren't available to me (it's not a problem with code I'm writing, but with the Eclipse plugin's use of Apache CXF, and IT'S use of Velocity.
Any suggestions would be grand. :-)
Failed to Generate Web Service code, please check the log for more details
org.eclipse.core.runtime.CoreException: Could not find log4j.properties or log4j.xml configuration, logging to console.
java2ws -s C:\Production\iknowmed\g2\src -classdir C:\Production\iknowmed\g2\war\WEB-INF\classes -d C:\Production\iknowmed\g2\wsdl -verbose -cp /C:/Users/eufjdzb/AppData/Local/Temp/temp7537020417576759813.jar; -wrapperbean -createxsdimports com.mscs.emr.web.webservices.elasticsearch.ElasticSearchMediatorImpl
java2ws - Apache CXF 3.1.10.redhat-1
JBWS024002: Failed to invoke org.apache.cxf.tools.java2ws.JavaToWS
org.apache.cxf.tools.common.ToolException: Failed to initialize velocity engine
at org.apache.cxf.tools.common.VelocityGenerator.initVelocity(VelocityGenerator.java:83)
at org.apache.cxf.tools.common.VelocityGenerator.<init>(VelocityGenerator.java:53)
at org.apache.cxf.tools.java2wsdl.generator.wsdl11.BeanGenerator.generateAndCompile(BeanGenerator.java:65)
at org.apache.cxf.tools.java2wsdl.generator.wsdl11.BeanGenerator.generate(BeanGenerator.java:58)
at org.apache.cxf.tools.java2wsdl.generator.wsdl11.BeanGenerator.generate(BeanGenerator.java:35)
at org.apache.cxf.tools.java2wsdl.processor.JavaToWSDLProcessor.generate(JavaToWSDLProcessor.java:156)
at org.apache.cxf.tools.java2wsdl.processor.JavaToWSDLProcessor.process(JavaToWSDLProcessor.java:118)
at org.apache.cxf.tools.java2ws.JavaToWSContainer.processWSDL(JavaToWSContainer.java:110)
at org.apache.cxf.tools.java2ws.JavaToWSContainer.execute(JavaToWSContainer.java:75)
at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:103)
at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:45)
at org.apache.cxf.tools.java2ws.JavaToWS.run(JavaToWS.java:82)
at org.jboss.wsf.stack.cxf.tools.CXFProviderImpl.provide(CXFProviderImpl.java:200)
at org.jboss.wsf.stack.cxf.tools.CXFProviderImpl.provide(CXFProviderImpl.java:109)
at org.jboss.ws.tools.cmd.WSProvide.generate(WSProvide.java:217)
at org.jboss.ws.tools.cmd.WSProvide.main(WSProvide.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.modules.Module.run(Module.java:335)
at org.jboss.modules.Main.main(Main.java:505)
Caused by: org.apache.velocity.exception.VelocityException: Error initializing log: Failed to initialize an instance of org.apache.velocity.runtime.log.NullLogSystem with the current runtime configuration.
at org.apache.velocity.runtime.RuntimeInstance.initializeLog(RuntimeInstance.java:875)
at org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:262)
at org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:646)
at org.apache.velocity.runtime.RuntimeSingleton.init(RuntimeSingleton.java:226)
at org.apache.velocity.app.Velocity.init(Velocity.java:97)
at org.apache.cxf.tools.common.VelocityGenerator.initVelocity(VelocityGenerator.java:79)
... 21 more
Caused by: org.apache.velocity.exception.VelocityException: Failed to initialize an instance of org.apache.velocity.runtime.log.NullLogSystem with the current runtime configuration.
at org.apache.velocity.runtime.log.LogManager.createLogChute(LogManager.java:220)
at org.apache.velocity.runtime.log.LogManager.updateLog(LogManager.java:269)
at org.apache.velocity.runtime.RuntimeInstance.initializeLog(RuntimeInstance.java:871)
... 26 more
Caused by: org.apache.velocity.exception.VelocityException: The specified logger class org.apache.velocity.runtime.log.NullLogSystem does not implement the org.apache.velocity.runtime.log.LogChute interface.
at org.apache.velocity.runtime.log.LogManager.createLogChute(LogManager.java:181)
... 28 more
at org.jboss.tools.ws.creation.core.commands.AbstractGenerateCodeCommand.execute(AbstractGenerateCodeCommand.java:125)
at org.jboss.tools.ws.creation.core.commands.Java2WSCommand.execute(Java2WSCommand.java:1)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:212)
at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:437)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:353)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:993)
at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264)
at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91)
at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154)
at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:869)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:419)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4418)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4236)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3824)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
at org.eclipse.jface.window.Window.open(Window.java:794)
at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
at sun.reflect.GeneratedMethodAccessor51.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:353)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:155)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4418)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4236)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3824)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
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"
Posted by "Bessie, Timothy" <Ti...@McKesson.com>.
Thanks much for your suggestion!
The issue is, we have absolutely no code involved in this, nor can we run any. We are running an Eclipse plugin's "Wizard" to generate the web services. It examines our code to do its work, but the actual code being run is not ours, it is in the plugin.
So any suggestions to run something in code is impossible to do in this case.
Unless you know a way to force a third-party plugin to run arbitrary code if there's no entry point for it to do so?
- Tim
________________________________
From: Mike Kienenberger <mk...@gmail.com>
Sent: Tuesday, January 16, 2018 6:38 AM
To: Velocity Developers List
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"
While I can't share the code, one of my clients has written a generic
class that dumps the current app's classpath, so this can be done
within your own java code.
The code I have access to is much more complicated, but a simple
approach can be found here:
http://cp.mcafee.com/d/2DRPoA73gA76QnQn4kmnT63pJ55d5VBdZZ4SyyCyYOCUOyrdCPqJyLQFm7bCStIg5km7J5tIXtQwUMaLeeA1lxNZ4l8njKaFK6zBZMQszJhLt4SrdCPo09kGmH0zO-2eCtMDkMnDkKJ6k9BWJPbP9-nIT6fMCnmzkh-QOZzZFhrpAYdzsyLCy02Fv3U4fyh-9Ewd7yFmnM-1054hfBPhYrd79EVjudwLQzh05ER87-Gq89gd40Ro-iRfd41ykOpEw0wpHixEDEq817jeFCa6y1KAE4jh0pY-JFjb6y0Kq83h42ivCy2yTSAXbQ3h0vkyh-9EwIvJa6y003SHroD_6vfHqkOThrxeiLYvkzMcrff2Ji8MmFfRjh0xnW6y25pCy2iGN_G_2pEwCjYQg00uRrr4_UPVZriCmWbs9Ol_zWAu2Ji8AjrDVEwB2vNtSTCy8SDsQsCQPrNKVJUSyrh
The approached used by my client checked the "java.class.path" system
property, pulled out the classes in the JRE's lib/rt.jar file for
bootstrap classes, as well as the JRE's lib/ext classes.
It then pulled out the actual classes used with specific code based on
whether the classpath resource was a directory, zip, or a jar file.
On Mon, Jan 15, 2018 at 6:13 PM, Bessie, Timothy
<Ti...@mckesson.com> wrote:
> 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.Bessie@McKesson.com]
> Sent: Monday, January 15, 2018 14:32
> To: Velocity Developers List <de...@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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
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"
Posted by Mike Kienenberger <mk...@gmail.com>.
While I can't share the code, one of my clients has written a generic
class that dumps the current app's classpath, so this can be done
within your own java code.
The code I have access to is much more complicated, but a simple
approach can be found here:
http://www.mkyong.com/java/how-to-print-out-the-current-project-classpath/
The approached used by my client checked the "java.class.path" system
property, pulled out the classes in the JRE's lib/rt.jar file for
bootstrap classes, as well as the JRE's lib/ext classes.
It then pulled out the actual classes used with specific code based on
whether the classpath resource was a directory, zip, or a jar file.
On Mon, Jan 15, 2018 at 6:13 PM, Bessie, Timothy
<Ti...@mckesson.com> wrote:
> 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.Bessie@McKesson.com]
> Sent: Monday, January 15, 2018 14:32
> To: Velocity Developers List <de...@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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
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"
Posted by "Bessie, Timothy" <Ti...@McKesson.com>.
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.Bessie@McKesson.com]
Sent: Monday, January 15, 2018 14:32
To: Velocity Developers List <de...@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
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"
Posted by "Bessie, Timothy" <Ti...@McKesson.com>.
>> 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
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"
Posted by Claude Brisson <cl...@renegat.net.INVALID>.
On 12/01/2018 20:26, Bessie, Timothy wrote:
> Hi all, thanks for the response!
>
> My replies:
>
>> 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.
>> Alessio Soldano: It would be great to know which version of JBossWS (which is where the org.jboss.ws*.* classes come) and/or Apache CXF is being used here. Which version of Eclipse and JBoss plugins ? With that, I can try having the problem reproduced and investigated here.
> We're using "Red Hat JBoss Developer Developer Studio" (a branded version of Eclipse) with this version info:
>
> Version: 10.4.0.GA
> Build id: GA-v20170511-1748-B62
> Build date: 20170511-1748
>
> This corresponds to Eclipse Neon.
>
> JBoss version from server startup message: JBoss EAP 7.0.7.GA (WildFly Core 2.1.17.Final-redhat-1)
> Java version 1.8
>
> The stacktrace appears to indicate that Apache CXF (version 3.1.10 or 3.1.14) is used at least for part of the generation, but that the end-product will use JBossWS annotations, etc. I tried to mimic the call in the stacktrace using Ant, but it generates files that, on startup, JBoss recognizes as Apache CXF only and won't allow them (it displays a warning message). So whatever the plugin is doing appears not to be JUST what the stacktrace indicates (I get the sense that that is just the first step, and it might munge the generated files to conform to JBossWS standards).
>
> I hope to contact Red Hat for support on this as well.
>
> - Tim
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
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"
Posted by "Bessie, Timothy" <Ti...@McKesson.com>.
Also, in searching for the cause of this issue, I found this:
https://plus.google.com/116012605255269201011/posts/6tviyMPbqTU
... which seems like the issue I'm having, though since this isn't happening during my own direct use of the code, I don't have control over.
- Tim
-----Original Message-----
From: Bessie, Timothy [mailto:Tim.Bessie@McKesson.com]
Sent: Friday, January 12, 2018 11:26
To: Velocity Developers List <de...@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"
Hi all, thanks for the response!
My replies:
> 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.
> Alessio Soldano: It would be great to know which version of JBossWS (which is where the org.jboss.ws*.* classes come) and/or Apache CXF is being used here. Which version of Eclipse and JBoss plugins ? With that, I can try having the problem reproduced and investigated here.
We're using "Red Hat JBoss Developer Developer Studio" (a branded version of Eclipse) with this version info:
Version: 10.4.0.GA
Build id: GA-v20170511-1748-B62
Build date: 20170511-1748
This corresponds to Eclipse Neon.
JBoss version from server startup message: JBoss EAP 7.0.7.GA (WildFly Core 2.1.17.Final-redhat-1) Java version 1.8
The stacktrace appears to indicate that Apache CXF (version 3.1.10 or 3.1.14) is used at least for part of the generation, but that the end-product will use JBossWS annotations, etc. I tried to mimic the call in the stacktrace using Ant, but it generates files that, on startup, JBoss recognizes as Apache CXF only and won't allow them (it displays a warning message). So whatever the plugin is doing appears not to be JUST what the stacktrace indicates (I get the sense that that is just the first step, and it might munge the generated files to conform to JBossWS standards).
I hope to contact Red Hat for support on this as well.
- Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
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"
Posted by "Bessie, Timothy" <Ti...@McKesson.com>.
Hi all, thanks for the response!
My replies:
> 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.
> Alessio Soldano: It would be great to know which version of JBossWS (which is where the org.jboss.ws*.* classes come) and/or Apache CXF is being used here. Which version of Eclipse and JBoss plugins ? With that, I can try having the problem reproduced and investigated here.
We're using "Red Hat JBoss Developer Developer Studio" (a branded version of Eclipse) with this version info:
Version: 10.4.0.GA
Build id: GA-v20170511-1748-B62
Build date: 20170511-1748
This corresponds to Eclipse Neon.
JBoss version from server startup message: JBoss EAP 7.0.7.GA (WildFly Core 2.1.17.Final-redhat-1)
Java version 1.8
The stacktrace appears to indicate that Apache CXF (version 3.1.10 or 3.1.14) is used at least for part of the generation, but that the end-product will use JBossWS annotations, etc. I tried to mimic the call in the stacktrace using Ant, but it generates files that, on startup, JBoss recognizes as Apache CXF only and won't allow them (it displays a warning message). So whatever the plugin is doing appears not to be JUST what the stacktrace indicates (I get the sense that that is just the first step, and it might munge the generated files to conform to JBossWS standards).
I hope to contact Red Hat for support on this as well.
- Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
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"
Posted by Claude Brisson <cl...@renegat.net.INVALID>.
Most probably, you have several instances of Velocity in your classpath,
an 1.7 and an older one somewhere else.
Claude
On 12/01/2018 14:14, Alessio Soldano wrote:
> It would be great to know which version of JBossWS (which is where the
> org.jboss.ws*.* classes come) and/or Apache CXF is being used here. Which
> version of Eclipse and JBoss plugins ?
> With that, I can try having the problem reproduced and investigated here.
>
> Cheers
> Alessio
>
> On Fri, Jan 12, 2018 at 3:05 AM, Bessie, Timothy <Ti...@mckesson.com>
> wrote:
>
>> Hi all...
>>
>> I'm attempting to use Eclipse/JBoss to generate web service artefacts from
>> an implementation class. Everything appears to proceed smoothly, but then
>> we get the below stacktrace. Researching this, it appears to be related to
>> Velocity 1.7 and its use of classloaders and default class
>> implementations. Does anyone know a smart way around this? Given that
>> this is part of the JBoss plugins for Eclipse, I don't have a lot of
>> control over how it works, so the couple of clever ways around this I've
>> found online aren't available to me (it's not a problem with code I'm
>> writing, but with the Eclipse plugin's use of Apache CXF, and IT'S use of
>> Velocity.
>>
>> Any suggestions would be grand. :-)
>>
>> Failed to Generate Web Service code, please check the log for more details
>> org.eclipse.core.runtime.CoreException: Could not find
>> log4j.properties or log4j.xml configuration, logging to console.
>>
>> java2ws -s C:\Production\iknowmed\g2\src -classdir
>> C:\Production\iknowmed\g2\war\WEB-INF\classes -d
>> C:\Production\iknowmed\g2\wsdl -verbose -cp /C:/Users/eufjdzb/AppData/
>> Local/Temp/temp7537020417576759813.jar; -wrapperbean -createxsdimports
>> com.mscs.emr.web.webservices.elasticsearch.ElasticSearchMediatorImpl
>> java2ws - Apache CXF 3.1.10.redhat-1
>>
>> JBWS024002: Failed to invoke org.apache.cxf.tools.java2ws.JavaToWS
>> org.apache.cxf.tools.common.ToolException: Failed to initialize
>> velocity engine
>> at org.apache.cxf.tools.common.VelocityGenerator.initVelocity(
>> VelocityGenerator.java:83)
>> at org.apache.cxf.tools.common.VelocityGenerator.<init>(
>> VelocityGenerator.java:53)
>> at org.apache.cxf.tools.java2wsdl.generator.wsdl11.BeanGenerator.
>> generateAndCompile(BeanGenerator.java:65)
>> at org.apache.cxf.tools.java2wsdl.generator.wsdl11.
>> BeanGenerator.generate(BeanGenerator.java:58)
>> at org.apache.cxf.tools.java2wsdl.generator.wsdl11.
>> BeanGenerator.generate(BeanGenerator.java:35)
>> at org.apache.cxf.tools.java2wsdl.processor.
>> JavaToWSDLProcessor.generate(JavaToWSDLProcessor.java:156)
>> at org.apache.cxf.tools.java2wsdl.processor.
>> JavaToWSDLProcessor.process(JavaToWSDLProcessor.java:118)
>> at org.apache.cxf.tools.java2ws.JavaToWSContainer.processWSDL(
>> JavaToWSContainer.java:110)
>> at org.apache.cxf.tools.java2ws.JavaToWSContainer.execute(
>> JavaToWSContainer.java:75)
>> at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(
>> ToolRunner.java:103)
>> at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(
>> ToolRunner.java:45)
>> at org.apache.cxf.tools.java2ws.JavaToWS.run(JavaToWS.java:82)
>> at org.jboss.wsf.stack.cxf.tools.CXFProviderImpl.provide(
>> CXFProviderImpl.java:200)
>> at org.jboss.wsf.stack.cxf.tools.CXFProviderImpl.provide(
>> CXFProviderImpl.java:109)
>> at org.jboss.ws.tools.cmd.WSProvide.generate(WSProvide.java:217)
>> at org.jboss.ws.tools.cmd.WSProvide.main(WSProvide.java:87)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(
>> NativeMethodAccessorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>> DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at org.jboss.modules.Module.run(Module.java:335)
>> at org.jboss.modules.Main.main(Main.java:505)
>> Caused by: org.apache.velocity.exception.VelocityException: Error
>> initializing log: Failed to initialize an instance of
>> org.apache.velocity.runtime.log.NullLogSystem with the current runtime
>> configuration.
>> at org.apache.velocity.runtime.RuntimeInstance.initializeLog(
>> RuntimeInstance.java:875)
>> at org.apache.velocity.runtime.RuntimeInstance.init(
>> RuntimeInstance.java:262)
>> at org.apache.velocity.runtime.RuntimeInstance.init(
>> RuntimeInstance.java:646)
>> at org.apache.velocity.runtime.RuntimeSingleton.init(
>> RuntimeSingleton.java:226)
>> at org.apache.velocity.app.Velocity.init(Velocity.java:97)
>> at org.apache.cxf.tools.common.VelocityGenerator.initVelocity(
>> VelocityGenerator.java:79)
>> ... 21 more
>> Caused by: org.apache.velocity.exception.VelocityException: Failed to
>> initialize an instance of org.apache.velocity.runtime.log.NullLogSystem
>> with the current runtime configuration.
>> at org.apache.velocity.runtime.log.LogManager.createLogChute(
>> LogManager.java:220)
>> at org.apache.velocity.runtime.log.LogManager.updateLog(
>> LogManager.java:269)
>> at org.apache.velocity.runtime.RuntimeInstance.initializeLog(
>> RuntimeInstance.java:871)
>> ... 26 more
>> Caused by: org.apache.velocity.exception.VelocityException: The
>> specified logger class org.apache.velocity.runtime.log.NullLogSystem does
>> not implement the org.apache.velocity.runtime.log.LogChute interface.
>> at org.apache.velocity.runtime.log.LogManager.createLogChute(
>> LogManager.java:181)
>> ... 28 more
>>
>> at org.jboss.tools.ws.creation.core.commands.
>> AbstractGenerateCodeCommand.execute(AbstractGenerateCodeCommand.java:125)
>> at org.jboss.tools.ws.creation.core.commands.Java2WSCommand.
>> execute(Java2WSCommand.java:1)
>> at org.eclipse.wst.command.internal.env.core.fragment.
>> CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
>> at org.eclipse.wst.command.internal.env.core.fragment.
>> CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
>> at org.eclipse.wst.command.internal.env.core.fragment.
>> CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:
>> 212)
>> at org.eclipse.wst.command.internal.env.ui.widgets.
>> SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
>> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(
>> ModalContext.java:437)
>> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:353)
>> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:993)
>> at org.eclipse.wst.command.internal.env.ui.widgets.
>> SimpleCommandEngineManager.runForwardToNextStop(
>> SimpleCommandEngineManager.java:264)
>> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.
>> runForwardToNextStop(WizardPageManager.java:91)
>> at org.eclipse.wst.command.internal.env.ui.widgets.
>> WizardPageManager.getNextPage(WizardPageManager.java:154)
>> at org.eclipse.wst.command.internal.env.ui.widgets.
>> SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
>> at org.eclipse.jface.wizard.WizardDialog.nextPressed(
>> WizardDialog.java:869)
>> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(
>> WizardDialog.java:419)
>> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
>> at org.eclipse.swt.widgets.TypedListener.handleEvent(
>> TypedListener.java:249)
>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
>> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4418)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
>> at org.eclipse.swt.widgets.Display.runDeferredEvents(
>> Display.java:4236)
>> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3824)
>> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
>> at org.eclipse.jface.window.Window.open(Window.java:794)
>> at org.eclipse.ui.internal.handlers.WizardHandler$New.
>> executeHandler(WizardHandler.java:269)
>> at org.eclipse.ui.internal.handlers.WizardHandler.
>> execute(WizardHandler.java:290)
>> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(
>> HandlerProxy.java:295)
>> at org.eclipse.ui.internal.handlers.E4HandlerProxy.
>> execute(E4HandlerProxy.java:90)
>> at sun.reflect.GeneratedMethodAccessor51.invoke(Unknown Source)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>> DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(
>> MethodRequestor.java:55)
>> at org.eclipse.e4.core.internal.di.InjectorImpl.
>> invokeUsingClass(InjectorImpl.java:282)
>> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(
>> InjectorImpl.java:264)
>> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(
>> ContextInjectionFactory.java:132)
>> at org.eclipse.e4.core.commands.internal.
>> HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
>> at org.eclipse.core.commands.Command.executeWithChecks(
>> Command.java:494)
>> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(
>> ParameterizedCommand.java:488)
>> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.
>> executeHandler(HandlerServiceImpl.java:210)
>> at org.eclipse.ui.internal.handlers.LegacyHandlerService.
>> executeCommand(LegacyHandlerService.java:353)
>> at org.eclipse.ui.internal.actions.CommandAction.
>> runWithEvent(CommandAction.java:155)
>> at org.eclipse.jface.action.ActionContributionItem.
>> handleWidgetSelection(ActionContributionItem.java:565)
>> at org.eclipse.jface.action.ActionContributionItem.lambda$
>> 4(ActionContributionItem.java:397)
>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
>> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4418)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
>> at org.eclipse.swt.widgets.Display.runDeferredEvents(
>> Display.java:4236)
>> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3824)
>> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(
>> PartRenderingEngine.java:1121)
>> at org.eclipse.core.databinding.observable.Realm.
>> runWithDefault(Realm.java:336)
>> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(
>> PartRenderingEngine.java:1022)
>> at org.eclipse.e4.ui.internal.workbench.E4Workbench.
>> createAndRunUI(E4Workbench.java:150)
>> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
>> at org.eclipse.core.databinding.observable.Realm.
>> runWithDefault(Realm.java:336)
>> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(
>> Workbench.java:610)
>> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(
>> PlatformUI.java:148)
>> at org.eclipse.ui.internal.ide.application.IDEApplication.
>> start(IDEApplication.java:138)
>> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(
>> EclipseAppHandle.java:196)
>> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.
>> runApplication(EclipseAppLauncher.java:134)
>> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(
>> EclipseAppLauncher.java:104)
>> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(
>> EclipseStarter.java:388)
>> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(
>> EclipseStarter.java:243)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(
>> NativeMethodAccessorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>> DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
>> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
>> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
>> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
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"
Posted by Alessio Soldano <as...@redhat.com>.
It would be great to know which version of JBossWS (which is where the
org.jboss.ws*.* classes come) and/or Apache CXF is being used here. Which
version of Eclipse and JBoss plugins ?
With that, I can try having the problem reproduced and investigated here.
Cheers
Alessio
On Fri, Jan 12, 2018 at 3:05 AM, Bessie, Timothy <Ti...@mckesson.com>
wrote:
> Hi all...
>
> I'm attempting to use Eclipse/JBoss to generate web service artefacts from
> an implementation class. Everything appears to proceed smoothly, but then
> we get the below stacktrace. Researching this, it appears to be related to
> Velocity 1.7 and its use of classloaders and default class
> implementations. Does anyone know a smart way around this? Given that
> this is part of the JBoss plugins for Eclipse, I don't have a lot of
> control over how it works, so the couple of clever ways around this I've
> found online aren't available to me (it's not a problem with code I'm
> writing, but with the Eclipse plugin's use of Apache CXF, and IT'S use of
> Velocity.
>
> Any suggestions would be grand. :-)
>
> Failed to Generate Web Service code, please check the log for more details
> org.eclipse.core.runtime.CoreException: Could not find
> log4j.properties or log4j.xml configuration, logging to console.
>
> java2ws -s C:\Production\iknowmed\g2\src -classdir
> C:\Production\iknowmed\g2\war\WEB-INF\classes -d
> C:\Production\iknowmed\g2\wsdl -verbose -cp /C:/Users/eufjdzb/AppData/
> Local/Temp/temp7537020417576759813.jar; -wrapperbean -createxsdimports
> com.mscs.emr.web.webservices.elasticsearch.ElasticSearchMediatorImpl
> java2ws - Apache CXF 3.1.10.redhat-1
>
> JBWS024002: Failed to invoke org.apache.cxf.tools.java2ws.JavaToWS
> org.apache.cxf.tools.common.ToolException: Failed to initialize
> velocity engine
> at org.apache.cxf.tools.common.VelocityGenerator.initVelocity(
> VelocityGenerator.java:83)
> at org.apache.cxf.tools.common.VelocityGenerator.<init>(
> VelocityGenerator.java:53)
> at org.apache.cxf.tools.java2wsdl.generator.wsdl11.BeanGenerator.
> generateAndCompile(BeanGenerator.java:65)
> at org.apache.cxf.tools.java2wsdl.generator.wsdl11.
> BeanGenerator.generate(BeanGenerator.java:58)
> at org.apache.cxf.tools.java2wsdl.generator.wsdl11.
> BeanGenerator.generate(BeanGenerator.java:35)
> at org.apache.cxf.tools.java2wsdl.processor.
> JavaToWSDLProcessor.generate(JavaToWSDLProcessor.java:156)
> at org.apache.cxf.tools.java2wsdl.processor.
> JavaToWSDLProcessor.process(JavaToWSDLProcessor.java:118)
> at org.apache.cxf.tools.java2ws.JavaToWSContainer.processWSDL(
> JavaToWSContainer.java:110)
> at org.apache.cxf.tools.java2ws.JavaToWSContainer.execute(
> JavaToWSContainer.java:75)
> at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(
> ToolRunner.java:103)
> at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(
> ToolRunner.java:45)
> at org.apache.cxf.tools.java2ws.JavaToWS.run(JavaToWS.java:82)
> at org.jboss.wsf.stack.cxf.tools.CXFProviderImpl.provide(
> CXFProviderImpl.java:200)
> at org.jboss.wsf.stack.cxf.tools.CXFProviderImpl.provide(
> CXFProviderImpl.java:109)
> at org.jboss.ws.tools.cmd.WSProvide.generate(WSProvide.java:217)
> at org.jboss.ws.tools.cmd.WSProvide.main(WSProvide.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.modules.Module.run(Module.java:335)
> at org.jboss.modules.Main.main(Main.java:505)
> Caused by: org.apache.velocity.exception.VelocityException: Error
> initializing log: Failed to initialize an instance of
> org.apache.velocity.runtime.log.NullLogSystem with the current runtime
> configuration.
> at org.apache.velocity.runtime.RuntimeInstance.initializeLog(
> RuntimeInstance.java:875)
> at org.apache.velocity.runtime.RuntimeInstance.init(
> RuntimeInstance.java:262)
> at org.apache.velocity.runtime.RuntimeInstance.init(
> RuntimeInstance.java:646)
> at org.apache.velocity.runtime.RuntimeSingleton.init(
> RuntimeSingleton.java:226)
> at org.apache.velocity.app.Velocity.init(Velocity.java:97)
> at org.apache.cxf.tools.common.VelocityGenerator.initVelocity(
> VelocityGenerator.java:79)
> ... 21 more
> Caused by: org.apache.velocity.exception.VelocityException: Failed to
> initialize an instance of org.apache.velocity.runtime.log.NullLogSystem
> with the current runtime configuration.
> at org.apache.velocity.runtime.log.LogManager.createLogChute(
> LogManager.java:220)
> at org.apache.velocity.runtime.log.LogManager.updateLog(
> LogManager.java:269)
> at org.apache.velocity.runtime.RuntimeInstance.initializeLog(
> RuntimeInstance.java:871)
> ... 26 more
> Caused by: org.apache.velocity.exception.VelocityException: The
> specified logger class org.apache.velocity.runtime.log.NullLogSystem does
> not implement the org.apache.velocity.runtime.log.LogChute interface.
> at org.apache.velocity.runtime.log.LogManager.createLogChute(
> LogManager.java:181)
> ... 28 more
>
> at org.jboss.tools.ws.creation.core.commands.
> AbstractGenerateCodeCommand.execute(AbstractGenerateCodeCommand.java:125)
> at org.jboss.tools.ws.creation.core.commands.Java2WSCommand.
> execute(Java2WSCommand.java:1)
> at org.eclipse.wst.command.internal.env.core.fragment.
> CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
> at org.eclipse.wst.command.internal.env.core.fragment.
> CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
> at org.eclipse.wst.command.internal.env.core.fragment.
> CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:
> 212)
> at org.eclipse.wst.command.internal.env.ui.widgets.
> SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(
> ModalContext.java:437)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:353)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:993)
> at org.eclipse.wst.command.internal.env.ui.widgets.
> SimpleCommandEngineManager.runForwardToNextStop(
> SimpleCommandEngineManager.java:264)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.
> runForwardToNextStop(WizardPageManager.java:91)
> at org.eclipse.wst.command.internal.env.ui.widgets.
> WizardPageManager.getNextPage(WizardPageManager.java:154)
> at org.eclipse.wst.command.internal.env.ui.widgets.
> SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(
> WizardDialog.java:869)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(
> WizardDialog.java:419)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(
> TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4418)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(
> Display.java:4236)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3824)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.
> executeHandler(WizardHandler.java:269)
> at org.eclipse.ui.internal.handlers.WizardHandler.
> execute(WizardHandler.java:290)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(
> HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.
> execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor51.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(
> MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.
> invokeUsingClass(InjectorImpl.java:282)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(
> InjectorImpl.java:264)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(
> ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.
> HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(
> Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(
> ParameterizedCommand.java:488)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.
> executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.
> executeCommand(LegacyHandlerService.java:353)
> at org.eclipse.ui.internal.actions.CommandAction.
> runWithEvent(CommandAction.java:155)
> at org.eclipse.jface.action.ActionContributionItem.
> handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$
> 4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4418)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(
> Display.java:4236)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3824)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(
> PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.
> runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(
> PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.
> createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
> at org.eclipse.core.databinding.observable.Realm.
> runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(
> Workbench.java:610)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(
> PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.
> start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(
> EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.
> runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(
> EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(
> EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(
> EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
>
>