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-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
