January 2012 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2518) RM10PolicyAssertionDeployer enforces the incorrect Reliable Messaging Namespace

by Bryan Kearney (JIRA)

RM10PolicyAssertionDeployer enforces the incorrect Reliable Messaging Namespace ------------------------------------------------------------------------------- Key: JBWS-2518 URL: https://jira.jboss.org/jira/browse/JBWS-2518 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Environment: jboss 5.0, jboss native 3.0.5, fedora 10 Reporter: Bryan Kearney The class org/jboss/ws/extensions/wsrm/policy/RM10PolicyAssertionDeployer.java asserts the valid namespace for reliable messaging to be: http://schemas.xmlsoap.org/ws/2005/02/rm Per the spec at: http://www.google.com/url?sa=t&source=web&ct=res&cd=1&url=http%3A%2F%2Fsp... As well as the metro documentation the valid namespace should be http://schemas.xmlsoap.org/ws/2005/02/rm/policy Note the addition of policy. -- 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

12 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2254) SchemaValidation exception when referencing independent schema in wsdl

by Bob Bucy (JIRA)

SchemaValidation exception when referencing independent schema in wsdl ---------------------------------------------------------------------- Key: JBWS-2254 URL: http://jira.jboss.com/jira/browse/JBWS-2254 Project: JBoss Web Services Issue Type: Quality Risk Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.1 Environment: JBoss Server: JBoss_4_2_2_GA with jbossws-3.0.1-native-2.0.4.GA and JBoss Messaging 1.4.0.SP3 replacing JBossMQ. OS/JVM: Sun JVM build 1.5.0_15-b04, Windows XP Service Pack 2 Reporter: Bob Bucy The following exception takes place on the server when executing webservice with "@SchemaValidation" annotation. Exception does not occur when "@SchemaValidation" is disabled (e.g. able to execute service successfully, client able to run wsconsume, able to access ?WSDL, etc.). A sample application is attached which demonstrates the issue. The webservice being executed (e.g. WSTest.wsdl) does reference another schema (e.g. WSTest.xsd) that defines the input and output arguments to the webservice. Both the WSTest.wsdl and WSTest.xsd schemas are located in the WEB-INF\wsdl directory. 2008-07-10 13:36:26,224 WARN [org.jboss.ws.extensions.validation.StrictlyValidErrorHandler] org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'WSTest.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. 2008-07-10 13:36:26,224 ERROR [org.jboss.ws.extensions.validation.StrictlyValidErrorHandler] org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'wsdoc:WSReq' to a(n) 'element declaration' component. 2008-07-10 13:36:26,224 DEBUG [org.jboss.ws.core.jaxws.handler.MessageContextJAXWS] Begin response processing 2008-07-10 13:36:26,224 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS@de4588 (Thread http-127.0.0.1-8080-2) 2008-07-10 13:36:26,224 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] pushMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS@15d7792 (Thread http-127.0.0.1-8080-2) 2008-07-10 13:36:26,240 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception org.jboss.ws.WSException: org.xml.sax.SAXException: src-resolve: Cannot resolve the name 'wsdoc:WSReq' to a(n) 'element declaration' component. at org.jboss.ws.WSException.rethrow(WSException.java:68) at org.jboss.ws.core.soap.SOAPBodyElementDoc.validatePayload(SOAPBodyElementDoc.java:130) at org.jboss.ws.core.soap.SOAPBodyElementDoc.transitionTo(SOAPBodyElementDoc.java:82) at org.jboss.ws.core.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:173) at org.jboss.ws.core.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:263) at org.jboss.ws.core.EndpointInvocation.getRequestParamValue(EndpointInvocation.java:115) at org.jboss.ws.core.EndpointInvocation.getRequestPayload(EndpointInvocation.java:135) -- 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, 10 months

3
4
0 / 0

[JBoss JIRA] (JBWS-3422) Review and enable passing serviceref/webserviceref tests

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3422: ------------------------------------- Summary: Review and enable passing serviceref/webserviceref tests Key: JBWS-3422 URL: https://issues.jboss.org/browse/JBWS-3422 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0.1, 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, 10 months

1
1
0 / 0

[JBoss JIRA] (JBWS-3421) EndpointRegistryDeploymentAspect can't properly deal with AS7 domain reloads

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3421: ------------------------------------- Summary: EndpointRegistryDeploymentAspect can't properly deal with AS7 domain reloads Key: JBWS-3421 URL: https://issues.jboss.org/browse/JBWS-3421 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0.1, jbossws-native-4.0.1 ... because it caches the EndpointRegistry, which is created internally by an AS7 service during domain load. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3162) Add javaee_web_services_metadata_handler_2_0.xsd to jbossws-entities.properties

by Robert Dale (JIRA)

Add javaee_web_services_metadata_handler_2_0.xsd to jbossws-entities.properties ------------------------------------------------------------------------------- Key: JBWS-3162 URL: https://jira.jboss.org/browse/JBWS-3162 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.4.1 Reporter: Robert Dale This is for JBEPP-400 . I believe this change belongs here rather than have EPP use a catalog. META-INF/jbossws-entities.properties: http\://java.sun.com/xml/ns/javaee/javaee_web_services_metadata_handler_2_0.xsd=schema/javaee_web_services_metadata_handler_2_0.xsd schema/javaee_web_services_metadata_handler_2_0.xsd (from http://java.sun.com/xml/ns/javaee/javaee_web_services_metadata_handler_2_...): <?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://java.sun.com/xml/ns/javaee" xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" version="2.0"> <xsd:annotation> <xsd:documentation> javaee_web_services_metadata_handler.xsd v2.0.1 11/09/2007 </xsd:documentation> </xsd:annotation> <xsd:annotation> <xsd:documentation> Copyright 2004-2007 BEA Systems, Inc. </xsd:documentation> </xsd:annotation> <xsd:include schemaLocation="javaee_5.xsd"/> <xsd:element name="handler-chains" type="javaee:service-ref_handler-chainsType"> <xsd:annotation> <xsd:documentation> The handler-chains element is the root element for defining handlerchains. The Web Services Metadata for the Java Platform (JSR-181), Version 2.0 specification defines the @javax.jws.HandlerChain annotation that refers to an XML descriptor conforming to this schema. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:schema> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
2
0 / 0

[JBoss JIRA] (JBWS-3386) Usernametoken support requires optional elements

by Matt Wringe (Created) (JIRA)

Usernametoken support requires optional elements ------------------------------------------------ Key: JBWS-3386 URL: https://issues.jboss.org/browse/JBWS-3386 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Matt Wringe Usernametoken support is currently broken as it requires a username and password to be present in the wss security header. According to the WSS specifications (both 1.0 and 1.1*) these are optional elements in wsse:UsernameToken. If either one of these elements are missing, then JBossWS incorrectly throws a WSSecurityException. See http://anonsvn.jboss.org/repos/jbossws/stack/native/trunk/modules/core/sr... lines 78 and 84 for where it should not be throwing this error. * 1.1 spec http://www.oasis-open.org/committees/download.php/16782/wss-v1.1-spec-os-... 1.0 spec http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-pr... -- 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, 10 months

4
4
0 / 0

[JBoss JIRA] (JBWS-3420) Enhance deployment performance by simplifying connector conf retrieval

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3420: ------------------------------------- Summary: Enhance deployment performance by simplifying connector conf retrieval Key: JBWS-3420 URL: https://issues.jboss.org/browse/JBWS-3420 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0.1, jbossws-native-4.0.1 After the refactoring for supporting AS 7, a sensible amount of ws endpoints deployment time is spent into org.jboss.ws.common.management.AbstractServerConfig for computing the port/securePort. That needs to be fixed removing legacy code. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] (JBWS-3388) Rewrite tests using JMX to connect to the server

by Richard Opalka (Created) (JIRA)

Rewrite tests using JMX to connect to the server ------------------------------------------------ Key: JBWS-3388 URL: https://issues.jboss.org/browse/JBWS-3388 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Richard Opalka Fix For: jbossws-cxf-4.0.1, jbossws-native-4.0.1 The JMX support have been removed in AS 7.1 We need to investigate different approach and rewrite the tests relying on this 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, 10 months

4
3
0 / 0

[JBoss JIRA] (JBWS-3419) Restore managed endpoint registry

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3419: ------------------------------------- Summary: Restore managed endpoint registry Key: JBWS-3419 URL: https://issues.jboss.org/browse/JBWS-3419 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0.1, 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, 10 months

1
1
0 / 0

[JBoss JIRA] (JBWS-3410) Upgrade to Apache CXF 2.4.5

by Richard Opalka (Created) (JIRA)

Upgrade to Apache CXF 2.4.5 --------------------------- Key: JBWS-3410 URL: https://issues.jboss.org/browse/JBWS-3410 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-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, 10 months

2
2
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