[jira] [Commented] (CXF-9034) IllegalAccessError: class org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine
[
https://issues.apache.org/jira/browse/CXF-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881980#comment-17881980
]
Joakim Erdfelt commented on CXF-9034:
-
The code at
[https://github.com/apache/cxf/blob/cxf-4.0.4/rt/transports/http-jetty/src/main/java/org/apache/cxf/transport/http_jetty/JettyHTTPServerEngine.java#L596]
References a Jetty 11 class
`org.eclipse.jetty.server.handler.ContextHandlerCollection` which does exist in
Jetty 12.x, but is part of Jetty Core, which has all Servlet level dependencies
removed from it.
Keep in mind that Jetty 12 is now a Jetty Core (with no EE dependencies), and
Environments (ee11, ee10, ee9, ee8, etc) which has the EE dependencies, like
Servlet.
Looking at your JettyHTTPServerEngine you have a fair number of changes to
make, both due to the Jetty 12 version changes, and also due to Java changes
itself (eg: the SSLv3 code is moot now that you are on Java 17, as it is
disabled at the JVM level)
> IllegalAccessError: class
> org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine
> ---
>
> Key: CXF-9034
> URL: https://issues.apache.org/jira/browse/CXF-9034
> Project: CXF
> Issue Type: Bug
>Affects Versions: 4.0.4
>Reporter: Gary D. Gregory
>Priority: Major
> Fix For: 4.1.0
>
>
> I have a complex and proprietary test that fails with
> {noformat}
> java.lang.IllegalAccessError: class
> org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine tried to access
> protected method 'void
> org.eclipse.jetty.server.Handler$AbstractContainer.()'
> (org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine and
> org.eclipse.jetty.server.Handler$AbstractContainer are in unnamed module of
> loader 'app')
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine.initializeContexts(JettyHTTPServerEngine.java:596)
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine.addServant(JettyHTTPServerEngine.java:397)
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.activate(JettyHTTPDestination.java:184)
> at
> org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:53)
> at
> org.apache.cxf.binding.AbstractBindingFactory.addListener(AbstractBindingFactory.java:95)
> at
> org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:894)
> at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:130)
> at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:364)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:255)
> at
> org.apache.cxf.jaxws.spi.ProviderImpl.createAndPublishEndpoint(ProviderImpl.java:130)
> at jakarta.xml.ws.Endpoint.publish(Endpoint.java:224)
> at
> com.seagullsw.appinterface.server.backend.soap.LS38925ClientOperationsTest.beforeClass(LS38925ClientOperationsTest.java:91)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.RunBefores.invokeMethod(RunBefores.java:33)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:93)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:40)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:529)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:757)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:452)
> at
> org.ecl
[jira] [Created] (CXF-9058) jaxws binding example in documentation no more work in v4.x because of jarkarta
Mathieu CARBONNEAUX created CXF-9058:
Summary: jaxws binding example in documentation no more work in
v4.x because of jarkarta
Key: CXF-9058
URL: https://issues.apache.org/jira/browse/CXF-9058
Project: CXF
Issue Type: Bug
Components: Tooling
Affects Versions: 4.0.5, 4.0.4, 4.0.3, 4.0.2, 4.0.1, 4.0.0
Reporter: Mathieu CARBONNEAUX
in cxf wsdl2java documentation :
[https://cxf.apache.org/docs/wsdl-to-java.html]
You have the ability to use JAXWS binding file to customise wsdl2java
generation to enable enableWrapperStyle:
{code:java}
http://www.w3.org/2001/XMLSchema";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
wsdlLocation="your.wsdl"
xmlns="http://java.sun.com/xml/ns/jaxws"
xmlns:jaxws="http://java.sun.com/xml/ns/jaxws";>
false
{code}
and i got this error :
{noformat}
org.apache.cxf.tools.common.ToolException: Not a valid jaxb or jaxws binding
file, please check the namespace{noformat}
but with v4.x cxf had upgraded to jakarta and now we need to change
namespace:
{code:java}
http://www.w3.org/2001/XMLSchema";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
wsdlLocation="your.wsdl"
xmlns="http://jakarta.ee/xml/ns/jaxws"
xmlns:jaxws="http://jakarta.ee/xml/ns/jaxws";>
false
{code}
we need to change java.sun.com to jakarta.ee and add version="3.0".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CXF-9058) jaxws binding example in documentation no more work in v4.x because of jarkarta
[
https://issues.apache.org/jira/browse/CXF-9058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mathieu CARBONNEAUX updated CXF-9058:
-
Description:
in cxf wsdl2java documentation :
[https://cxf.apache.org/docs/wsdl-to-java.html]
You have the ability to use JAXWS binding file to customise wsdl2java
generation to enable enableWrapperStyle:
{code:java}
http://www.w3.org/2001/XMLSchema";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
wsdlLocation="your.wsdl"
xmlns="http://java.sun.com/xml/ns/jaxws"
xmlns:jaxws="http://java.sun.com/xml/ns/jaxws";>
false
{code}
and i got this error :
{noformat}
org.apache.cxf.tools.common.ToolException: Not a valid jaxb or jaxws binding
file, please check the namespace{noformat}
but with v4.x cxf had upgraded to jakarta and now we need to change
namespace:
{code:java}
http://www.w3.org/2001/XMLSchema";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
wsdlLocation="your.wsdl"
xmlns="http://jakarta.ee/xml/ns/jaxws"
xmlns:jaxws="http://jakarta.ee/xml/ns/jaxws";>
false
{code}
we need to change java.sun.com to jakarta.ee and add version="3.0".
can you modify documentation to explain the difference between <4.x and >=4.x.
was:
in cxf wsdl2java documentation :
[https://cxf.apache.org/docs/wsdl-to-java.html]
You have the ability to use JAXWS binding file to customise wsdl2java
generation to enable enableWrapperStyle:
{code:java}
http://www.w3.org/2001/XMLSchema";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
wsdlLocation="your.wsdl"
xmlns="http://java.sun.com/xml/ns/jaxws"
xmlns:jaxws="http://java.sun.com/xml/ns/jaxws";>
false
{code}
and i got this error :
{noformat}
org.apache.cxf.tools.common.ToolException: Not a valid jaxb or jaxws binding
file, please check the namespace{noformat}
but with v4.x cxf had upgraded to jakarta and now we need to change
namespace:
{code:java}
http://www.w3.org/2001/XMLSchema";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
wsdlLocation="your.wsdl"
xmlns="http://jakarta.ee/xml/ns/jaxws"
xmlns:jaxws="http://jakarta.ee/xml/ns/jaxws";>
false
{code}
we need to change java.sun.com to jakarta.ee and add version="3.0".
> jaxws binding example in documentation no more work in v4.x because of
> jarkarta
> ---
>
> Key: CXF-9058
> URL: https://issues.apache.org/jira/browse/CXF-9058
> Project: CXF
> Issue Type: Bug
> Components: Tooling
>Affects Versions: 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5
>Reporter: Mathieu CARBONNEAUX
>Priority: Major
>
> in cxf wsdl2java documentation :
> [https://cxf.apache.org/docs/wsdl-to-java.html]
>
> You have the ability to use JAXWS binding file to customise wsdl2java
> generation to enable enableWrapperStyle:
>
> {code:java}
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
>wsdlLocation="your.wsdl"
>xmlns="http://java.sun.com/xml/ns/jaxws"
>xmlns:jaxws="http://java.sun.com/xml/ns/jaxws";>
>false
> {code}
>
> and i got this error :
> {noformat}
> org.apache.cxf.tools.common.ToolException: Not a valid jaxb or jaxws binding
> file, please check the namespace{noformat}
> but with v4.x cxf had upgraded to jakarta and now we need to change
> namespace:
> {code:java}
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
>wsdlLocation="your.wsdl"
>xmlns="http://jakarta.ee/xml/ns/jaxws"
>xmlns:jaxws="http://jakarta.ee/xml/ns/jaxws";>
>false
> {code}
> we need to change java.sun.com to jakarta.ee and add version="3.0".
>
> can you modify documentation to explain the difference between <4.x and >=4.x.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CXF-9039) Run Jakarta RESTful Web Services 3.1 TCK
[ https://issues.apache.org/jira/browse/CXF-9039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-9039: -- Description: Run Jakarta RESTful Web Services 3.1 TCK (JakarteEE 10). It seems like the Jakarta EE 10 jaxrs TCK is split between: - [https://github.com/jakartaee/rest/tree/3.1.0/jersey-tck] - https://github.com/jakartaee/platform-tck/tree/10.0.5 was:Run Jakarta RESTful Web Services 3.1 TCK (JakarteEE 10) > Run Jakarta RESTful Web Services 3.1 TCK > > > Key: CXF-9039 > URL: https://issues.apache.org/jira/browse/CXF-9039 > Project: CXF > Issue Type: Improvement >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0 > > > Run Jakarta RESTful Web Services 3.1 TCK (JakarteEE 10). > It seems like the Jakarta EE 10 jaxrs TCK is split between: > - [https://github.com/jakartaee/rest/tree/3.1.0/jersey-tck] > - https://github.com/jakartaee/platform-tck/tree/10.0.5 -- This message was sent by Atlassian Jira (v8.20.10#820010)
