July 2016 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-4002) JBossWS SPI don't include the license file

by gil cattaneo (JIRA)

gil cattaneo created JBWS-4002: ---------------------------------- Summary: JBossWS SPI don't include the license file Key: JBWS-4002 URL: https://issues.jboss.org/browse/JBWS-4002 Project: JBoss Web Services Issue Type: Feature Request Reporter: gil cattaneo Not available LICENSE file in source directory structure Please. Added license and copyright notice. the fedora pakaging guideline is very strictly precise about this problem https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging... Thanks in advance Regards -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4001) JBossWS API don't include the license file

by gil cattaneo (JIRA)

gil cattaneo created JBWS-4001: ---------------------------------- Summary: JBossWS API don't include the license file Key: JBWS-4001 URL: https://issues.jboss.org/browse/JBWS-4001 Project: JBoss Web Services Issue Type: Feature Request Reporter: gil cattaneo Hi Not available LICENSE file in source directory structure Please. Added license and copyright notice. the fedora pakaging guideline is very strictly precise about this problem https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging... Thanks in advance Regards -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4000) Omit unnecessary external schemas in generated wsdl

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4000?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-4000: --------------------------------------- [~david.boeren], is it possible to see (privately is fine too) the code for WebPaymentInternal? > Omit unnecessary external schemas in generated wsdl > --------------------------------------------------- > > Key: JBWS-4000 > URL: https://issues.jboss.org/browse/JBWS-4000 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3.2 > Environment: JBoss EAP 6.4.x > Reporter: david.boeren > Priority: Minor > Attachments: CNP_2_2.java, EMIS_CNP_2_2_EAP-43.wsdl.xml, EMIS_CNP_2_2_EAP-64.wsdl.xml > > > We have a stateless EJB exposed as a SOAP Web Services endpoint on a EAP 4.3 working perfectly. We have now ported this to EAP 6.4 and noticed that the WSDL that it generates includes 3rd party schema definitions for some internal data elements that are not part of any of the Web Services method's input or output parameter. On EAP 4.3 we do not see such schema definitions for internal data elements included. Please see attached two WSDL files, also the source code for EJB. > What I can see is that the implementation of 4 WebMethods [beginWebPayment(), updateWebPayment(), getWebPayment() & cancelWebPayment()] makes a call to a private method convertRequest() that returns WebPaymentInternal which in turn contains a private member that is an instance of a EBay defined object. If I comment out these 4 methods then the resulting WSDL does not contain three EBay specific schema definitions, otherwise those three EBay specific schema definitions are included. What I do not understand why the WSDL need to expose internal data definitions when they are not part of any interface. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4000) Omit unnecessary external schemas in generated wsdl

by david.boeren (JIRA)

[ https://issues.jboss.org/browse/JBWS-4000?page=com.atlassian.jira.plugin.... ] david.boeren updated JBWS-4000: ------------------------------- Issue Type: Feature Request (was: Bug) > Omit unnecessary external schemas in generated wsdl > --------------------------------------------------- > > Key: JBWS-4000 > URL: https://issues.jboss.org/browse/JBWS-4000 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3.2 > Environment: JBoss EAP 6.4.x > Reporter: david.boeren > Priority: Minor > Attachments: CNP_2_2.java, EMIS_CNP_2_2_EAP-43.wsdl.xml, EMIS_CNP_2_2_EAP-64.wsdl.xml > > > We have a stateless EJB exposed as a SOAP Web Services endpoint on a EAP 4.3 working perfectly. We have now ported this to EAP 6.4 and noticed that the WSDL that it generates includes 3rd party schema definitions for some internal data elements that are not part of any of the Web Services method's input or output parameter. On EAP 4.3 we do not see such schema definitions for internal data elements included. Please see attached two WSDL files, also the source code for EJB. > What I can see is that the implementation of 4 WebMethods [beginWebPayment(), updateWebPayment(), getWebPayment() & cancelWebPayment()] makes a call to a private method convertRequest() that returns WebPaymentInternal which in turn contains a private member that is an instance of a EBay defined object. If I comment out these 4 methods then the resulting WSDL does not contain three EBay specific schema definitions, otherwise those three EBay specific schema definitions are included. What I do not understand why the WSDL need to expose internal data definitions when they are not part of any interface. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4000) Omit unnecessary external schemas in generated wsdl

by david.boeren (JIRA)

david.boeren created JBWS-4000: ---------------------------------- Summary: Omit unnecessary external schemas in generated wsdl Key: JBWS-4000 URL: https://issues.jboss.org/browse/JBWS-4000 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Affects Versions: jbossws-cxf-4.3.2 Environment: JBoss EAP 6.4.x Reporter: david.boeren Priority: Minor Attachments: CNP_2_2.java, EMIS_CNP_2_2_EAP-43.wsdl.xml, EMIS_CNP_2_2_EAP-64.wsdl.xml We have a stateless EJB exposed as a SOAP Web Services endpoint on a EAP 4.3 working perfectly. We have now ported this to EAP 6.4 and noticed that the WSDL that it generates includes 3rd party schema definitions for some internal data elements that are not part of any of the Web Services method's input or output parameter. On EAP 4.3 we do not see such schema definitions for internal data elements included. Please see attached two WSDL files, also the source code for EJB. What I can see is that the implementation of 4 WebMethods [beginWebPayment(), updateWebPayment(), getWebPayment() & cancelWebPayment()] makes a call to a private method convertRequest() that returns WebPaymentInternal which in turn contains a private member that is an instance of a EBay defined object. If I comment out these 4 methods then the resulting WSDL does not contain three EBay specific schema definitions, otherwise those three EBay specific schema definitions are included. What I do not understand why the WSDL need to expose internal data definitions when they are not part of any interface. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3989) JBossWS 5.1.4.Final and JBossWS 5.1.5.Final errata

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3989?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3989: ---------------------------------- Summary: JBossWS 5.1.4.Final and JBossWS 5.1.5.Final errata (was: JBossWS 5.1.4.Final errata) > JBossWS 5.1.4.Final and JBossWS 5.1.5.Final errata > -------------------------------------------------- > > Key: JBWS-3989 > URL: https://issues.jboss.org/browse/JBWS-3989 > Project: JBoss Web Services > Issue Type: Task > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1.4.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3989) JBossWS 5.1.4.Final errata

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3989?page=com.atlassian.jira.plugin.... ] Alessio Soldano reopened JBWS-3989: ----------------------------------- > JBossWS 5.1.4.Final errata > -------------------------- > > Key: JBWS-3989 > URL: https://issues.jboss.org/browse/JBWS-3989 > Project: JBoss Web Services > Issue Type: Task > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1.4.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3990) Upgrade to Apache CXF 3.1.6

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3990?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3990: ---------------------------------- Fix Version/s: jbossws-cxf-5.1.5.Final (was: jbossws-cxf-5.2.0.Final) > Upgrade to Apache CXF 3.1.6 > --------------------------- > > Key: JBWS-3990 > URL: https://issues.jboss.org/browse/JBWS-3990 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1.5.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3999) Testsuite failing on WFLY master because of duplicated https listener

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3999?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3999: ---------------------------------- Fix Version/s: jbossws-cxf-5.1.5.Final (was: jbossws-cxf-5.2.0.Final) > Testsuite failing on WFLY master because of duplicated https listener > --------------------------------------------------------------------- > > Key: JBWS-3999 > URL: https://issues.jboss.org/browse/JBWS-3999 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, productization > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1.5.Final > > > As a consequence of https://github.com/wildfly/wildfly/commit/8f66017f291c6e11bf1c4c9eb8a860d... , the jbossws-cxf testsuite is failing against wildfly master, because now it comes with a https listener configured by default. The jbossws-cxf test scripts needs to remove it before adding the jbossws-cxf test one in the container test configuration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3808) The response-count of the endpoint metrics sometimes not counted

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3808?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3808: ---------------------------------- Fix Version/s: jbossws-cxf-5.1.5.Final (was: jbossws-cxf-5.2.0.Final) > The response-count of the endpoint metrics sometimes not counted > ---------------------------------------------------------------- > > Key: JBWS-3808 > URL: https://issues.jboss.org/browse/JBWS-3808 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: jbossws-cxf-5.1.5.Final > > > We now calculate the request-count, response-count and other metric value in RequestHandlerImpl , it is executed after cxf's httpDestination.invoke(cfg, context, req, response) which the response already sent to receiver and invocation is done. The response related metric won't be incremented and updated if the metric query happens between httpDestination.invoke and metrics update. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues July 2016