November 2011 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2803) Need mechanism for externalizing wsdl_url property

by Matt Davis (JIRA)

Need mechanism for externalizing wsdl_url property -------------------------------------------------- Key: JBWS-2803 URL: https://jira.jboss.org/jira/browse/JBWS-2803 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: JBoss [EAP] 4.3.0.GA_CP04 Java VM: Java HotSpot(TM) Server VM 14.0-b16,Sun Microsystems Inc. OS-System: Windows XP 5.1,x86 Reporter: Matt Davis Assignee: Darran Lofthouse Priority: Minor A customer is requesting a way to externalize the wsdl url (move it outside of the JBoss environment). They have attempted using <wsdl-override> and then passing a property inside of the tag - ${jboss.host.details}. This does not work and property replacement is not supported in this portion of the jboss-web.xml file. In the interim the customer has made changes to the DefaultServiceRefMetaDataParser class to allow them to pass the property into the wsdl-overide. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBWS-2697) Consistent Configuration for HTTP connections

by Darran Lofthouse (JIRA)

Consistent Configuration for HTTP connections --------------------------------------------- Key: JBWS-2697 URL: https://jira.jboss.org/jira/browse/JBWS-2697 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Darran Lofthouse Assignee: Alessio Soldano Fix For: jbossws-native-3.2.0 When calling a remote endpoint that is either secured using BASIC authentication or using HTTPS (or even both together) we use the java.net.URL.openConnection() method to obtain the WSDL and related XSDs but we then use JBoss Remoting for the WS call. This means that both connection approaches need to be configured to call the same endpoint. If would help if there was some way we could unify the configuration so when calling an endpoint this only needs to be configured once. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBWS-2635) Provider can't send back (echo) received soap message correctly

by Alessio Soldano (JIRA)

Provider can't send back (echo) received soap message correctly --------------------------------------------------------------- Key: JBWS-2635 URL: https://jira.jboss.org/jira/browse/JBWS-2635 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.1.1 Reporter: Alessio Soldano Invoking the org.jboss.test.ws.jaxws.samples.provider.ProviderBeanMessage endpoint using tools like SOAPUi with a message like <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:prov="http://org.jboss.ws/provider"> <soapenv:Header/> <soapenv:Body> <prov:user> <string>?</string> <qname>?</qname> </prov:user> </soapenv:Body> </soapenv:Envelope> causes a truncated message to go on the wire, even if the message is correctly logged by the MessageTrace. Exchanging the message above using the related testcase (org.jboss.test.ws.jaxws.samples.provider.ProviderMessageTestCase) does not reproduce the issue. -- 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

1
9
0 / 0

[JBoss JIRA] Created: (JBWS-2311) WSA does not work for provider based endpoint

by Jim Ma (JIRA)

WSA does not work for provider based endpoint --------------------------------------------- Key: JBWS-2311 URL: https://jira.jboss.org/jira/browse/JBWS-2311 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native, ws-addressing Affects Versions: jbossws-native-3.0.1 Reporter: Jim Ma When add the WSAddressingServerHandler for provider based endpoint , it raises the following error : ERROR [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Exception during handler processing javax.xml.ws.addressing.AddressingException: Required addressing property missing: {http://www.w3.org/2005/08/addressing}Action at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.appendRequiredHeader(SOAPAddressingPropertiesImpl.java:304) at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.writeHeaders(SOAPAddressingPropertiesImpl.java:257) at org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler.handleResponseOrFault(WSAddressingServerHandler.java:156) at org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler.handleOutbound(WSAddressingServerHandler.java:92) at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140) at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callResponseHandlerChain JAXWSProviderMetaDataBuilder does not process the WSA information add generate AddressingOpMetaExt. This will cause the required outbound action in SoapAddressingProperties not set , see the following WSAddressingServerHandler code segment : OperationMetaData opMetaData = ((SOAPMessageContextJAXRPC)msgContext).getOperationMetaData(); if (!isFault && !opMetaData.isOneWay()) { AddressingOpMetaExt addrExt = (AddressingOpMetaExt)opMetaData.getExtension(ADDR_CONSTANTS.getNamespaceURI()); if (addrExt != null) { outProps.setAction(ADDR_BUILDER.newURI(addrExt.getOutboundAction())); } else { log.warn("Unable to resolve replyAction for " + opMetaData.getQName()); } } -- 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

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-2459) Allow WebServiceFeature to disable wsdl extension requirements

by Alessio Soldano (JIRA)

Allow WebServiceFeature to disable wsdl extension requirements -------------------------------------------------------------- Key: JBWS-2459 URL: https://jira.jboss.org/jira/browse/JBWS-2459 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Regarding the @RespectBinding/RespectBindingFeature, the JAXWS 2.1 spec says that all required wsdl:extensions MUST be supported and honored by the implementation unless a specific wsdl:extension has been explicitely disabled via a WebServiceFeature. This is currently not supported as there's no webservice feature implemented having a corresponding wsdl extension. Perhaps ws-addressing could be an example with UsingAddressing. We should nevertheless implement this mechanism. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBWS-2406) Make OneWay Operations Non-Blocking

by Darran Lofthouse (JIRA)

Make OneWay Operations Non-Blocking ----------------------------------- Key: JBWS-2406 URL: https://jira.jboss.org/jira/browse/JBWS-2406 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.4 Reporter: Darran Lofthouse Currently the @OneWay operations block while the business logic executes on the server and does not return a response until processing is complete. This feature request is to modify one-way operations to be non-blocking. There are various options to be investigated: - - As soon as server knows it is a valid message send HTTP response but thread continue to process. - Fork a new thread server side to call business method. - Fork thread client side for the call. (This is not an exhaustive list just some of the current suggestions) -- 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

3
16
0 / 0

[JBoss JIRA] Created: (JBWS-2277) When publishing WS using an existing WSDL file from wsdlLocation, file:// <soap:address> bindings are not converted to http://

by Alexandros Karypidis (JIRA)

When publishing WS using an existing WSDL file from wsdlLocation, file:// <soap:address> bindings are not converted to http:// ------------------------------------------------------------------------------------------------------------------------------ Key: JBWS-2277 URL: https://jira.jboss.org/jira/browse/JBWS-2277 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.2 Environment: I am using Sun's JDK 1.5.0_15, JBoss 4.2.3 with JBossWS-Native-3.0.2 on a x86-32 Intel PC with Windows XP. Reporter: Alexandros Karypidis Priority: Trivial Attachments: fileURLBindingBug.zip When using "wsdLocation" in @WebService, JBoss reads the WSDL file you provided and does the following: 1) if the <soap:address> tag in the WSDL file has a "file://..." URL in it, it does NOT replace it with the actual address where your web service endpoint was bound. 2) if the <soap:address> tag in the WSDL file has an "http://..." URL in it, it replaces it with the actual address where your web service endpoint was bound. The WSDL published by JBoss should use http/https as appropriate. -- 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
10
0 / 0

[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] 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, 11 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2011