January 2012 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3413) ServletClientBusTestCase is missing an edge case

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3413: ------------------------------------- Summary: ServletClientBusTestCase is missing an edge case Key: JBWS-3413 URL: https://issues.jboss.org/browse/JBWS-3413 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
3
0 / 0

[JBoss JIRA] (JBWS-3418) Enhance X509 certificate issuer comparison

by Kyle Lape (JIRA)

Kyle Lape created JBWS-3418: ------------------------------- Summary: Enhance X509 certificate issuer comparison Key: JBWS-3418 URL: https://issues.jboss.org/browse/JBWS-3418 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-native-3.0.2 Reporter: Kyle Lape Assignee: Kyle Lape Fix For: jbossws-native-4.0.1 Attachments: patch.txt See the forum message -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3417) JAXWSServerMetaDataBuilder::processWSDDContribution does not process WSDL location override

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3417: ------------------------------------- Summary: JAXWSServerMetaDataBuilder::processWSDDContribution does not process WSDL location override Key: JBWS-3417 URL: https://issues.jboss.org/browse/JBWS-3417 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-4.0.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3416) MetadataBuilder does not re-use WebserviceMetadata parsed into AS integration layer

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3416: ------------------------------------- Summary: MetadataBuilder does not re-use WebserviceMetadata parsed into AS integration layer Key: JBWS-3416 URL: https://issues.jboss.org/browse/JBWS-3416 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-4.0.0.CR1 Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0 MetadataBuilder::processWSDDContribution(DDEndpoint endpoint, ArchiveDeployment dep) forces additional check / parse of webservices.xml descriptor while it should re-use the metadata coming from ASIL where that descriptor is already parsed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
1
0 / 0

[JBoss JIRA] (JBWS-3415) Provider endpoints are not processed for DD contribution

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3415: ------------------------------------- Summary: Provider endpoints are not processed for DD contribution Key: JBWS-3415 URL: https://issues.jboss.org/browse/JBWS-3415 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-4.0.1 Currently provider endpoints (@WebServiceProvider annotated) are not processed for deployment descriptor contribution (see 5.3.2.2 in JSR 109 1.3) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3414) DeploymentAspectManagerImpl does not properly deal with deployment failures

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3414: ------------------------------------- Summary: DeploymentAspectManagerImpl does not properly deal with deployment failures Key: JBWS-3414 URL: https://issues.jboss.org/browse/JBWS-3414 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0.1, jbossws-native-4.0.1 The DeploymentAspectManagerImpl (which is currently being used by the EndpointPublisher spi) does not properly undo the already started aspects' work when an exception is thrown during deployment. That leaves the server in an inconsistent state (usually due to endpoint registry still having the failed deployment). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3268) REPLACE_WITH_ACTUAL_URL does not work for more than one Port in a WSDL

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3268?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3268: ---------------------------------- Fix Version/s: (was: jbossws-cxf-4.0.1) (was: jbossws-native-4.0.1) > REPLACE_WITH_ACTUAL_URL does not work for more than one Port in a WSDL > ---------------------------------------------------------------------- > > Key: JBWS-3268 > URL: https://issues.jboss.org/browse/JBWS-3268 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-native > Reporter: Mustafa Musaji > Assignee: Jim Ma > > If you have a WSDL that contains more than one port and want the wsdl address location to be changed as per the jboss-beans.xml file this does not work. Only the first port will have it's location changed. The second will remain as REPLACE_WITH_ACTUAL_URL value and no error displayed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3412) Add WS-Security Policy (sign+encrypt) testcase with multiple clients support

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3412: ------------------------------------- Summary: Add WS-Security Policy (sign+encrypt) testcase with multiple clients support Key: JBWS-3412 URL: https://issues.jboss.org/browse/JBWS-3412 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0.1 We need to enrich the ws-security policy samples with a testcase featuring an endpoint configured for supporting encrypting responses for multiple clients. Basically that's possible using the "ws-security.encryption.username = useReqSigCert" CXF feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2251) Enhance X509 certificate issuer comparison

by Alessio Soldano (JIRA)

Enhance X509 certificate issuer comparison ------------------------------------------ Key: JBWS-2251 URL: http://jira.jboss.com/jira/browse/JBWS-2251 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-native-3.0.2 Reporter: Alessio Soldano See the forum message -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
7
0 / 0

[JBoss JIRA] (JBWS-3411) WSDL generation for javax.jws SOAP services uses system-default character set.

by Bastian Blankenburg (Created) (JIRA)

WSDL generation for javax.jws SOAP services uses system-default character set. ------------------------------------------------------------------------------ Key: JBWS-3411 URL: https://issues.jboss.org/browse/JBWS-3411 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.4.1 Environment: Windows 7, JDK 1.6.0 64bit, JBoss AS 5.1.0GA Reporter: Bastian Blankenburg When deploying a webservice implemented using javax.jws and JAXB annotations, a WSDL is generated. In this process, a temporary XML schema file is generated and written to the tmp directory by the WSDL11Reader.processSchemaInclude method. It uses a DOMWriter in lines 640-646 to actually write the file via a FileWriter. This leads to the schema being written with the system-default character set, without an XML declaration. For non-ASCII characters, this might in turn lead to org.apache.xerces.xni.XNIException being thrown by the xerces parser when the file is read again by the JavaToXSD.parseSchema (line 181) method. For example, part of my I have an @XmlEnum with a value "località", specified by @XmlEnumValue("localit\u00e0"), which causes this problem. The exception message in this case is "Parser should stop: JBossWS_(...)18444939893360070.xsd[domain:http://www.w3.org/TR/1998/REC-x... byte 2 of 3-byte UTF-8 sequence." Java char supports UTF-16 characters with the "\u" escape sequences. The DOMWriter has another constructor DOMWriter(OutputStream stream, String charsetName) which also causes an XML declaration to be written. Its usage in WSDL11Reader with "UTF-16" as second parameter would thus avoid the described problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 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 January 2012