Mark,
Please try the 7.0.5-SNAPSHOT.
On 25/09/17 01:59, Mark Struberg wrote:
Additional info.
Happens if I use openejb-core to run tests on modules which have a jax-ws
client generated via CXF.
LieGrue,
strub
Am 25.09.2017 um 09:32 schrieb Mark Struberg <[email protected]>:
Oki, I did some extensive testing with a few customer project over the weekend.
2 of them now blow up with an Exception (used to work fine with 7.0.3).
<full-stacktrace>
<![CDATA[com.sun.xml.internal.ws.spi.db.DatabindingException:
Unknown JAXBContext implementation: class
com.sun.xml.bind.v2.runtime.JAXBContextImpl
at
com.sun.xml.internal.ws.spi.db.BindingContextFactory.getJAXBFactory(BindingContextFactory.java:192)
at
com.sun.xml.internal.ws.spi.db.BindingContextFactory.create(BindingContextFactory.java:134)
at
com.sun.xml.internal.ws.message.jaxb.JAXBMessage.create(JAXBMessage.java:152)
at
com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createSOAPFaultMessage(SOAPFaultBuilder.java:247)
at
com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createSOAPFaultMessage(SOAPFaultBuilder.java:230)
at
com.sun.xml.internal.ws.wsdl.OperationDispatcher.getWSDLOperationMapping(OperationDispatcher.java:91)
at
com.sun.xml.internal.ws.api.message.Packet.getWSDLOperationMapping(Packet.java:285)
at
com.sun.xml.internal.ws.api.message.Message.getOperation(Message.java:284)
at
com.sun.xml.internal.ws.api.message.Message.getOperation(Message.java:302)
at
com.sun.xml.internal.ws.api.message.Message.isOneWay(Message.java:379)
at
com.sun.xml.internal.ws.api.message.MessageWrapper.isOneWay(MessageWrapper...java:113)
at
com.sun.xml.internal.ws.handler.HandlerTube.checkOneWay(HandlerTube.java:292)
at
com.sun.xml.internal.ws.handler.HandlerTube.processRequest(HandlerTube.java:108)
at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:1121)
at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:1035)
at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:1004)
at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:862)
at com.sun.xml.internal.ws.client.Stub.process(Stub.java:448)
at
com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:178)
at
com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:93)
at
com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:77)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:147)
at com.sun.proxy.$Proxy275.holeAlleEinrichtungen(Unknown Source)
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
at.sozvers.pva.infra.log.proxy.SoapLoggingInvocationHandler.invoke(SoapLoggingInvocationHandler.java:100)
at com.sun.proxy.$Proxy275.holeAlleEinrichtungen(Unknown Source)
I've looked into the dependency:tree and here is the difference.
In openejb-7.0.3 there was no jaxb impl as transitive dependency:
3221 [main] [INFO] | | +- org.apache.tomee:openejb-jee:jar:7.0.3:test
3221 [main] [INFO] | | +-
org.apache.tomee:openejb-jee-accessors:jar:7.0.3:test
3221 [main] [INFO] | | | \- org.metatype.sxc:sxc-jaxb-core:jar:0.8:test
3221 [main] [INFO] | | | \- org.metatype.sxc:sxc-runtime:jar:0.8:test
3221 [main] [INFO] | | +- commons-cli:commons-cli:jar:1.2:test
But in openejb-7.0.4 I get an old jaxb version as transitive dependency. And
this one seems to be incompatible with Java8:
3299 [main] [INFO] | | +- org.apache.tomee:openejb-jee:jar:7.0.4:test
3299 [main] [INFO] | | | +-
javax.xml.bind:jaxb-api:jar:2.3.0-b170201.1204:test
3299 [main] [INFO] | | | +-
com.sun.xml.bind:jaxb-impl:jar:2.3.0-b170127.1453:test
3299 [main] [INFO] | | | \-
com.sun.xml.bind:jaxb-core:jar:2.3.0-b170127.1453:test
3299 [main] [INFO] | | +-
org.apache.tomee:openejb-jee-accessors:jar:7.0.4:test
3299 [main] [INFO] | | | \- org.metatype.sxc:sxc-jaxb-core:jar:0.8:test
3299 [main] [INFO] | | | \- org.metatype.sxc:sxc-runtime:jar:0.8:test
This happens if I use a JAX-WS client in my project.
Can anyone plz review my findings before we go on?
txs and LieGrue,
strub
Am 24.09.2017 um 02:34 schrieb David Blevins <[email protected]>:
+1
Thanks, Andy for the effort on this one!
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
On Sep 21, 2017, at 7:06 PM, Andy Gumbrecht <[email protected]> wrote:
Hi Everyone,
I'd kindly like to ask you all to take a look at this build and place your
votes for a 7.0.4 release.
Staging repo:
https://repository.apache.org/content/repositories/orgapachetomee-1106/
Source zip:
https://repository.apache.org/content/repositories/orgapachetomee-1106/org/apache/tomee/tomee-project/7.0.4/tomee-project-7.0.4-source-release.zip
Dist area:
https://dist.apache.org/repos/dist/dev/tomee/tomee-7.0.4/
Legal report:
https://dist.apache.org/repos/dist/dev/tomee/tomee-7.0.4/legal.zip
Keys:
https://dist.apache.org/repos/dist/release/tomee/KEYS
Changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320&version=12339959
Green buildbot:
https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/725
https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/839
The RAT report indicates 0 Unknown Licenses.
Please vote:
+1: Release
-1 Do not release because ...
The vote will be open for 3 days or the consensus is binding (At least 3
binding votes).
Everyone, committer or not, is encouraged to vote. Thank you very much for your
time, and have a nice weekend.
Andy Gumbrecht.
.
.
