[jira] [Commented] (CXF-8694) CXF 3.5.0 Generated WSDL root element
[
https://issues.apache.org/jira/browse/CXF-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524719#comment-17524719
]
Vincent commented on CXF-8694:
--
Hi,
I attached the wsdl and the external xsd.
Thank you for your help
> CXF 3.5.0 Generated WSDL root element
> -
>
> Key: CXF-8694
> URL: https://issues.apache.org/jira/browse/CXF-8694
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Vincent
>Priority: Major
> Attachments: mobileCatalog.wsdl, mobileCatalog.xsd
>
>
> Hi,
> I'm migrating an existing soap service from 3.1.5 version to 3.5.0.
> The wsdl contains the following information :
>
> {code:java}
>
>
>
>
> ...
>
>
>
> ...
>
>element="nsmp:getMobileProductsRequest"/>
>
> ...
>
> ...
>
>name="getMobileProductsRequest">
>name="getMobileProductsResponse">
>
>
>
> ...
>
> {code}
> When I look the generated wsdl, cxf add a root element *getMobileProducts*
> above *getMobileProductsRequest* :
>
> {code:java}
>
>
>
>
>
>
>
>
> type="tns:PtMobileCatalogPortType">
> transport="http://schemas.xmlsoap.org/soap/http"/>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Do you know how can we fix it because we have another backend that call our
> webservice and we cannot change the original wsdl?
>
> Thank you for your help
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CXF-8694) CXF 3.5.0 Generated WSDL root element
[
https://issues.apache.org/jira/browse/CXF-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent updated CXF-8694:
-
Attachment: mobileCatalog.xsd
> CXF 3.5.0 Generated WSDL root element
> -
>
> Key: CXF-8694
> URL: https://issues.apache.org/jira/browse/CXF-8694
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Vincent
>Priority: Major
> Attachments: mobileCatalog.wsdl, mobileCatalog.xsd
>
>
> Hi,
> I'm migrating an existing soap service from 3.1.5 version to 3.5.0.
> The wsdl contains the following information :
>
> {code:java}
>
>
>
>
> ...
>
>
>
> ...
>
>element="nsmp:getMobileProductsRequest"/>
>
> ...
>
> ...
>
>name="getMobileProductsRequest">
>name="getMobileProductsResponse">
>
>
>
> ...
>
> {code}
> When I look the generated wsdl, cxf add a root element *getMobileProducts*
> above *getMobileProductsRequest* :
>
> {code:java}
>
>
>
>
>
>
>
>
> type="tns:PtMobileCatalogPortType">
> transport="http://schemas.xmlsoap.org/soap/http"/>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Do you know how can we fix it because we have another backend that call our
> webservice and we cannot change the original wsdl?
>
> Thank you for your help
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (CXF-8694) CXF 3.5.0 Generated WSDL root element
[
https://issues.apache.org/jira/browse/CXF-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent updated CXF-8694:
-
Attachment: mobileCatalog.wsdl
> CXF 3.5.0 Generated WSDL root element
> -
>
> Key: CXF-8694
> URL: https://issues.apache.org/jira/browse/CXF-8694
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Vincent
>Priority: Major
> Attachments: mobileCatalog.wsdl, mobileCatalog.xsd
>
>
> Hi,
> I'm migrating an existing soap service from 3.1.5 version to 3.5.0.
> The wsdl contains the following information :
>
> {code:java}
>
>
>
>
> ...
>
>
>
> ...
>
>element="nsmp:getMobileProductsRequest"/>
>
> ...
>
> ...
>
>name="getMobileProductsRequest">
>name="getMobileProductsResponse">
>
>
>
> ...
>
> {code}
> When I look the generated wsdl, cxf add a root element *getMobileProducts*
> above *getMobileProductsRequest* :
>
> {code:java}
>
>
>
>
>
>
>
>
> type="tns:PtMobileCatalogPortType">
> transport="http://schemas.xmlsoap.org/soap/http"/>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Do you know how can we fix it because we have another backend that call our
> webservice and we cannot change the original wsdl?
>
> Thank you for your help
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (CXF-8685) cannot access https in swagger UI with OpenApiFeature
[
https://issues.apache.org/jira/browse/CXF-8685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524641#comment-17524641
]
Andriy Redko commented on CXF-8685:
---
Thanks [~letrth...@gmail.com], this is weird, may I ask you please to share
minimal reproducer project? Thank you.
> cannot access https in swagger UI with OpenApiFeature
> -
>
> Key: CXF-8685
> URL: https://issues.apache.org/jira/browse/CXF-8685
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS, Services
>Affects Versions: 3.3.13
>Reporter: Thang Le
>Priority: Critical
> Labels: OpenApiFeature, openapi
>
> In CXF {*}OpenApiFeature
> ({*}https://cxf.apache.org/docs/openapifeature.html). We need to allow to set
> server to '/' to fix https cannot set in Swagger UI.
>
> Reference issue:
> [https://github.com/springdoc/springdoc-openapi/issues/726]
> https://stackoverflow.com/questions/70843940/springdoc-openapi-ui-how-do-i-set-the-request-to-https
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (CXF-8694) CXF 3.5.0 Generated WSDL root element
[
https://issues.apache.org/jira/browse/CXF-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524635#comment-17524635
]
Andriy Redko edited comment on CXF-8694 at 4/20/22 12:22 AM:
-
Thanks [~vincent.broucke] , with the information I have I was not able to
reproduce the issue, I don't see this type:
May I ask you please to share the minimal reproducer project?
Thank you.
was (Author: reta):
Thanks [~vincent.broucke] , with the information I have I was not able to
reproduce the issue, I don't see this type.
May I ask you please to share the minimal reproducer project?
Thank you.
> CXF 3.5.0 Generated WSDL root element
> -
>
> Key: CXF-8694
> URL: https://issues.apache.org/jira/browse/CXF-8694
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Vincent
>Priority: Major
>
> Hi,
> I'm migrating an existing soap service from 3.1.5 version to 3.5.0.
> The wsdl contains the following information :
>
> {code:java}
>
>
>
>
> ...
>
>
>
> ...
>
>element="nsmp:getMobileProductsRequest"/>
>
> ...
>
> ...
>
>name="getMobileProductsRequest">
>name="getMobileProductsResponse">
>
>
>
> ...
>
> {code}
> When I look the generated wsdl, cxf add a root element *getMobileProducts*
> above *getMobileProductsRequest* :
>
> {code:java}
>
>
>
>
>
>
>
>
> type="tns:PtMobileCatalogPortType">
> transport="http://schemas.xmlsoap.org/soap/http"/>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Do you know how can we fix it because we have another backend that call our
> webservice and we cannot change the original wsdl?
>
> Thank you for your help
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (CXF-8694) CXF 3.5.0 Generated WSDL root element
[
https://issues.apache.org/jira/browse/CXF-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524635#comment-17524635
]
Andriy Redko commented on CXF-8694:
---
Thanks [~vincent.broucke] , with the information I have I was not able to
reproduce the issue, I don't see this type.
May I ask you please to share the minimal reproducer project?
Thank you.
> CXF 3.5.0 Generated WSDL root element
> -
>
> Key: CXF-8694
> URL: https://issues.apache.org/jira/browse/CXF-8694
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Vincent
>Priority: Major
>
> Hi,
> I'm migrating an existing soap service from 3.1.5 version to 3.5.0.
> The wsdl contains the following information :
>
> {code:java}
>
>
>
>
> ...
>
>
>
> ...
>
>element="nsmp:getMobileProductsRequest"/>
>
> ...
>
> ...
>
>name="getMobileProductsRequest">
>name="getMobileProductsResponse">
>
>
>
> ...
>
> {code}
> When I look the generated wsdl, cxf add a root element *getMobileProducts*
> above *getMobileProductsRequest* :
>
> {code:java}
>
>
>
>
>
>
>
>
> type="tns:PtMobileCatalogPortType">
> transport="http://schemas.xmlsoap.org/soap/http"/>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Do you know how can we fix it because we have another backend that call our
> webservice and we cannot change the original wsdl?
>
> Thank you for your help
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (CXF-8694) CXF 3.5.0 Generated WSDL root element
[
https://issues.apache.org/jira/browse/CXF-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524567#comment-17524567
]
Vincent Broucke commented on CXF-8694:
--
Hi, Andriy, I generated my classes from WSDL using apache cxf-codegen-plugin
and here is the small snippet of my service :
{code:java}
@WebService(targetNamespace = "http://mobilecatalog.esb.voo.be";, name =
"ptMobileCatalog")
@XmlSeeAlso({ObjectFactory.class})
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
public interface PtMobileCatalog {
@WebMethod(action = "getMobileProducts")
@WebResult(name = "getMobileProductsResponse", targetNamespace =
"http://mobilecatalog.esb.voo.be";, partName = "getMobileProductsResponse")
public GetMobileProductsResponse getMobileProducts(
@WebParam(partName = "getMobileProductsRequest", name =
"getMobileProductsRequest", targetNamespace = "http://mobilecatalog.esb.voo.be";)
GetMobileProductsRequest getMobileProductsRequest
) throws MsgFault;
...
} {code}
Thank you for your help
> CXF 3.5.0 Generated WSDL root element
> -
>
> Key: CXF-8694
> URL: https://issues.apache.org/jira/browse/CXF-8694
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Vincent
>Priority: Major
>
> Hi,
> I'm migrating an existing soap service from 3.1.5 version to 3.5.0.
> The wsdl contains the following information :
>
> {code:java}
>
>
>
>
> ...
>
>
>
> ...
>
>element="nsmp:getMobileProductsRequest"/>
>
> ...
>
> ...
>
>name="getMobileProductsRequest">
>name="getMobileProductsResponse">
>
>
>
> ...
>
> {code}
> When I look the generated wsdl, cxf add a root element *getMobileProducts*
> above *getMobileProductsRequest* :
>
> {code:java}
>
>
>
>
>
>
>
>
> type="tns:PtMobileCatalogPortType">
> transport="http://schemas.xmlsoap.org/soap/http"/>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Do you know how can we fix it because we have another backend that call our
> webservice and we cannot change the original wsdl?
>
> Thank you for your help
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (CXF-8579) Upgrade wss4j to v3.0.0 and OpenSAML to 4.x
[
https://issues.apache.org/jira/browse/CXF-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved CXF-8579.
--
Resolution: Fixed
> Upgrade wss4j to v3.0.0 and OpenSAML to 4.x
> ---
>
> Key: CXF-8579
> URL: https://issues.apache.org/jira/browse/CXF-8579
> Project: CXF
> Issue Type: Task
> Components: STS, WS-* Components
>Affects Versions: 3.5.0
>Reporter: Misagh Moayyed
>Assignee: Colm O hEigeartaigh
>Priority: Minor
> Fix For: 4.0.0
>
>
> The next release of wss4j has switched to support OpenSAML v4. This release
> as of this writing is in SNAPSHOT mode. When testing wss4j against CXF, it
> turns out that SAMLTokenProvider is not compatible with the latest wss4j and
> opensaml v4, mainly due to the following:
>
> {code:java}
> DateTime validFrom = null;
> DateTime validTill = null;
> if (assertion.getSamlVersion().equals(SAMLVersion.VERSION_20)) {
> validFrom = assertion.getSaml2().getConditions().getNotBefore();
> validTill = assertion.getSaml2().getConditions().getNotOnOrAfter();
> } else {
> validFrom = assertion.getSaml1().getConditions().getNotBefore();
> validTill = assertion.getSaml1().getConditions().getNotOnOrAfter();
> }
> {code}
> There may be other areas that require attention.
> This Jira focuses on upgrading wss4j to the next 2.5.x line, while making
> sure opensaml v4 continues to work correctly. If possible, it would be great
> to publish a SNAPSHOT version of CXF that contains an updated 2.5.0-SNAPSHOT
> version for wss4j, and allow the user community to test it.
>
> I can surely submit a patch or pull request that attempts to handle the
> upgrade on GH, etc.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CXF-8579) Upgrade wss4j to v3.0.0 and OpenSAML to 4.x
[
https://issues.apache.org/jira/browse/CXF-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated CXF-8579:
-
Summary: Upgrade wss4j to v3.0.0 and OpenSAML to 4.x (was: Upgrade wss4j
to v2.5.0 and OpenSAML to 4.x)
> Upgrade wss4j to v3.0.0 and OpenSAML to 4.x
> ---
>
> Key: CXF-8579
> URL: https://issues.apache.org/jira/browse/CXF-8579
> Project: CXF
> Issue Type: Task
> Components: STS, WS-* Components
>Affects Versions: 3.5.0
>Reporter: Misagh Moayyed
>Assignee: Colm O hEigeartaigh
>Priority: Minor
> Fix For: 4.0.0
>
>
> The next release of wss4j has switched to support OpenSAML v4. This release
> as of this writing is in SNAPSHOT mode. When testing wss4j against CXF, it
> turns out that SAMLTokenProvider is not compatible with the latest wss4j and
> opensaml v4, mainly due to the following:
>
> {code:java}
> DateTime validFrom = null;
> DateTime validTill = null;
> if (assertion.getSamlVersion().equals(SAMLVersion.VERSION_20)) {
> validFrom = assertion.getSaml2().getConditions().getNotBefore();
> validTill = assertion.getSaml2().getConditions().getNotOnOrAfter();
> } else {
> validFrom = assertion.getSaml1().getConditions().getNotBefore();
> validTill = assertion.getSaml1().getConditions().getNotOnOrAfter();
> }
> {code}
> There may be other areas that require attention.
> This Jira focuses on upgrading wss4j to the next 2.5.x line, while making
> sure opensaml v4 continues to work correctly. If possible, it would be great
> to publish a SNAPSHOT version of CXF that contains an updated 2.5.0-SNAPSHOT
> version for wss4j, and allow the user community to test it.
>
> I can surely submit a patch or pull request that attempts to handle the
> upgrade on GH, etc.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (CXF-8579) Upgrade wss4j to v2.5.0 and OpenSAML to 4.x
[
https://issues.apache.org/jira/browse/CXF-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated CXF-8579:
-
Fix Version/s: 4.0.0
> Upgrade wss4j to v2.5.0 and OpenSAML to 4.x
> ---
>
> Key: CXF-8579
> URL: https://issues.apache.org/jira/browse/CXF-8579
> Project: CXF
> Issue Type: Task
> Components: STS, WS-* Components
>Affects Versions: 3.5.0
>Reporter: Misagh Moayyed
>Priority: Minor
> Fix For: 4.0.0
>
>
> The next release of wss4j has switched to support OpenSAML v4. This release
> as of this writing is in SNAPSHOT mode. When testing wss4j against CXF, it
> turns out that SAMLTokenProvider is not compatible with the latest wss4j and
> opensaml v4, mainly due to the following:
>
> {code:java}
> DateTime validFrom = null;
> DateTime validTill = null;
> if (assertion.getSamlVersion().equals(SAMLVersion.VERSION_20)) {
> validFrom = assertion.getSaml2().getConditions().getNotBefore();
> validTill = assertion.getSaml2().getConditions().getNotOnOrAfter();
> } else {
> validFrom = assertion.getSaml1().getConditions().getNotBefore();
> validTill = assertion.getSaml1().getConditions().getNotOnOrAfter();
> }
> {code}
> There may be other areas that require attention.
> This Jira focuses on upgrading wss4j to the next 2.5.x line, while making
> sure opensaml v4 continues to work correctly. If possible, it would be great
> to publish a SNAPSHOT version of CXF that contains an updated 2.5.0-SNAPSHOT
> version for wss4j, and allow the user community to test it.
>
> I can surely submit a patch or pull request that attempts to handle the
> upgrade on GH, etc.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (CXF-8579) Upgrade wss4j to v2.5.0 and OpenSAML to 4.x
[
https://issues.apache.org/jira/browse/CXF-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh reassigned CXF-8579:
Assignee: Colm O hEigeartaigh
> Upgrade wss4j to v2.5.0 and OpenSAML to 4.x
> ---
>
> Key: CXF-8579
> URL: https://issues.apache.org/jira/browse/CXF-8579
> Project: CXF
> Issue Type: Task
> Components: STS, WS-* Components
>Affects Versions: 3.5.0
>Reporter: Misagh Moayyed
>Assignee: Colm O hEigeartaigh
>Priority: Minor
> Fix For: 4.0.0
>
>
> The next release of wss4j has switched to support OpenSAML v4. This release
> as of this writing is in SNAPSHOT mode. When testing wss4j against CXF, it
> turns out that SAMLTokenProvider is not compatible with the latest wss4j and
> opensaml v4, mainly due to the following:
>
> {code:java}
> DateTime validFrom = null;
> DateTime validTill = null;
> if (assertion.getSamlVersion().equals(SAMLVersion.VERSION_20)) {
> validFrom = assertion.getSaml2().getConditions().getNotBefore();
> validTill = assertion.getSaml2().getConditions().getNotOnOrAfter();
> } else {
> validFrom = assertion.getSaml1().getConditions().getNotBefore();
> validTill = assertion.getSaml1().getConditions().getNotOnOrAfter();
> }
> {code}
> There may be other areas that require attention.
> This Jira focuses on upgrading wss4j to the next 2.5.x line, while making
> sure opensaml v4 continues to work correctly. If possible, it would be great
> to publish a SNAPSHOT version of CXF that contains an updated 2.5.0-SNAPSHOT
> version for wss4j, and allow the user community to test it.
>
> I can surely submit a patch or pull request that attempts to handle the
> upgrade on GH, etc.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
