July 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3049) Hudson jobs need to test binary and src distros against vanilla JBoss AS

by Alessio Soldano (JIRA)

Hudson jobs need to test binary and src distros against vanilla JBoss AS ------------------------------------------------------------------------ Key: JBWS-3049 URL: https://jira.jboss.org/browse/JBWS-3049 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0, jbossws-metro-4.0, jbossws-native-4.0 .. to prevent issues like JBWS-3048. I'm thinking about creating a zip of the jboss AS that is built by the AS-XYZ jobs and unzipping it in the bin/src distro jobs. The content of the zip is then used, so that we have a fresh install and not something already processed by the installations in the core jobs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-3006) Review jbossws maven dependencies

by Alessio Soldano (JIRA)

Review jbossws maven dependencies --------------------------------- Key: JBWS-3006 URL: https://jira.jboss.org/jira/browse/JBWS-3006 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native, productization Reporter: Alessio Soldano Fix For: jbossws-cxf-4.0, jbossws-metro-4.0, jbossws-native-4.0 Ideally, on trunk we should be able to replace all the deprecated maven dependencies with the new ones. Basically, we should try not to depend on the jboss deprecated maven repository (https://repository.jboss.org/nexus/content/repositories/deprecated/) Also evaluate if the org.jboss.jbossas:jboss-as-depchain can be used to further simplify the maven dependencies we need for running the testsuites. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-3063) Support Log4J in command line wsconsume and wsprovide

by Alessio Soldano (JIRA)

Support Log4J in command line wsconsume and wsprovide ----------------------------------------------------- Key: JBWS-3063 URL: https://jira.jboss.org/browse/JBWS-3063 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0, jbossws-metro-4.0, jbossws-native-4.0 ... to prevent logging directly to console, which is btw really annoying during testsuite runs (besides not being configurable) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-3002) Verify POJO endpoints are shared

by Alessio Soldano (JIRA)

Verify POJO endpoints are shared -------------------------------- Key: JBWS-3002 URL: https://jira.jboss.org/jira/browse/JBWS-3002 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-4.0 This is basically to verify we have the same behaviour as in Native, considering the performance implications this has. See https://jira.jboss.org/jira/browse/JBWS-2486 Ideally, we should have a test in framework for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-3086) Review and merge CXF JMS prototype upstream

by Richard Opalka (JIRA)

Review and merge CXF JMS prototype upstream ------------------------------------------- Key: JBWS-3086 URL: https://jira.jboss.org/browse/JBWS-3086 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-3.4.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-3069) Latest CXF release in AS trunk breaks XTS

by Andrew Dinn (JIRA)

Latest CXF release in AS trunk breaks XTS ----------------------------------------- Key: JBWS-3069 URL: https://jira.jboss.org/browse/JBWS-3069 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.3.1 Reporter: Andrew Dinn Priority: Blocker CFX JaxWS will no longer deliver asynchronous faults. The ability to do this is required by the XTS specification. See the forum thread for details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
9
0 / 0

[JBoss JIRA] Created: (JBWS-3070) Secondary import of XSD contains incorrect path

by Stelios Koussouris (JIRA)

Secondary import of XSD contains incorrect path ----------------------------------------------- Key: JBWS-3070 URL: https://jira.jboss.org/browse/JBWS-3070 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Stelios Koussouris WSDL contains import for 2 XSDs The paths to both XSD imports are correct containing schemaLocation=http://127.0.0.1:8080/my-web-service/my-web-service/?wsdl&resource=../../../xsd/misc/my-first-import.xsd When using the link to my-first-import.xsd the content of it is presented and it contains further import of schemaLocation="http://127.0.0.1:8080/my-web-service/?wsdl&resource=../../external/xsd/mi..." This one's path contains only "../../" and the link to it fails if it was "../../../../" sounds like a bug -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2990) Evaluate default enabling soap address rewrite in wsdl with request address

by Alessio Soldano (JIRA)

Evaluate default enabling soap address rewrite in wsdl with request address --------------------------------------------------------------------------- Key: JBWS-2990 URL: https://jira.jboss.org/jira/browse/JBWS-2990 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Reporter: Alessio Soldano Fix For: jbossws-cxf-4.0, jbossws-native-4.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-3080) Update build for supporting Maven 3

by Alessio Soldano (JIRA)

Update build for supporting Maven 3 ----------------------------------- Key: JBWS-3080 URL: https://jira.jboss.org/browse/JBWS-3080 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-4.0, jbossws-metro-4.0, jbossws-cxf-4.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3059) annotated POJO deployment fails

by Jonathan Halliday (JIRA)

annotated POJO deployment fails ------------------------------- Key: JBWS-3059 URL: https://jira.jboss.org/browse/JBWS-3059 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jonathan Halliday http://community.jboss.org/wiki/JBossWS-UserGuide#Plain_old_Java_Object_POJO <servlet-name> may contain spaces per web-app schema, but won't deploy in that case. Deploys fine on Native, so this is a regression for users moving between stacks / app server versions. Caused by: org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.1: 'Test Name' is not a valid value for 'NCName'. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.impl.xs.XMLSchemaValidator.processOneAttribute(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.impl.xs.XMLSchemaValidator.processAttributes(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) [xercesImpl.jar:] at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) [xercesImpl.jar:] at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:75) [:3.0.1.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:388) [:3.0.1.RELEASE] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues July 2010