December 2011 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3339) Preamble is omitted when supplying external XSDs

by Kyle Lape (JIRA)

Preamble is omitted when supplying external XSDs ------------------------------------------------ Key: JBWS-3339 URL: https://issues.jboss.org/browse/JBWS-3339 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Kyle Lape The XML preamble is omitted when serving external WSDL resources. This can cause problem when specifying a non-default character set using the XML preamble. For example, you access an external XSD: http://localhost:8080/testService/Service?wsdl&resource=external.xsd The file on the server starts like this: <?xml version="1.0" encoding="UTF-8"?> <xsd:schema ...> ... </xsd:schema> But when it's served to a client, it starts like this: <xsd:schema ...> ... </xsd:schema> This affects the WSDL and any resources referenced by the WSDL. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (JBWS-3165) Add support for jax-ws xml catalog to be spec-compliant

by Robert Dale (JIRA)

Add support for jax-ws xml catalog to be spec-compliant ------------------------------------------------------- Key: JBWS-3165 URL: https://jira.jboss.org/browse/JBWS-3165 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Robert Dale <ropalka> rdale, OK, JAXWS 2.2 - section 4.4 <ropalka> --- <ropalka> The catalog is assembled by taking into account all accessible resources whose name is META-INF/jax- <ropalka> -ws-catalog.xml. Each resource MUST be a valid entity catalog according to the XML Catalogs 1.1 <ropalka> specification. When running on the Java SE platform, the current context class loader MUST be used to <ropalka> retrieve all the resources with the specified name. Relative URIs inside a catalog file are relative to the <ropalka> location of the catalog that contains them. <ropalka> --- <ropalka> rdale, AFAIK Native doesn't support it. It uses proprietary jbossws-entities.properties approach <ropalka> rdale, CXF should support it. <ropalka> rdale, Do U use JBossWS Native or JBossWS CXF? <darran> ropalka, CXF does, we are using it in SOA-P 5.1 <ropalka> rdale, I confirm JBossWS Native doesn't support it (although this is required by JAX-WS spec). The reason is this is not tested in TCK6 (certification suites) and we didn't have feature request to implement it yet. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
1
0 / 0

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

by Mustafa Musaji (Created) (JIRA)

Enhance X509 certificate issuer comparison ------------------------------------------ Key: JBWS-3406 URL: https://issues.jboss.org/browse/JBWS-3406 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: Mustafa Musaji 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3404) JBossWS-Native 4.0.0.GA Errata

by Alessio Soldano (Created) (JIRA)

JBossWS-Native 4.0.0.GA Errata ------------------------------ Key: JBWS-3404 URL: https://issues.jboss.org/browse/JBWS-3404 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Assignee: Richard Opalka Fix For: jbossws-native-4.0 -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] (JBWS-3403) JBossWS-CXF 4.0.0.GA Errata

by Alessio Soldano (Created) (JIRA)

JBossWS-CXF 4.0.0.GA Errata --------------------------- Key: JBWS-3403 URL: https://issues.jboss.org/browse/JBWS-3403 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Richard Opalka Fix For: jbossws-cxf-4.0 -- 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, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-3281) Create a migration guide to JBossWS 4.0 / AS 7 integration

by Alessio Soldano (JIRA)

Create a migration guide to JBossWS 4.0 / AS 7 integration ---------------------------------------------------------- Key: JBWS-3281 URL: https://issues.jboss.org/browse/JBWS-3281 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native, productization Reporter: Alessio Soldano Fix For: jbossws-native-4.0, jbossws-cxf-4.0 A migration guide from JBossWS 3.4.x to JBossWS 4.0 (and in particular to AS7 w/ JBossWS 4) should be included in the release documentation. At the moment the topic to be covered should be: - consequences for users due to changes in classloading (see JBossWS AS7 FAQ) - changes in API (new jbossws-api library, package refactorings, etc.) - changes in WS-* configuration - changes due to libraries upgrades (mainly due to dependencies coming from Apache CXF 2.4 upgrade) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

4
6
0 / 0

[JBoss JIRA] (JBWS-3405) Additional WS-Security Policy samples

by Alessio Soldano (Created) (JIRA)

Additional WS-Security Policy samples ------------------------------------- Key: JBWS-3405 URL: https://issues.jboss.org/browse/JBWS-3405 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.1 We should evaluate extending the samples testsuite with new scenarios (see http://coheigea.blogspot.com/2011/12/ws-securitypolicy-examples-in-apache... for instance) and possibly see if we can have an example using @Policy too. -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-3295) Change default folder for wsconsume generated sources

by Anders Hammar (JIRA)

Change default folder for wsconsume generated sources ----------------------------------------------------- Key: JBWS-3295 URL: https://issues.jboss.org/browse/JBWS-3295 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Components: jaxws-tools-maven-plugin Affects Versions: jbossws-jaxws-tools-maven-plugin-1.0.1.GA Environment: n/a Reporter: Anders Hammar Priority: Minor The Maven convention for generated sources is for those to be created under target/generated-sources/blabla. The AbstractWsConsumeMojo class specifies that sources be created under target/wsconsume/java (through the default-value of the sourceDirectory param). I suggest this is changed to "${project.build.directory}/generated-sources/wsconsume". (I don't see a need for adding a trailing "java".) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
2
0 / 0

[JBoss JIRA] (JBWS-3401) Implement support for deployment of EJB3 endpoints bundled in war archives referencing WSDL that is importing XML schema(s)

by Richard Opalka (Created) (JIRA)

Implement support for deployment of EJB3 endpoints bundled in war archives referencing WSDL that is importing XML schema(s) --------------------------------------------------------------------------------------------------------------------------- Key: JBWS-3401 URL: https://issues.jboss.org/browse/JBWS-3401 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.0, jbossws-cxf-4.0 -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] (JBWS-3402) jaxws-tools-maven-plugin does not resolve 'provided' scope project dependencies

by Alessio Soldano (Created) (JIRA)

jaxws-tools-maven-plugin does not resolve 'provided' scope project dependencies ------------------------------------------------------------------------------- Key: JBWS-3402 URL: https://issues.jboss.org/browse/JBWS-3402 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxws-tools-maven-plugin Affects Versions: jbossws-jaxws-tools-maven-plugin-1.0.1.GA Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-jaxws-tools-maven-plugin-1.1.0.GA The plugin does not resolve dependencies that are added with 'provided' scope to the project the plugin is used into. This is a problem when users want to also add the maven-war-plugin as that includes all non-provided dependencies into the generated war archive and of course we don't want users to have jbossws-*-client artifacts into their deployments. -- 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, 11 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 December 2011