[jira] [Created] (CXF-7179) Unable to set ServerConnector in JettyHTTPServerEngine using jetty 9
Michael Austermann created CXF-7179:
---
Summary: Unable to set ServerConnector in JettyHTTPServerEngine
using jetty 9
Key: CXF-7179
URL: https://issues.apache.org/jira/browse/CXF-7179
Project: CXF
Issue Type: Bug
Components: Transports
Affects Versions: 3.1.9
Reporter: Michael Austermann
With Jetty 9 a reference to the jetty server is needed to create a
ServerConnector (jetty's default connector).
See org.eclipse.jetty.server.ServerConnector.ServerConnector(Server)
Using the CXF JettyHTTPServerEngineFactory and JettyHTTPServerEngine to create
a jetty server, it is impossible to override the Connector.
The method
org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine.setConnector(Connector)
is useless, because it is immpossible to create a ServerConnector without a
Jetty Server and JettyHTTPServerEngine.getServer() returns null during
configuration phase of the JettyHTTPServerEngine.
The example below leads to a NullPointerException:
{noformat}
public class Example {
public static void main(String[] args) throws Exception {
JettyHTTPServerEngineFactory factory = new
JettyHTTPServerEngineFactory();
JettyHTTPServerEngine engine =
factory.createJettyHTTPServerEngine(12345, "http");
ServerConnector connector = new ServerConnector(null); //
engine.getServer() is also NULL at this time
engine.setConnector(connector);
Provider provider = Provider.provider();
EndpointImpl epi = (EndpointImpl) provider.createEndpoint(null, new
FooImpl());
epi.publish("http://0.0.0.0:12345/foo";);
}
}
{noformat}
{noformat}
Exception in thread "main" java.lang.NullPointerException
at
org.eclipse.jetty.server.AbstractConnector.(AbstractConnector.java:170)
at
org.eclipse.jetty.server.AbstractNetworkConnector.(AbstractNetworkConnector.java:44)
at
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:227)
at
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:96)
at Example.main(Example.java:14)
{noformat}
Class JettyHTTPServerEngine needs to be adapted to enable setting a custom
jetty 9 connector.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CXF-7179) Unable to set ServerConnector in JettyHTTPServerEngine using jetty 9
[
https://issues.apache.org/jira/browse/CXF-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Austermann updated CXF-7179:
Description:
With Jetty 9 a reference to the jetty server is needed to create a
ServerConnector (jetty's default connector).
See org.eclipse.jetty.server.ServerConnector.ServerConnector(Server)
Using the CXF JettyHTTPServerEngineFactory and JettyHTTPServerEngine to create
a jetty server, it is impossible to override the Connector.
The method
org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine.setConnector(Connector)
is useless, because it is impossible to create a ServerConnector without a
Jetty Server and JettyHTTPServerEngine.getServer() returns null during
configuration phase of the JettyHTTPServerEngine.
The example below leads to a NullPointerException:
{noformat}
public class Example {
public static void main(String[] args) throws Exception {
JettyHTTPServerEngineFactory factory = new
JettyHTTPServerEngineFactory();
JettyHTTPServerEngine engine =
factory.createJettyHTTPServerEngine(12345, "http");
ServerConnector connector = new ServerConnector(null); //
engine.getServer() is also NULL at this time
engine.setConnector(connector);
Provider provider = Provider.provider();
EndpointImpl epi = (EndpointImpl) provider.createEndpoint(null, new
FooImpl());
epi.publish("http://0.0.0.0:12345/foo";);
}
}
{noformat}
{noformat}
Exception in thread "main" java.lang.NullPointerException
at
org.eclipse.jetty.server.AbstractConnector.(AbstractConnector.java:170)
at
org.eclipse.jetty.server.AbstractNetworkConnector.(AbstractNetworkConnector.java:44)
at
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:227)
at
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:96)
at Example.main(Example.java:14)
{noformat}
Class JettyHTTPServerEngine needs to be adapted to enable setting a custom
jetty 9 connector.
was:
With Jetty 9 a reference to the jetty server is needed to create a
ServerConnector (jetty's default connector).
See org.eclipse.jetty.server.ServerConnector.ServerConnector(Server)
Using the CXF JettyHTTPServerEngineFactory and JettyHTTPServerEngine to create
a jetty server, it is impossible to override the Connector.
The method
org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine.setConnector(Connector)
is useless, because it is immpossible to create a ServerConnector without a
Jetty Server and JettyHTTPServerEngine.getServer() returns null during
configuration phase of the JettyHTTPServerEngine.
The example below leads to a NullPointerException:
{noformat}
public class Example {
public static void main(String[] args) throws Exception {
JettyHTTPServerEngineFactory factory = new
JettyHTTPServerEngineFactory();
JettyHTTPServerEngine engine =
factory.createJettyHTTPServerEngine(12345, "http");
ServerConnector connector = new ServerConnector(null); //
engine.getServer() is also NULL at this time
engine.setConnector(connector);
Provider provider = Provider.provider();
EndpointImpl epi = (EndpointImpl) provider.createEndpoint(null, new
FooImpl());
epi.publish("http://0.0.0.0:12345/foo";);
}
}
{noformat}
{noformat}
Exception in thread "main" java.lang.NullPointerException
at
org.eclipse.jetty.server.AbstractConnector.(AbstractConnector.java:170)
at
org.eclipse.jetty.server.AbstractNetworkConnector.(AbstractNetworkConnector.java:44)
at
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:227)
at
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:96)
at Example.main(Example.java:14)
{noformat}
Class JettyHTTPServerEngine needs to be adapted to enable setting a custom
jetty 9 connector.
> Unable to set ServerConnector in JettyHTTPServerEngine using jetty 9
>
>
> Key: CXF-7179
> URL: https://issues.apache.org/jira/browse/CXF-7179
> Project: CXF
> Issue Type: Bug
> Components: Transports
>Affects Versions: 3.1.9
>Reporter: Michael Austermann
>
> With Jetty 9 a reference to the jetty server is needed to create a
> ServerConnector (jetty's default connector).
> See org.eclipse.jetty.server.ServerConnector.ServerConnector(Server)
> Using the CXF JettyHTTPServerEngineFactory and JettyHTTPServerEngine to
> create a jetty server, it is impossible to override the Connector.
> The method
> org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine.setConnector(Connector)
> is useless, because it is impossible to create a ServerConnector without a
> Jetty Server and JettyHTTPServerEngine.getServer() returns null during
[jira] [Commented] (CXF-7160) Can not configure CXF http-jetty transport to handle X-Fowarded-for headers with Jetty 9
[
https://issues.apache.org/jira/browse/CXF-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15747822#comment-15747822
]
Sergey Beryozkin commented on CXF-7160:
---
FYI, https://issues.apache.org/jira/browse/CXF-7179.
While this CXF-7160 issue can be addressed via the reflective coding for 3.1.x
(and 3.2.0), I wonder if a dev discussion should be started on how to support
Jetty9 better
> Can not configure CXF http-jetty transport to handle X-Fowarded-for headers
> with Jetty 9
>
>
> Key: CXF-7160
> URL: https://issues.apache.org/jira/browse/CXF-7160
> Project: CXF
> Issue Type: Bug
> Components: Transports
>Affects Versions: 3.1.5
>Reporter: Joe Luo
>Assignee: Freeman Fang
>
> With Jetty 8, we can configure CXF http-jetty transport to handle reverse
> proxy headers by simply setting "forwarded" to "true" to Jetty8 NIO
> SelectChannelConnector:
> {code}
>
>
>
>class="org.eclipse.jetty.server.nio.SelectChannelConnector">
>
>
>
>
>
>
>
>
>
> {code}
> However, with Jetty 9, it is not possible to do so. Because in Jetty 9, the
> SelectChannelConnector was replaced by more generic purpose ServerConnector.
> And we can't configure ServerConnector since the old no-args constructor does
> not exist anymore in ServerConnector class and all new constructors require
> the org.eclipse.jetty.server.Server as an input parameter.
> Jetty 9 documentation here talked about "X-Forward-for Configuration":
> http://www.eclipse.org/jetty/documentation/9.4.x/configuring-connectors.html
> We should configure HttpConfiguration with ForwardedRequestCustomizer in
> order to handle reverse proxy headers:
> {code}
>
> 32768
> 8192
> 8192
>
>
>
>
>
>
> {code}
> However, CXF http-jetty transport schema is not in-sync with API changes in
> Jetty 9. There is no way to configure above with CXF http-jetty transport
> schema.
> I can think of two solutions:
> # Just like what we did in another JIRA:
> https://issues.apache.org/jira/browse/CXF-5937 for servlet, we should also
> fix CXF http-jetty transport so we can optionally react to X-Forwarded
> headers;
> # Change CXF http-jetty transport schema
> http://cxf.apache.org/schemas/configuration/http-jetty.xsd
> and related java code to allow configuring HttpConfiguration along with
> ForwardedRequestCustomizer in order to handle X-Fowarded-for headers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FEDIZ-184) Remove OGNL parser from the IdP
Colm O hEigeartaigh created FEDIZ-184: - Summary: Remove OGNL parser from the IdP Key: FEDIZ-184 URL: https://issues.apache.org/jira/browse/FEDIZ-184 Project: CXF-Fediz Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.4.0 This task is to remove the OGNL parser from the IdP, we can just use Spring EL instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FEDIZ-184) Remove OGNL parser from the IdP
[ https://issues.apache.org/jira/browse/FEDIZ-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved FEDIZ-184. --- Resolution: Fixed > Remove OGNL parser from the IdP > --- > > Key: FEDIZ-184 > URL: https://issues.apache.org/jira/browse/FEDIZ-184 > Project: CXF-Fediz > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.4.0 > > > This task is to remove the OGNL parser from the IdP, we can just use Spring > EL instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-6882) Implement JAX-RS 2.1 NIO Proposal (Writer)
[ https://issues.apache.org/jira/browse/CXF-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-6882: -- Summary: Implement JAX-RS 2.1 NIO Proposal (Writer) (was: Implement JAX-RS 2.1 NIO Proposal) > Implement JAX-RS 2.1 NIO Proposal (Writer) > -- > > Key: CXF-6882 > URL: https://issues.apache.org/jira/browse/CXF-6882 > Project: CXF > Issue Type: Sub-task > Components: JAX-RS >Reporter: Sergey Beryozkin >Assignee: Andriy Redko > Fix For: 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CXF-7180) Implement JAX-RS 2.1 NIO Proposal (Reader)
Andriy Redko created CXF-7180: - Summary: Implement JAX-RS 2.1 NIO Proposal (Reader) Key: CXF-7180 URL: https://issues.apache.org/jira/browse/CXF-7180 Project: CXF Issue Type: Sub-task Reporter: Andriy Redko -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CXF-7085) Introduce support for Server Sent Events (Client)
[ https://issues.apache.org/jira/browse/CXF-7085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-7085: - Assignee: Andriy Redko > Introduce support for Server Sent Events (Client) > - > > Key: CXF-7085 > URL: https://issues.apache.org/jira/browse/CXF-7085 > Project: CXF > Issue Type: Sub-task > Components: JAX-RS, Transports >Reporter: Sergey Beryozkin >Assignee: Andriy Redko > Fix For: 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CXF-6882) Implement JAX-RS 2.1 NIO Proposal (Writer)
[ https://issues.apache.org/jira/browse/CXF-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-6882. --- Resolution: Fixed Major part has been completed by [~sergey_beryozkin]. > Implement JAX-RS 2.1 NIO Proposal (Writer) > -- > > Key: CXF-6882 > URL: https://issues.apache.org/jira/browse/CXF-6882 > Project: CXF > Issue Type: Sub-task > Components: JAX-RS >Reporter: Sergey Beryozkin >Assignee: Andriy Redko > Fix For: 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CXF-7180) Implement JAX-RS 2.1 NIO Proposal (Reader)
[ https://issues.apache.org/jira/browse/CXF-7180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-7180: - Assignee: Andriy Redko > Implement JAX-RS 2.1 NIO Proposal (Reader) > -- > > Key: CXF-7180 > URL: https://issues.apache.org/jira/browse/CXF-7180 > Project: CXF > Issue Type: Sub-task > Components: JAX-RS >Reporter: Andriy Redko >Assignee: Andriy Redko > Fix For: 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-6882) Implement JAX-RS 2.1 NIO Proposal (Writer)
[ https://issues.apache.org/jira/browse/CXF-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-6882: -- Labels: server (was: ) > Implement JAX-RS 2.1 NIO Proposal (Writer) > -- > > Key: CXF-6882 > URL: https://issues.apache.org/jira/browse/CXF-6882 > Project: CXF > Issue Type: Sub-task > Components: JAX-RS >Reporter: Sergey Beryozkin >Assignee: Andriy Redko > Labels: server > Fix For: 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-7180) Implement JAX-RS 2.1 NIO Proposal (Reader)
[ https://issues.apache.org/jira/browse/CXF-7180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-7180: -- Labels: server (was: ) > Implement JAX-RS 2.1 NIO Proposal (Reader) > -- > > Key: CXF-7180 > URL: https://issues.apache.org/jira/browse/CXF-7180 > Project: CXF > Issue Type: Sub-task > Components: JAX-RS >Reporter: Andriy Redko >Assignee: Andriy Redko > Labels: server > Fix For: 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-7180) Implement JAX-RS 2.1 NIO Proposal (Server/Reader)
[ https://issues.apache.org/jira/browse/CXF-7180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-7180: -- Summary: Implement JAX-RS 2.1 NIO Proposal (Server/Reader) (was: Implement JAX-RS 2.1 NIO Proposal (Reader)) > Implement JAX-RS 2.1 NIO Proposal (Server/Reader) > - > > Key: CXF-7180 > URL: https://issues.apache.org/jira/browse/CXF-7180 > Project: CXF > Issue Type: Sub-task > Components: JAX-RS >Reporter: Andriy Redko >Assignee: Andriy Redko > Labels: server > Fix For: 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-6882) Implement JAX-RS 2.1 NIO Proposal (Server/Writer)
[ https://issues.apache.org/jira/browse/CXF-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-6882: -- Summary: Implement JAX-RS 2.1 NIO Proposal (Server/Writer) (was: Implement JAX-RS 2.1 NIO Proposal (Writer)) > Implement JAX-RS 2.1 NIO Proposal (Server/Writer) > - > > Key: CXF-6882 > URL: https://issues.apache.org/jira/browse/CXF-6882 > Project: CXF > Issue Type: Sub-task > Components: JAX-RS >Reporter: Sergey Beryozkin >Assignee: Andriy Redko > Labels: server > Fix For: 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CXF-7182) Implement JAX-RS 2.1 NIO Proposal (Client/Writer)
Andriy Redko created CXF-7182: - Summary: Implement JAX-RS 2.1 NIO Proposal (Client/Writer) Key: CXF-7182 URL: https://issues.apache.org/jira/browse/CXF-7182 Project: CXF Issue Type: Sub-task Reporter: Andriy Redko Assignee: Andriy Redko -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-7182) Implement JAX-RS 2.1 NIO Proposal (Client/Writer)
[ https://issues.apache.org/jira/browse/CXF-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-7182: -- Labels: client (was: ) > Implement JAX-RS 2.1 NIO Proposal (Client/Writer) > - > > Key: CXF-7182 > URL: https://issues.apache.org/jira/browse/CXF-7182 > Project: CXF > Issue Type: Sub-task > Components: JAX-RS >Reporter: Andriy Redko >Assignee: Andriy Redko > Labels: client > Fix For: 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CXF-7181) Implement JAX-RS 2.1 NIO Proposal (Client/Reader)
Andriy Redko created CXF-7181: - Summary: Implement JAX-RS 2.1 NIO Proposal (Client/Reader) Key: CXF-7181 URL: https://issues.apache.org/jira/browse/CXF-7181 Project: CXF Issue Type: Sub-task Reporter: Andriy Redko Assignee: Andriy Redko -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CXF-7181) Implement JAX-RS 2.1 NIO Proposal (Client/Reader)
[ https://issues.apache.org/jira/browse/CXF-7181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-7181: -- Labels: client (was: ) > Implement JAX-RS 2.1 NIO Proposal (Client/Reader) > - > > Key: CXF-7181 > URL: https://issues.apache.org/jira/browse/CXF-7181 > Project: CXF > Issue Type: Sub-task > Components: JAX-RS >Reporter: Andriy Redko >Assignee: Andriy Redko > Labels: client > Fix For: 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-7168) CXF WSN Publisher SOAP 1.2 Binding
[
https://issues.apache.org/jira/browse/CXF-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15750575#comment-15750575
]
Freeman Fang commented on CXF-7168:
---
We should create the endpoint with soap1.2 enabled when the jaxws provider is
CXF(like JaxwsEndpointManager already do), so that both soap1.1 and soap1.2 are
supported OOTB.
And the CXFWSNHelper should be the place to do it, as only when the provider is
CXF the CXFWSNHelper is used
> CXF WSN Publisher SOAP 1.2 Binding
> --
>
> Key: CXF-7168
> URL: https://issues.apache.org/jira/browse/CXF-7168
> Project: CXF
> Issue Type: Improvement
> Components: WS-* Components
>Affects Versions: 3.1.7, 3.1.8
> Environment: Windows 7
>Reporter: Fahrettin Gökgöz
>Assignee: Freeman Fang
>Priority: Critical
> Labels: patch
>
> org.apache.cxf.wsn.client.Publisher -> SOAP 1.2 binding
> Following constructor does not allow to set SOAP binding for publisher.
> public Publisher(Callback callback, String address) {
> this.callback = callback;
> this.address = address;
> if (callback == null || address == null) {
> this.endpoint = null;
> } else {
> this.endpoint = WSNHelper.getInstance().publish(address, this);
> }
>}
> Which can be solve in the WSNHelper with using
> javax.xml.ws.Endpoint.create(String bindingId, Object implementor);
> instead of
> javax.xml.ws.Endpoint.create(Object implementor);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CXF-7168) CXF WSN Publisher SOAP 1.2 Binding
[
https://issues.apache.org/jira/browse/CXF-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved CXF-7168.
---
Resolution: Fixed
Fix Version/s: 3.0.13
3.1.10
> CXF WSN Publisher SOAP 1.2 Binding
> --
>
> Key: CXF-7168
> URL: https://issues.apache.org/jira/browse/CXF-7168
> Project: CXF
> Issue Type: Improvement
> Components: WS-* Components
>Affects Versions: 3.1.7, 3.1.8
> Environment: Windows 7
>Reporter: Fahrettin Gökgöz
>Assignee: Freeman Fang
>Priority: Critical
> Labels: patch
> Fix For: 3.1.10, 3.0.13
>
>
> org.apache.cxf.wsn.client.Publisher -> SOAP 1.2 binding
> Following constructor does not allow to set SOAP binding for publisher.
> public Publisher(Callback callback, String address) {
> this.callback = callback;
> this.address = address;
> if (callback == null || address == null) {
> this.endpoint = null;
> } else {
> this.endpoint = WSNHelper.getInstance().publish(address, this);
> }
>}
> Which can be solve in the WSNHelper with using
> javax.xml.ws.Endpoint.create(String bindingId, Object implementor);
> instead of
> javax.xml.ws.Endpoint.create(Object implementor);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
