[jira] [Updated] (CXF-7317) Non-URL encoded Content-Id href does not seem be serialized by CXF's AttachmentSerializer
[ https://issues.apache.org/jira/browse/CXF-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst updated CXF-7317: Summary: Non-URL encoded Content-Id href does not seem be serialized by CXF's AttachmentSerializer (was: Non-URL encoded Content-Id href does not seem be serilaized by CXF's AttachmentSerializer) > Non-URL encoded Content-Id href does not seem be serialized by CXF's > AttachmentSerializer > - > > Key: CXF-7317 > URL: https://issues.apache.org/jira/browse/CXF-7317 > Project: CXF > Issue Type: Bug > Components: Core >Affects Versions: 3.1.10 >Reporter: Viral Gohel >Priority: Major > Attachments: mtomExample.war > > > CXF-6484 states that, > >> URL-encoded content ID for MTOM attachments causes problems with web > >> service clients. This is effectively a regression on: > https://issues.apache.org/jira/browse/CXF-2669 > For example, If the namespace is "https://cxf.apache.org/; for the service > endpoint, then the content id is now: > 5726d366-df25-4945-9f3b-3003a2ae8a70-3@http%3A%2F%2Fcxf.apache.org%2F > It was previously: > 5726d366-df25-4945-9f3b-3003a2ae8a7...@cxf.apache.org > Hence, > Actual results: > Content Id contains the full namespace (as URL) which is URL encoded: > 5726d366-df25-4945-9f3b-3003a2ae8a70-3@http%3A%2F%2Fcxf.apache.org%2F > Expected results: > Content id does not require encoding and only contains hostname: > 5726d366-df25-4945-9f3b-3003a2ae8a7...@cxf.apache.org > With the attached reproducer, here's what the results looks like, > Actual Result - > href="cid:0842d204-23ec-4b6f-955b-0e38a4c2f35a-1@urn%3Awsc.td.com%2Fcis%2F2010%2F01%2F19 > Expected Result - > href="cid:0842d204-23ec-4b6f-955b-0e38a4c2f35a-1@urn:Awsc.td.com/cis/2010/01/19 > The difference here compared to the fix for CXF-6484, is that a non-url > encoded href using namespace with 'urn:' for the attachments is used. > For example, like the below in the @WebService class, > @WebService(targetNamespace = "urn:wsc.td.com/cis/2010/01/19") > To me, it seems that the fix for CXF-6484 does not work for non-url encoded > href. > I.e After the fix of CXF-6484, > Actual Result - > href="cid:0842d204-23ec-4b6f-955b-0e38a4c2f35a-1@urn%3Awsc.td.com%2Fcis%2F2010%2F01%2F19 > Expected Result - > href="cid:0842d204-23ec-4b6f-955b-0e38a4c2f35a-1@urn:Awsc.td.com/cis/2010/01/19 > It looks like CXF's AttachmentSerializer is not able to serialize the forward > slashes(/) or the AttachmentUtil needs to be changed. > I am not sure if the proper urn: namespaces should be of format, i.e > urn:com.namespace.someResource or it can be also like, > urn:com/namespace/someResource. > Can we make CXF to interpret and display the href in the Content-Id with > non-url namespace as > cid:0842d204-23ec-4b6f-955b-0e38a4c2f35a-1@urn:Awsc.td.com/cis/2010/01/19 ? > instead of > href="cid:0842d204-23ec-4b6f-955b-0e38a4c2f35a-1@urn%3Awsc.td.com%2Fcis%2F2010%2F01%2F19 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CXF-7682) context.get(MessageContext.HTTP_REQUEST_HEADERS) always returns null for client
[
https://issues.apache.org/jira/browse/CXF-7682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst resolved CXF-7682.
-
Resolution: Fixed
Fix Version/s: 3.2.5
3.1.16
> context.get(MessageContext.HTTP_REQUEST_HEADERS) always returns null for
> client
> ---
>
> Key: CXF-7682
> URL: https://issues.apache.org/jira/browse/CXF-7682
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
>Reporter: Jimmy Praet
>Priority: Major
> Fix For: 3.1.16, 3.2.5
>
>
> I have a client-side LogicalHandler that adds some HTTP headers and am
> noticing it causes the existing SOAPAction HTTP header (already added
> automatically by the JAX-WS runtime) to be removed.
> My handler code looks like this:
> {code:java}
> public boolean handleMessage(LogicalMessageContext context) {
> Boolean outbound = (Boolean)
> context.get(MessageContext.MESSAGE_OUTBOUND_PROPERTY);
> if (outbound) {
> Map> headers =
> (Map>)
> context.get(MessageContext.HTTP_REQUEST_HEADERS);
> if (headers == null) {
> headers = new HashMap>();
> context.put(MessageContext.HTTP_REQUEST_HEADERS, headers);
> }
> for (Map.Entry entry : Tracer.getEntries().entrySet()) {
> headers.put(entry.getKey(),
> Collections.singletonList(entry.getValue()));
> }
> }
> return true;
> }
> {code}
> I had a quick look at the code and noticed the
> [LogicalMessageContextImpl#get(Object)
> |https://github.com/apache/cxf/blob/a36af6323505211479c875fb9923cc6dcbc6ac95/rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/handler/logical/LogicalMessageContextImpl.java#L53]
> always returns null on the client side (isRequestor() = true).
> So my handler will create a new header map and put it on the context, which
> is internally mapped to key "org.apache.cxf.message.Message.PROTOCOL_HEADERS"
> [here|https://github.com/apache/cxf/blob/master/rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/context/WrappedMessageContext.java#L462].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CXF-7730) Swagger UI 3.5.0 is not working with apaceh cxf 3.1.10
[ https://issues.apache.org/jira/browse/CXF-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst resolved CXF-7730. - Resolution: Won't Fix Closing as no further feedback has been provided and existing testcases are working. > Swagger UI 3.5.0 is not working with apaceh cxf 3.1.10 > -- > > Key: CXF-7730 > URL: https://issues.apache.org/jira/browse/CXF-7730 > Project: CXF > Issue Type: Bug >Reporter: div >Priority: Major > Fix For: NeedMoreInfo > > Attachments: image-2018-04-26-08-42-55-781.png, > image-2018-04-26-08-51-25-813.png > > > Hi, > > We are trying to create a swagger ui for apache cxf services and > :/swagger.json gives me json response. But when I try > [http://localhost:/api-docs/?url=/swagger.json|http://localhost:9110/api-docs/?url=/swagger.json] > I keep getting 404. > > !image-2018-04-26-08-42-55-781.png! > http://localhost:/api-docs?url=swagger.json > !image-2018-04-26-08-51-25-813.png! > > org.apache.cxf > cxf-rt-rs-service-description-swagger > 3.1.11 > > > > org.webjars > swagger-ui > 3.5.0 > > > class="org.apache.cxf.jaxrs.swagger.Swagger2Feature"> > > class="com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider" /> > > > > > > > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CXF-7742) CdiResourceProvider is not thread safe
[ https://issues.apache.org/jira/browse/CXF-7742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1649#comment-1649 ] Dennis Kieselhorst commented on CXF-7742: - [~romain.manni-bucau] [~reta] PR has been merged, can we resolve this issue? > CdiResourceProvider is not thread safe > -- > > Key: CXF-7742 > URL: https://issues.apache.org/jira/browse/CXF-7742 > Project: CXF > Issue Type: Bug >Affects Versions: 3.2.4 >Reporter: Romain Manni-Bucau >Priority: Major > Fix For: 3.2.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CXF-7742) CdiResourceProvider is not thread safe
[ https://issues.apache.org/jira/browse/CXF-7742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst updated CXF-7742: Fix Version/s: 3.2.5 > CdiResourceProvider is not thread safe > -- > > Key: CXF-7742 > URL: https://issues.apache.org/jira/browse/CXF-7742 > Project: CXF > Issue Type: Bug >Affects Versions: 3.2.4 >Reporter: Romain Manni-Bucau >Priority: Major > Fix For: 3.2.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CXF-7739) java-cxf WebService Exceptioon
[ https://issues.apache.org/jira/browse/CXF-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst updated CXF-7739: Fix Version/s: NeedMoreInfo > java-cxf WebService Exceptioon > -- > > Key: CXF-7739 > URL: https://issues.apache.org/jira/browse/CXF-7739 > Project: CXF > Issue Type: Bug > Components: Core, JAX-RS Security, JAX-WS Runtime >Affects Versions: 3.2.4 >Reporter: laibaoliu >Priority: Major > Fix For: NeedMoreInfo > > > I am working on CXF 3.2.4, When I access my wsdl and get following error: > Invocation of init method failed; nested exception is > javax.xml.ws.WebServiceException: > org.apache.cxf.service.factory.ServiceConstructionException: Failed to create > service. > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1628) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.apache.cxf.transport.servlet.CXFServlet.createSpringContext(CXFServlet.java:151) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.apache.cxf.transport.servlet.CXFServlet.loadBus(CXFServlet.java:74) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.apache.cxf.transport.servlet.CXFNonSpringServlet.init(CXFNonSpringServlet.java:83) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:582) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.eclipse.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:445) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:711) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1651) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > com.hp.erp.ei.web.EICXFServletFilter.doFilter(EICXFServletFilter.java:33) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1631) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > com.hp.alm.platform.web.XSSProtectionFilter.doFilter(XSSProtectionFilter.java:27) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1622) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > com.mercury.optane.core.state.ServerStatusFilter.doFilter(ServerStatusFilter.java:37) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1622) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.hp.qc.web.restapi.authentication.LwssoRedirectFilter.doFilter(LwssoRedirectFilter.java:26) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1622) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at > com.hp.alm.platform.web.NoSniffFilter.doFilter(NoSniffFilter.java:20) > INFO | jvm 1 | 2018/05/14 15:26:40.858 | at >
[jira] [Commented] (CXF-7746) Swagger2Feature - SwaggerUiResolver & JBoss 7 EAP
[
https://issues.apache.org/jira/browse/CXF-7746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498884#comment-16498884
]
Dennis Kieselhorst commented on CXF-7746:
-
Could you create a pull request for it? [https://github.com/apache/cxf/pulls]
Please optimize the code by using the existing constant
{color:#660e7a}UI_RESOURCES_ROOT_START {color}and maybe add some more constants
for the "magic numbers".
> Swagger2Feature - SwaggerUiResolver & JBoss 7 EAP
> -
>
> Key: CXF-7746
> URL: https://issues.apache.org/jira/browse/CXF-7746
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.2.4
>Reporter: Etienne Dumont
>Assignee: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.2.5
>
>
> Hi,
> Same problem as CXF-7474, but for JBoss EAP 7.0 & CXF 3.2.4.
> The SwaggerUiResolver is not able to find the swagger-ui jar, included in our
> war via maven; the path returned by the class loader ends with ".jar/"
> instead of the expected ".jar" or ".jar!/".
> To bypass the problem, we modified the checkUiRoot as follow:
> {code:java}
> // Artifact: cxf-rt-rs-service-description-swagger
> // Class: org.apache.cxf.jaxrs.swagger.SwaggerUiResolver
> protected static String checkUiRoot(String urlStr, String swaggerUiVersion)
> {
> int swaggerUiIndex = urlStr.lastIndexOf("/swagger-ui-");
> if (swaggerUiIndex != -1)
> {
> boolean urlEndsWithJarSep = urlStr.endsWith(".jar!/");
> int offset = -1;
> if (urlEndsWithJarSep || urlStr.endsWith(".jar"))
> {
> offset = urlEndsWithJarSep ? 6 : 4;
> }
> else if (urlStr.endsWith(".jar/"))
> {
> offset = 5;
> urlEndsWithJarSep = true;
> }
> if (offset > -1)
> {
> String version = urlStr.substring(swaggerUiIndex + 12, urlStr.length()
> - offset);
> if (swaggerUiVersion != null && !swaggerUiVersion.equals(version))
> {
> return null;
> }
> else
> {
> if (!urlEndsWithJarSep)
> {
> urlStr = "jar:" + urlStr + "!/";
> }
> return urlStr + "META-INF/resources/webjars/swagger-ui/" + version +
> "/";
> }
> }
> }
> return null;
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CXF-7746) Swagger2Feature - SwaggerUiResolver & JBoss 7 EAP
[
https://issues.apache.org/jira/browse/CXF-7746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst updated CXF-7746:
Fix Version/s: 3.2.5
> Swagger2Feature - SwaggerUiResolver & JBoss 7 EAP
> -
>
> Key: CXF-7746
> URL: https://issues.apache.org/jira/browse/CXF-7746
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.2.4
>Reporter: Etienne Dumont
>Assignee: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.2.5
>
>
> Hi,
> Same problem as CXF-7474, but for JBoss EAP 7.0 & CXF 3.2.4.
> The SwaggerUiResolver is not able to find the swagger-ui jar, included in our
> war via maven; the path returned by the class loader ends with ".jar/"
> instead of the expected ".jar" or ".jar!/".
> To bypass the problem, we modified the checkUiRoot as follow:
> {code:java}
> // Artifact: cxf-rt-rs-service-description-swagger
> // Class: org.apache.cxf.jaxrs.swagger.SwaggerUiResolver
> protected static String checkUiRoot(String urlStr, String swaggerUiVersion)
> {
> int swaggerUiIndex = urlStr.lastIndexOf("/swagger-ui-");
> if (swaggerUiIndex != -1)
> {
> boolean urlEndsWithJarSep = urlStr.endsWith(".jar!/");
> int offset = -1;
> if (urlEndsWithJarSep || urlStr.endsWith(".jar"))
> {
> offset = urlEndsWithJarSep ? 6 : 4;
> }
> else if (urlStr.endsWith(".jar/"))
> {
> offset = 5;
> urlEndsWithJarSep = true;
> }
> if (offset > -1)
> {
> String version = urlStr.substring(swaggerUiIndex + 12, urlStr.length()
> - offset);
> if (swaggerUiVersion != null && !swaggerUiVersion.equals(version))
> {
> return null;
> }
> else
> {
> if (!urlEndsWithJarSep)
> {
> urlStr = "jar:" + urlStr + "!/";
> }
> return urlStr + "META-INF/resources/webjars/swagger-ui/" + version +
> "/";
> }
> }
> }
> return null;
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CXF-7746) Swagger2Feature - SwaggerUiResolver & JBoss 7 EAP
[
https://issues.apache.org/jira/browse/CXF-7746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst reassigned CXF-7746:
---
Assignee: Dennis Kieselhorst
> Swagger2Feature - SwaggerUiResolver & JBoss 7 EAP
> -
>
> Key: CXF-7746
> URL: https://issues.apache.org/jira/browse/CXF-7746
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.2.4
>Reporter: Etienne Dumont
>Assignee: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.2.5
>
>
> Hi,
> Same problem as CXF-7474, but for JBoss EAP 7.0 & CXF 3.2.4.
> The SwaggerUiResolver is not able to find the swagger-ui jar, included in our
> war via maven; the path returned by the class loader ends with ".jar/"
> instead of the expected ".jar" or ".jar!/".
> To bypass the problem, we modified the checkUiRoot as follow:
> {code:java}
> // Artifact: cxf-rt-rs-service-description-swagger
> // Class: org.apache.cxf.jaxrs.swagger.SwaggerUiResolver
> protected static String checkUiRoot(String urlStr, String swaggerUiVersion)
> {
> int swaggerUiIndex = urlStr.lastIndexOf("/swagger-ui-");
> if (swaggerUiIndex != -1)
> {
> boolean urlEndsWithJarSep = urlStr.endsWith(".jar!/");
> int offset = -1;
> if (urlEndsWithJarSep || urlStr.endsWith(".jar"))
> {
> offset = urlEndsWithJarSep ? 6 : 4;
> }
> else if (urlStr.endsWith(".jar/"))
> {
> offset = 5;
> urlEndsWithJarSep = true;
> }
> if (offset > -1)
> {
> String version = urlStr.substring(swaggerUiIndex + 12, urlStr.length()
> - offset);
> if (swaggerUiVersion != null && !swaggerUiVersion.equals(version))
> {
> return null;
> }
> else
> {
> if (!urlEndsWithJarSep)
> {
> urlStr = "jar:" + urlStr + "!/";
> }
> return urlStr + "META-INF/resources/webjars/swagger-ui/" + version +
> "/";
> }
> }
> }
> return null;
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CXF-7751) Codegen plugin can't work with empty extraarg tag
[
https://issues.apache.org/jira/browse/CXF-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst updated CXF-7751:
Fix Version/s: 3.2.5
3.1.16
> Codegen plugin can't work with empty extraarg tag
> -
>
> Key: CXF-7751
> URL: https://issues.apache.org/jira/browse/CXF-7751
> Project: CXF
> Issue Type: Bug
> Components: Build system
>Affects Versions: 3.1.6, 3.2.4
>Reporter: Sergey Pushkin
>Assignee: Daniel Kulp
>Priority: Critical
> Fix For: 3.1.16, 3.2.5
>
>
>
> I use cxf codegen plugin and i have separate maven profile to generate code
> by wsdl. My problem in extraarg tag.
> i have soap connectors, that have pom where is configuration of codegen
> plugin. When project runnnig with generate code by wsdl profile
> ${wsdl.extraarg.keep} equal "-keep." And that good work.
> When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize
> and in codegen in extraarg put emty string " ".
> {code:java}
>
> org.apache.cxf
> cxf-codegen-plugin
> 3.1.6
>
>
> generate-sources
> generate-sources
>
> src/main/java
>
>
>
> ../wsdl//ReferenceDataService.wsdl
>
>
> ${wsdl.extraarg.keep}
>
>
>
> UTF-8
>
>
> wsdl2java
>
>
>
>
> {code}
> In result i have error.
> [ERROR] Failed to execute goal
> org.apache.cxf:cxf-codegen-plugin:3.1.6:wsdl2java (generate-sources) on
> project test-project: Execution generate-sources of goal
> org.apache.cxf:cxf-codegen-plugin:3.1.6:wsdl2java failed:
> org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
> argument:
> [file:/C:/Projects/test/backend/soap-connectors/wsdl/ReferenceDataService.wsdl|file:///C:/Projects/test/backend/soap-connectors/wsdl/ReferenceDataService.wsdl]
> it's couse emppty is "The path and name of the WSDL file to use in generating
> the code."
> Okey. I cheat and use that:
> {code:java}
>
> org.apache.cxf
> cxf-codegen-plugin
> 3.1.6
>
>
> generate-sources
> generate-sources
>
> src/main/java
>
>
>
> ../wsdl//ReferenceDataService.wsdl
>
>
>
> ../wsdl//ReferenceDataService.wsdl
> ${wsdl.extraarg.keep}
>
>
>
> UTF-8
>
>
> wsdl2java
>
>
>
> {code}
> In result i have error "Unexpected argument" with empty string.
> [ERROR] Failed to execute goal
> org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java (generate-sources) on
> project test-project: Execution generate-sources of goal
> org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java failed:
> org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
> argument:
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CXF-7751) Codegen plugin can't work with empty extraarg tag
[
https://issues.apache.org/jira/browse/CXF-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst reassigned CXF-7751:
---
Assignee: Daniel Kulp
> Codegen plugin can't work with empty extraarg tag
> -
>
> Key: CXF-7751
> URL: https://issues.apache.org/jira/browse/CXF-7751
> Project: CXF
> Issue Type: Bug
> Components: Build system
>Affects Versions: 3.1.6, 3.2.4
>Reporter: Sergey Pushkin
>Assignee: Daniel Kulp
>Priority: Critical
>
>
> I use cxf codegen plugin and i have separate maven profile to generate code
> by wsdl. My problem in extraarg tag.
> i have soap connectors, that have pom where is configuration of codegen
> plugin. When project runnnig with generate code by wsdl profile
> ${wsdl.extraarg.keep} equal "-keep." And that good work.
> When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize
> and in codegen in extraarg put emty string " ".
> {code:java}
>
> org.apache.cxf
> cxf-codegen-plugin
> 3.1.6
>
>
> generate-sources
> generate-sources
>
> src/main/java
>
>
>
> ../wsdl//ReferenceDataService.wsdl
>
>
> ${wsdl.extraarg.keep}
>
>
>
> UTF-8
>
>
> wsdl2java
>
>
>
>
> {code}
> In result i have error.
> [ERROR] Failed to execute goal
> org.apache.cxf:cxf-codegen-plugin:3.1.6:wsdl2java (generate-sources) on
> project test-project: Execution generate-sources of goal
> org.apache.cxf:cxf-codegen-plugin:3.1.6:wsdl2java failed:
> org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
> argument:
> [file:/C:/Projects/test/backend/soap-connectors/wsdl/ReferenceDataService.wsdl|file:///C:/Projects/test/backend/soap-connectors/wsdl/ReferenceDataService.wsdl]
> it's couse emppty is "The path and name of the WSDL file to use in generating
> the code."
> Okey. I cheat and use that:
> {code:java}
>
> org.apache.cxf
> cxf-codegen-plugin
> 3.1.6
>
>
> generate-sources
> generate-sources
>
> src/main/java
>
>
>
> ../wsdl//ReferenceDataService.wsdl
>
>
>
> ../wsdl//ReferenceDataService.wsdl
> ${wsdl.extraarg.keep}
>
>
>
> UTF-8
>
>
> wsdl2java
>
>
>
> {code}
> In result i have error "Unexpected argument" with empty string.
> [ERROR] Failed to execute goal
> org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java (generate-sources) on
> project test-project: Execution generate-sources of goal
> org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java failed:
> org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
> argument:
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CXF-7600) Add Automatic-Module-Name MANIFEST entry for Java 9 compatibility
[ https://issues.apache.org/jira/browse/CXF-7600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498645#comment-16498645 ] ASF GitHub Bot commented on CXF-7600: - reta commented on issue #420: CXF-7600: Add Automatic-Module-Name MANIFEST entry for Java 9 compatibility URL: https://github.com/apache/cxf/pull/420#issuecomment-394025516 @cschneider What do you think about this PR? Good to go? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add Automatic-Module-Name MANIFEST entry for Java 9 compatibility > - > > Key: CXF-7600 > URL: https://issues.apache.org/jira/browse/CXF-7600 > Project: CXF > Issue Type: Improvement > Components: Build system >Affects Versions: 3.2.1 >Reporter: Dennis Kieselhorst >Assignee: Andriy Redko >Priority: Major > > See mailinglist discussion: > https://lists.apache.org/thread.html/790a276b4a7b3d977f5cb1abdc764a0529324b286fba915d19352afb@%3Cdev.cxf.apache.org%3E > Similar issues: IO-551, LANG-1338, CODEC-242 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CXF-7749) OpenApi 3.0: Enable restriction of swagger definitions per CXF endpoint (based on the path)
[
https://issues.apache.org/jira/browse/CXF-7749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko reassigned CXF-7749:
-
Assignee: Andriy Redko
> OpenApi 3.0: Enable restriction of swagger definitions per CXF endpoint
> (based on the path)
> ---
>
> Key: CXF-7749
> URL: https://issues.apache.org/jira/browse/CXF-7749
> Project: CXF
> Issue Type: New Feature
>Reporter: Bharanidharan Viswanathan
>Assignee: Andriy Redko
>Priority: Major
>
> h3: What
> OpenApi 3.0 - enable restricting swagger definitions per CXF endpoint (based
> on the path)! For example, if there would two CXF endpoints ("/admin" &
> "/public") & then on each of them, only the specific swagger definitions
> should be visible.
> [~reta] FYI.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FEDIZ-217) SAML authentication fails in plugin
[
https://issues.apache.org/jira/browse/FEDIZ-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498229#comment-16498229
]
Arnaud MERGEY commented on FEDIZ-217:
-
tested recently it works perfectly with OKTA and some other provider as well,
thanks !
Any ideas when the 1.4.4 will be released ?
> SAML authentication fails in plugin
> ---
>
> Key: FEDIZ-217
> URL: https://issues.apache.org/jira/browse/FEDIZ-217
> Project: CXF-Fediz
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 1.4.3
>Reporter: Arnaud MERGEY
>Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 1.4.4
>
>
> On a tomcat hosting a SP application trying to authenticate against a SAML
> IDP (OKTA)
> authentication fails with this log:
> May 11, 2018 11:22:14 AM
> org.apache.cxf.fediz.core.processor.SAMLProcessorImpl processRelayState
> SEVERE: Missing Request State
> May 11, 2018 11:22:14 AM org.apache.cxf.fediz.core.handler.SigninHandler
> handleRequest
> SEVERE: Federation processing failed: The request was invalid or malformed
> I checked in the code and it fails because request state in
> org.apache.cxf.fediz.core.processor.FedizRequest is null, but it seems with
> SAML protocol
> org.apache.cxf.fediz.core.processor.FedizRequest.setRequestState(RequestState)
> is never called, so I am wondering how it can be different from null and I
> suspect a bug
> I manage to patch fediz to have it working, I could propose a Pull request
> for this if required
> Additionally to OKTA I also tried with samling for a simple test setup, same
> error
>
> {code:java}
>
>
>
> http://localhost:8080/myApp/
>
>
>
> type="JKS" />
>
>
>
>
>
> http://www.w3.org/2001/XMLSchema-instance;
> xsi:type="samlProtocolType" version="2.0">
> true
> true
> https://capriza.github.io/samling/samling.html
> groups
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CXF-7751) Codegen plugin can't work with empty extraarg tag
[
https://issues.apache.org/jira/browse/CXF-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Pushkin updated CXF-7751:
Description:
I use cxf codegen plugin and i have separate maven profile to generate code by
wsdl. My problem in extraarg tag.
i have soap connectors, that have pom where is configuration of codegen plugin.
When project runnnig with generate code by wsdl profile ${wsdl.extraarg.keep}
equal "-keep." And that good work.
When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize and
in codegen in extraarg put emty string " ".
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
{code}
In result i have error.
[ERROR] Failed to execute goal
org.apache.cxf:cxf-codegen-plugin:3.1.6:wsdl2java (generate-sources) on project
test-project: Execution generate-sources of goal
org.apache.cxf:cxf-codegen-plugin:3.1.6:wsdl2java failed:
org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
argument:
[file:/C:/Projects/test/backend/soap-connectors/wsdl/ReferenceDataService.wsdl|file:///C:/Projects/test/backend/soap-connectors/wsdl/ReferenceDataService.wsdl]
it's couse emppty is "The path and name of the WSDL file to use in generating
the code."
Okey. I cheat and use that:
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
{code}
In result i have error "Unexpected argument" with empty string.
[ERROR] Failed to execute goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java (generate-sources) on project
test-project: Execution generate-sources of goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java failed:
org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
argument:
was:
I use cxf codegen plugin and i have separate maven profile to generate code by
wsdl. My problem in extraarg tag.
i have soap connectors, that have pom where is configuration of codegen plugin.
When project runnnig with generate code by wsdl profile ${wsdl.extraarg.keep}
equal "-keep." And that good work.
When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize and
in codegen in extraarg put emty string " ".
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
{code}
In result i have error.
[ERROR] Failed to execute goal
org.apache.cxf:cxf-codegen-plugin:3.1.6:wsdl2java (generate-sources) on project
test-project: Execution generate-sources of goal
org.apache.cxf:cxf-codegen-plugin:3.1.6:wsdl2java failed:
org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
argument:
[file:/C:/Projects/test/backend/soap-connectors/wsdl/ReferenceDataService.wsdl|file:///C:/Projects/test/backend/soap-connectors/wsdl/ReferenceDataService.wsdl]
it's couse emppty is "The path and name of the WSDL file to use in generating
the code."
Okey. I cheat and use that:
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
[jira] [Updated] (CXF-7751) Codegen plugin can't work with empty extraarg tag
[
https://issues.apache.org/jira/browse/CXF-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Pushkin updated CXF-7751:
Description:
I use cxf codegen plugin and i have separate maven profile to generate code by
wsdl. My problem in extraarg tag.
i have soap connectors, that have pom where is configuration of codegen plugin.
When project runnnig with generate code by wsdl profile ${wsdl.extraarg.keep}
equal "-keep." And that good work.
When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize and
in codegen in extraarg put emty string " ".
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
{code}
In result i have error.
[ERROR] Failed to execute goal
org.apache.cxf:cxf-codegen-plugin:3.1.6:wsdl2java (generate-sources) on project
test-project: Execution generate-sources of goal
org.apache.cxf:cxf-codegen-plugin:3.1.6:wsdl2java failed:
org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
argument:
[file:/C:/Projects/test/backend/soap-connectors/wsdl/ReferenceDataService.wsdl|file:///C:/Projects/test/backend/soap-connectors/wsdl/ReferenceDataService.wsdl]
it's couse emppty is "The path and name of the WSDL file to use in generating
the code."
Okey. I cheat and use that:
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
{code}
In result i have error for empty string arg.
[ERROR] Failed to execute goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java (generate-sources) on project
test-project: Execution generate-sources of goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java failed:
org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
argument:
was:
I use cxf codegen plugin and i have separate maven profile to generate code by
wsdl. My problem in extraarg tag.
i have soap connectors, that have pom where is configuration of codegen plugin.
When project runnnig with generate code by wsdl profile ${wsdl.extraarg.keep}
equal "-keep." And that good work.
When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize and
in codegen in extraarg put emty string " ".
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
{code}
In result i have error.
[ERROR] Failed to execute goal
org.apache.cxf:cxf-codegen-plugin:3.1.6:wsdl2java (generate-sources) on project
test-project: Execution generate-sources of goal
org.apache.cxf:cxf-codegen-plugin:3.1.6:wsdl2java failed:
org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
argument:
file:/C:/Projects/test/backend/soap-connectors/wsdl/ReferenceDataService.wsdl
it's couse emppty is "The path and name of the WSDL file to use in generating
the code."
Okey. I cheat and use that:
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
[jira] [Updated] (CXF-7751) Codegen plugin can't work with empty extraarg tag
[
https://issues.apache.org/jira/browse/CXF-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Pushkin updated CXF-7751:
Description:
I use cxf codegen plugin and i have separate maven profile to generate code by
wsdl. My problem in extraarg tag.
i have soap connectors, that have pom where is configuration of codegen plugin.
When project runnnig with generate code by wsdl profile ${wsdl.extraarg.keep}
equal "-keep." And that good work.
When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize and
in codegen in extraarg put emty string " ".
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
{code}
In result i have error.
[ERROR] Failed to execute goal
org.apache.cxf:cxf-codegen-plugin:3.1.6:wsdl2java (generate-sources) on project
test-project: Execution generate-sources of goal
org.apache.cxf:cxf-codegen-plugin:3.1.6:wsdl2java failed:
org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
argument:
file:/C:/Projects/test/backend/soap-connectors/wsdl/ReferenceDataService.wsdl
it's couse emppty is "The path and name of the WSDL file to use in generating
the code."
Okey. I cheat and use that:
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
{code}
In result i have error for empty string arg.
[ERROR] Failed to execute goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java (generate-sources) on project
test-project: Execution generate-sources of goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java failed:
org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
argument:
was:
I use cxf codegen plugin and i have separate maven profile to generate code by
wsdl. My problem in extraarg tag.
i have soap connectors, that have pom where is configuration of codegen plugin.
When project runnnig with generate code by wsdl profile ${wsdl.extraarg.keep}
equal "-keep." And that good work.
When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize and
in codegen in extraarg put emty string " ".
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
{code}
In result i have error.
Okey. I cheat and use that:
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
{code}
In result i have error for empty string arg.
[ERROR] Failed to execute goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java (generate-sources) on project
test-project: Execution generate-sources of goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java failed:
org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
argument:
> Codegen plugin can't work with empty extraarg tag
> -
>
> Key: CXF-7751
> URL: https://issues.apache.org/jira/browse/CXF-7751
>
[jira] [Updated] (CXF-7751) Codegen plugin can't work with empty extraarg tag
[
https://issues.apache.org/jira/browse/CXF-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Pushkin updated CXF-7751:
Description:
I use cxf codegen plugin and i have separate maven profile to generate code by
wsdl. My problem in extraarg tag.
i have soap connectors, that have pom where is configuration of codegen plugin.
When project runnnig with generate code by wsdl profile ${wsdl.extraarg.keep}
equal "-keep." And that good work.
When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize and
in codegen in extraarg put emty string " ".
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
{code}
In result i have error.
Okey. I cheat and use that:
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
{code}
In result i have error for empty string arg.
[ERROR] Failed to execute goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java (generate-sources) on project
test-project: Execution generate-sources of goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java failed:
org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
argument:
was:
I use cxf codegen plugin and i have separate maven profile to generate code by
wsdl. My problem in extraarg tag.
i have soap connectors, that have pom where is configuration of codegen plugin.
When project runnnig with generate code by wsdl profile ${wsdl.extraarg.keep}
equal "-keep." And that good work.
When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize and
in codegen in extraarg put emty string " ".
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
{code}
In result i have error.
[ERROR] Failed to execute goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java (generate-sources) on project
test-project: Execution generate-sources of goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java failed:
org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
argument:
> Codegen plugin can't work with empty extraarg tag
> -
>
> Key: CXF-7751
> URL: https://issues.apache.org/jira/browse/CXF-7751
> Project: CXF
> Issue Type: Bug
> Components: Build system
>Affects Versions: 3.1.6, 3.2.4
>Reporter: Sergey Pushkin
>Priority: Critical
>
>
> I use cxf codegen plugin and i have separate maven profile to generate code
> by wsdl. My problem in extraarg tag.
> i have soap connectors, that have pom where is configuration of codegen
> plugin. When project runnnig with generate code by wsdl profile
> ${wsdl.extraarg.keep} equal "-keep." And that good work.
> When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize
> and in codegen in extraarg put emty string " ".
> {code:java}
>
> org.apache.cxf
> cxf-codegen-plugin
> 3.1.6
>
>
> generate-sources
> generate-sources
>
> src/main/java
>
>
>
> ../wsdl//ReferenceDataService.wsdl
>
>
> ${wsdl.extraarg.keep}
>
>
>
>
[jira] [Updated] (CXF-7751) Codegen plugin can't work with empty extraarg tag
[
https://issues.apache.org/jira/browse/CXF-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Pushkin updated CXF-7751:
Summary: Codegen plugin can't work with empty extraarg tag (was: Codegen
plugin can't work with empty extraarg)
> Codegen plugin can't work with empty extraarg tag
> -
>
> Key: CXF-7751
> URL: https://issues.apache.org/jira/browse/CXF-7751
> Project: CXF
> Issue Type: Bug
> Components: Build system
>Affects Versions: 3.1.6, 3.2.4
>Reporter: Sergey Pushkin
>Priority: Critical
>
>
> I use cxf codegen plugin and i have separate maven profile to generate code
> by wsdl. My problem in extraarg tag.
> i have soap connectors, that have pom where is configuration of codegen
> plugin. When project runnnig with generate code by wsdl profile
> ${wsdl.extraarg.keep} equal "-keep." And that good work.
> When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize
> and in codegen in extraarg put emty string " ".
> {code:java}
>
> org.apache.cxf
> cxf-codegen-plugin
> 3.1.6
>
>
> generate-sources
> generate-sources
>
> src/main/java
>
>
>
> ../wsdl//ReferenceDataService.wsdl
>
>
> ${wsdl.extraarg.keep}
>
>
>
> UTF-8
>
>
> wsdl2java
>
>
>
>
> {code}
> In result i have error.
> [ERROR] Failed to execute goal
> org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java (generate-sources) on
> project test-project: Execution generate-sources of goal
> org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java failed:
> org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
> argument:
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CXF-7751) Codegen plugin can't work with empty extraarg
[
https://issues.apache.org/jira/browse/CXF-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Pushkin updated CXF-7751:
Summary: Codegen plugin can't work with empty extraarg (was: Codegen
plugin can't read empty extraarg)
> Codegen plugin can't work with empty extraarg
> -
>
> Key: CXF-7751
> URL: https://issues.apache.org/jira/browse/CXF-7751
> Project: CXF
> Issue Type: Bug
> Components: Build system
>Affects Versions: 3.1.6, 3.2.4
>Reporter: Sergey Pushkin
>Priority: Critical
>
>
> I use cxf codegen plugin and i have separate maven profile to generate code
> by wsdl. My problem in extraarg tag.
> i have soap connectors, that have pom where is configuration of codegen
> plugin. When project runnnig with generate code by wsdl profile
> ${wsdl.extraarg.keep} equal "-keep." And that good work.
> When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize
> and in codegen in extraarg put emty string " ".
> {code:java}
>
> org.apache.cxf
> cxf-codegen-plugin
> 3.1.6
>
>
> generate-sources
> generate-sources
>
> src/main/java
>
>
>
> ../wsdl//ReferenceDataService.wsdl
>
>
> ${wsdl.extraarg.keep}
>
>
>
> UTF-8
>
>
> wsdl2java
>
>
>
>
> {code}
> In result i have error.
> [ERROR] Failed to execute goal
> org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java (generate-sources) on
> project test-project: Execution generate-sources of goal
> org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java failed:
> org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
> argument:
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CXF-7751) Codegen plugin can't read empty extraarg
[
https://issues.apache.org/jira/browse/CXF-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Pushkin updated CXF-7751:
Description:
I use cxf codegen plugin and i have separate maven profile to generate code by
wsdl. My problem in extraarg tag.
i have soap connectors, that have pom where is configuration of codegen plugin.
When project runnnig with generate code by wsdl profile ${wsdl.extraarg.keep}
equal "-keep." And that good work.
When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize and
in codegen in extraarg put emty string " ".
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
{code}
In result i have error.
[ERROR] Failed to execute goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java (generate-sources) on project
test-project: Execution generate-sources of goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java failed:
org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
argument:
was:
I use cxf codegen plugin and i have separate maven profile to generate code by
wsdl. My problem in extraarg tag.
i have soap connectors, that have pom where is configuration of codegen plugin.
When project runnnig with generate code by wsdl profile ${wsdl.extraarg.keep}
equal "-keep." And that good work.
When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize and
in codegen in extraarg put emty string " ".
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
{code}
[ERROR] Failed to execute goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java (generate-sources) on project
test-project: Execution generate-sources of goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java failed:
org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
argument:
> Codegen plugin can't read empty extraarg
>
>
> Key: CXF-7751
> URL: https://issues.apache.org/jira/browse/CXF-7751
> Project: CXF
> Issue Type: Bug
> Components: Build system
>Affects Versions: 3.1.6, 3.2.4
>Reporter: Sergey Pushkin
>Priority: Critical
>
>
> I use cxf codegen plugin and i have separate maven profile to generate code
> by wsdl. My problem in extraarg tag.
> i have soap connectors, that have pom where is configuration of codegen
> plugin. When project runnnig with generate code by wsdl profile
> ${wsdl.extraarg.keep} equal "-keep." And that good work.
> When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize
> and in codegen in extraarg put emty string " ".
> {code:java}
>
> org.apache.cxf
> cxf-codegen-plugin
> 3.1.6
>
>
> generate-sources
> generate-sources
>
> src/main/java
>
>
>
> ../wsdl//ReferenceDataService.wsdl
>
>
> ${wsdl.extraarg.keep}
>
>
>
> UTF-8
>
>
> wsdl2java
>
>
>
>
> {code}
> In result i have error.
> [ERROR] Failed to execute goal
> org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java (generate-sources) on
> project test-project: Execution generate-sources of goal
> org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java failed:
> org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
> argument:
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CXF-7751) Codegen plugin can't read empty extraarg
Sergey Pushkin created CXF-7751:
---
Summary: Codegen plugin can't read empty extraarg
Key: CXF-7751
URL: https://issues.apache.org/jira/browse/CXF-7751
Project: CXF
Issue Type: Bug
Components: Build system
Affects Versions: 3.2.4, 3.1.6
Reporter: Sergey Pushkin
I use cxf codegen plugin and i have separate maven profile to generate code by
wsdl. My problem in extraarg tag.
i have soap connectors, that have pom where is configuration of codegen plugin.
When project runnnig with generate code by wsdl profile ${wsdl.extraarg.keep}
equal "-keep." And that good work.
When runnig another maven profile my ${wsdl.extraarg.keep} don't initialize and
in codegen in extraarg put emty string " ".
{code:java}
org.apache.cxf
cxf-codegen-plugin
3.1.6
generate-sources
generate-sources
src/main/java
../wsdl//ReferenceDataService.wsdl
${wsdl.extraarg.keep}
UTF-8
wsdl2java
{code}
[ERROR] Failed to execute goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java (generate-sources) on project
test-project: Execution generate-sources of goal
org.apache.cxf:cxf-codegen-plugin:3.2.4:wsdl2java failed:
org.apache.cxf.tools.common.toolspec.parser.BadUsageException: Unexpected
argument:
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CXF-7750) cxf parent pom should have dependencyManagement entries for cxf artifacts
[ https://issues.apache.org/jira/browse/CXF-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7750: - Assignee: Freeman Fang > cxf parent pom should have dependencyManagement entries for cxf artifacts > - > > Key: CXF-7750 > URL: https://issues.apache.org/jira/browse/CXF-7750 > Project: CXF > Issue Type: Improvement > Components: Samples >Reporter: Tom Cunningham >Assignee: Freeman Fang >Priority: Major > > The cxf parent pom should have dependencyManagement entries for all of the > cxf artifacts. Other projects like camel > ([https://github.com/apache/camel/blob/18a110cc4e78968b623564fe02484d54af7f906f/parent/pom.xml)] > include these so that the parent pom can be imported like a BOM and provide > standard versions of all the artifacts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CXF-7750) cxf parent pom should have dependencyManagement entries for cxf artifacts
[ https://issues.apache.org/jira/browse/CXF-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16497932#comment-16497932 ] ASF GitHub Bot commented on CXF-7750: - cunningt opened a new pull request #421: CXF-7750 CXF parent pom should have dependencyManagement entries for cxf artifacts URL: https://github.com/apache/cxf/pull/421 https://issues.apache.org/jira/browse/CXF-7750 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > cxf parent pom should have dependencyManagement entries for cxf artifacts > - > > Key: CXF-7750 > URL: https://issues.apache.org/jira/browse/CXF-7750 > Project: CXF > Issue Type: Improvement > Components: Samples >Reporter: Tom Cunningham >Priority: Major > > The cxf parent pom should have dependencyManagement entries for all of the > cxf artifacts. Other projects like camel > ([https://github.com/apache/camel/blob/18a110cc4e78968b623564fe02484d54af7f906f/parent/pom.xml)] > include these so that the parent pom can be imported like a BOM and provide > standard versions of all the artifacts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CXF-7750) cxf parent pom should have dependencyManagement entries for cxf artifacts
Tom Cunningham created CXF-7750: --- Summary: cxf parent pom should have dependencyManagement entries for cxf artifacts Key: CXF-7750 URL: https://issues.apache.org/jira/browse/CXF-7750 Project: CXF Issue Type: Improvement Components: Samples Reporter: Tom Cunningham The cxf parent pom should have dependencyManagement entries for all of the cxf artifacts. Other projects like camel ([https://github.com/apache/camel/blob/18a110cc4e78968b623564fe02484d54af7f906f/parent/pom.xml)] include these so that the parent pom can be imported like a BOM and provide standard versions of all the artifacts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CXF-7747) FileUtils.maybeDeleteDefaultTempDir causes an IllegalStateException if it tries to remove the shutdown hook while the JVM is already shutting down
[ https://issues.apache.org/jira/browse/CXF-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CXF-7747. -- Resolution: Fixed > FileUtils.maybeDeleteDefaultTempDir causes an IllegalStateException if it > tries to remove the shutdown hook while the JVM is already shutting down > -- > > Key: CXF-7747 > URL: https://issues.apache.org/jira/browse/CXF-7747 > Project: CXF > Issue Type: Bug >Affects Versions: 3.2.4 > Environment: Java: jdk1.8.0_144 > Spring-boot: 1.4.1 > CXF: 2.1.4 > Jetty: 9.3.11.v20160721 > Operating system: Windows 7 >Reporter: George Jiang >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 3.1.16, 3.2.5 > > > I have seen this error in Jetty after a failsafe junit validation test suite > finishes. > 2018-05-23T13:58:07,188 +147913 [Thread-28] WARN > org.eclipse.jetty.servlet.ServletHolder - []: > java.lang.IllegalStateException: Shutdown in progress > at > java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) > ~[?:1.8.0_144] > at java.lang.Runtime.removeShutdownHook(Runtime.java:239) ~[?:1.8.0_144] > at > org.apache.cxf.helpers.FileUtils.maybeDeleteDefaultTempDir(FileUtils.java:122) > ~[cxf-core-3.1.14.jar:3.1.14] > at > org.apache.cxf.transport.servlet.AbstractHTTPServlet.destroy(AbstractHTTPServlet.java:128) > ~[cxf-rt-transports-http-3.1.14.jar:3.1.14] > at > org.apache.cxf.transport.servlet.CXFNonSpringServlet.destroy(CXFNonSpringServlet.java:214) > ~[cxf-rt-transports-http-3.1.14.jar:3.1.14] > at > org.eclipse.jetty.servlet.ServletHolder.destroyInstance(ServletHolder.java:475) > ~[jetty-servlet-9.3.11.v20160721.jar:9.3.11.v20160721] > at org.eclipse.jetty.servlet.ServletHolder.doStop(ServletHolder.java:446) > [jetty-servlet-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.servlet.ServletHandler.doStop(ServletHandler.java:281) > [jetty-servlet-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.security.SecurityHandler.doStop(SecurityHandler.java:381) > [jetty-security-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.security.ConstraintSecurityHandler.doStop(ConstraintSecurityHandler.java:456) > [jetty-security-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.session.SessionHandler.doStop(SessionHandler.java:127) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.handler.ContextHandler.stopContext(ContextHandler.java:825) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.servlet.ServletContextHandler.stopContext(ServletContextHandler.java:356) >
[jira] [Created] (CXF-7749) OpenApi 3.0: Enable restriction of swagger definitions per CXF endpoint (based on the path)
Bharanidharan Viswanathan created CXF-7749:
--
Summary: OpenApi 3.0: Enable restriction of swagger definitions
per CXF endpoint (based on the path)
Key: CXF-7749
URL: https://issues.apache.org/jira/browse/CXF-7749
Project: CXF
Issue Type: New Feature
Reporter: Bharanidharan Viswanathan
h3: What
OpenApi 3.0 - enable restricting swagger definitions per CXF endpoint (based on
the path)! For example, if there would two CXF endpoints ("/admin" & "/public")
& then on each of them, only the specific swagger definitions should be visible.
[~reta] FYI.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CXF-7748) WS-Addressing for One Way + Signature fails
Joerg Kessler created CXF-7748:
--
Summary: WS-Addressing for One Way + Signature fails
Key: CXF-7748
URL: https://issues.apache.org/jira/browse/CXF-7748
Project: CXF
Issue Type: Bug
Components: WS-* Components
Affects Versions: 3.1.14
Reporter: Joerg Kessler
I am using CXF together in Apache Camel. I want to enable WS-Adressing for the
provider including signing these headers by WS-Security if requested . This
should especially work for One Way requests. When I set up this scenario
(Camel-CXF to Camel-CXF including Signature) I get the error
org.apache.cxf.interceptor.Fault: No configured signature username detected
The call stack is
2018 06 01
06:57:37#+00#WARN#org.apache.cxf.phase.PhaseInterceptorChain##P1369096596#http-bio-8041-exec-5#na#wda71513f#jkt01ifl#web#w7e2e2211#na#na#na#na#Interceptor
for
\{http://xi.com/xiveri/source_runtime}JKCXF_TEST_IN\#\{http://xi.com/xiveri/source_runtime}JKCXF_TEST_IN
has thrown exception, unwinding noworg.apache.cxf.interceptor.Fault: No
configured signature username detected at
org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.doSignBeforeEncrypt(AsymmetricBindingHandler.java:232)
at
org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.handleBinding(AsymmetricBindingHandler.java:114)
at
org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessageInternal(PolicyBasedWSS4JOutInterceptor.java:190)
at
org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:109)
at
org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:96)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at
org.apache.cxf.ws.addressing.impl.InternalContextUtils.rebaseResponse(InternalContextUtils.java:280)
at
org.apache.cxf.ws.addressing.impl.MAPAggregatorImpl.mediate(MAPAggregatorImpl.java:469)
at
org.apache.cxf.ws.addressing.impl.MAPAggregatorImpl.handleMessage(MAPAggregatorImpl.java:142)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)
at
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:189)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:303)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:222)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:755) at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:278)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
com.sap.esb.security.cloud.authentication.CloudAuthenticationFilter.doFilter(CloudAuthenticationFilter.java:92)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
com.sap.core.communication.server.CertValidatorFilter.doFilter(CertValidatorFilter.java:331)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110)
at
org.eclipse.virgo.web.enterprise.security.valve.OpenEjbSecurityInitializationValve.invoke(OpenEjbSecurityInitializationValve.java:44)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:498)
at
com.sap.core.jpaas.security.auth.service.lib.AbstractAuthenticator.invoke(AbstractAuthenticator.java:170)
at
[jira] [Updated] (CXF-7747) FileUtils.maybeDeleteDefaultTempDir causes an IllegalStateException if it tries to remove the shutdown hook while the JVM is already shutting down
[ https://issues.apache.org/jira/browse/CXF-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CXF-7747: - Fix Version/s: 3.2.5 3.1.16 > FileUtils.maybeDeleteDefaultTempDir causes an IllegalStateException if it > tries to remove the shutdown hook while the JVM is already shutting down > -- > > Key: CXF-7747 > URL: https://issues.apache.org/jira/browse/CXF-7747 > Project: CXF > Issue Type: Bug >Affects Versions: 3.2.4 > Environment: Java: jdk1.8.0_144 > Spring-boot: 1.4.1 > CXF: 2.1.4 > Jetty: 9.3.11.v20160721 > Operating system: Windows 7 >Reporter: George Jiang >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 3.1.16, 3.2.5 > > > I have seen this error in Jetty after a failsafe junit validation test suite > finishes. > 2018-05-23T13:58:07,188 +147913 [Thread-28] WARN > org.eclipse.jetty.servlet.ServletHolder - []: > java.lang.IllegalStateException: Shutdown in progress > at > java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) > ~[?:1.8.0_144] > at java.lang.Runtime.removeShutdownHook(Runtime.java:239) ~[?:1.8.0_144] > at > org.apache.cxf.helpers.FileUtils.maybeDeleteDefaultTempDir(FileUtils.java:122) > ~[cxf-core-3.1.14.jar:3.1.14] > at > org.apache.cxf.transport.servlet.AbstractHTTPServlet.destroy(AbstractHTTPServlet.java:128) > ~[cxf-rt-transports-http-3.1.14.jar:3.1.14] > at > org.apache.cxf.transport.servlet.CXFNonSpringServlet.destroy(CXFNonSpringServlet.java:214) > ~[cxf-rt-transports-http-3.1.14.jar:3.1.14] > at > org.eclipse.jetty.servlet.ServletHolder.destroyInstance(ServletHolder.java:475) > ~[jetty-servlet-9.3.11.v20160721.jar:9.3.11.v20160721] > at org.eclipse.jetty.servlet.ServletHolder.doStop(ServletHolder.java:446) > [jetty-servlet-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.servlet.ServletHandler.doStop(ServletHandler.java:281) > [jetty-servlet-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.security.SecurityHandler.doStop(SecurityHandler.java:381) > [jetty-security-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.security.ConstraintSecurityHandler.doStop(ConstraintSecurityHandler.java:456) > [jetty-security-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.session.SessionHandler.doStop(SessionHandler.java:127) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.handler.ContextHandler.stopContext(ContextHandler.java:825) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.servlet.ServletContextHandler.stopContext(ServletContextHandler.java:356) >
[jira] [Assigned] (CXF-7747) FileUtils.maybeDeleteDefaultTempDir causes an IllegalStateException if it tries to remove the shutdown hook while the JVM is already shutting down
[ https://issues.apache.org/jira/browse/CXF-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned CXF-7747: Assignee: Colm O hEigeartaigh > FileUtils.maybeDeleteDefaultTempDir causes an IllegalStateException if it > tries to remove the shutdown hook while the JVM is already shutting down > -- > > Key: CXF-7747 > URL: https://issues.apache.org/jira/browse/CXF-7747 > Project: CXF > Issue Type: Bug >Affects Versions: 3.2.4 > Environment: Java: jdk1.8.0_144 > Spring-boot: 1.4.1 > CXF: 2.1.4 > Jetty: 9.3.11.v20160721 > Operating system: Windows 7 >Reporter: George Jiang >Assignee: Colm O hEigeartaigh >Priority: Minor > > I have seen this error in Jetty after a failsafe junit validation test suite > finishes. > 2018-05-23T13:58:07,188 +147913 [Thread-28] WARN > org.eclipse.jetty.servlet.ServletHolder - []: > java.lang.IllegalStateException: Shutdown in progress > at > java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) > ~[?:1.8.0_144] > at java.lang.Runtime.removeShutdownHook(Runtime.java:239) ~[?:1.8.0_144] > at > org.apache.cxf.helpers.FileUtils.maybeDeleteDefaultTempDir(FileUtils.java:122) > ~[cxf-core-3.1.14.jar:3.1.14] > at > org.apache.cxf.transport.servlet.AbstractHTTPServlet.destroy(AbstractHTTPServlet.java:128) > ~[cxf-rt-transports-http-3.1.14.jar:3.1.14] > at > org.apache.cxf.transport.servlet.CXFNonSpringServlet.destroy(CXFNonSpringServlet.java:214) > ~[cxf-rt-transports-http-3.1.14.jar:3.1.14] > at > org.eclipse.jetty.servlet.ServletHolder.destroyInstance(ServletHolder.java:475) > ~[jetty-servlet-9.3.11.v20160721.jar:9.3.11.v20160721] > at org.eclipse.jetty.servlet.ServletHolder.doStop(ServletHolder.java:446) > [jetty-servlet-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.servlet.ServletHandler.doStop(ServletHandler.java:281) > [jetty-servlet-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.security.SecurityHandler.doStop(SecurityHandler.java:381) > [jetty-security-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.security.ConstraintSecurityHandler.doStop(ConstraintSecurityHandler.java:456) > [jetty-security-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.session.SessionHandler.doStop(SessionHandler.java:127) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.handler.ContextHandler.stopContext(ContextHandler.java:825) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.servlet.ServletContextHandler.stopContext(ServletContextHandler.java:356) > [jetty-servlet-9.3.11.v20160721.jar:9.3.11.v20160721]
[jira] [Commented] (CXF-7747) FileUtils.maybeDeleteDefaultTempDir causes an IllegalStateException if it tries to remove the shutdown hook while the JVM is already shutting down
[ https://issues.apache.org/jira/browse/CXF-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16497651#comment-16497651 ] George Jiang commented on CXF-7747: --- I have already tried it. This problem still exists. > FileUtils.maybeDeleteDefaultTempDir causes an IllegalStateException if it > tries to remove the shutdown hook while the JVM is already shutting down > -- > > Key: CXF-7747 > URL: https://issues.apache.org/jira/browse/CXF-7747 > Project: CXF > Issue Type: Bug >Affects Versions: 3.2.4 > Environment: Java: jdk1.8.0_144 > Spring-boot: 1.4.1 > CXF: 2.1.4 > Jetty: 9.3.11.v20160721 > Operating system: Windows 7 >Reporter: George Jiang >Priority: Minor > > I have seen this error in Jetty after a failsafe junit validation test suite > finishes. > 2018-05-23T13:58:07,188 +147913 [Thread-28] WARN > org.eclipse.jetty.servlet.ServletHolder - []: > java.lang.IllegalStateException: Shutdown in progress > at > java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) > ~[?:1.8.0_144] > at java.lang.Runtime.removeShutdownHook(Runtime.java:239) ~[?:1.8.0_144] > at > org.apache.cxf.helpers.FileUtils.maybeDeleteDefaultTempDir(FileUtils.java:122) > ~[cxf-core-3.1.14.jar:3.1.14] > at > org.apache.cxf.transport.servlet.AbstractHTTPServlet.destroy(AbstractHTTPServlet.java:128) > ~[cxf-rt-transports-http-3.1.14.jar:3.1.14] > at > org.apache.cxf.transport.servlet.CXFNonSpringServlet.destroy(CXFNonSpringServlet.java:214) > ~[cxf-rt-transports-http-3.1.14.jar:3.1.14] > at > org.eclipse.jetty.servlet.ServletHolder.destroyInstance(ServletHolder.java:475) > ~[jetty-servlet-9.3.11.v20160721.jar:9.3.11.v20160721] > at org.eclipse.jetty.servlet.ServletHolder.doStop(ServletHolder.java:446) > [jetty-servlet-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.servlet.ServletHandler.doStop(ServletHandler.java:281) > [jetty-servlet-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.security.SecurityHandler.doStop(SecurityHandler.java:381) > [jetty-security-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.security.ConstraintSecurityHandler.doStop(ConstraintSecurityHandler.java:456) > [jetty-security-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.session.SessionHandler.doStop(SessionHandler.java:127) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161) > [jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.server.handler.ContextHandler.stopContext(ContextHandler.java:825) > [jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721] > at > org.eclipse.jetty.servlet.ServletContextHandler.stopContext(ServletContextHandler.java:356) > [jetty-servlet-9.3.11.v20160721.jar:9.3.11.v20160721] >
