November 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1439) Jdk 1.6.0 Requests get the error "setProperty must be overridden by all subclasses of SOAPMessage"

by Denis Angleton (JIRA)

Jdk 1.6.0 Requests get the error "setProperty must be overridden by all subclasses of SOAPMessage" -------------------------------------------------------------------------------------------------- Key: JBWS-1439 URL: http://jira.jboss.com/jira/browse/JBWS-1439 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.0.4 Environment: Jboss 4.0.5.GA Java 1.6.0 Reporter: Denis Angleton Requests get the error "setProperty must be overridden by all subclasses of SOAPMessage" In the abstract class javax.xml.soap.SOAPMessage which is now shipped with the jdk, the implementation of setProperty is as follows: public void setProperty(String property, Object value) throws SOAPException { throw new UnsupportedOperationException("setProperty must be overridden by all subclasses of SOAPMessage"); } in the constructor of org.jboss.ws.soap.SOAPMessageImpl it calls the super methods setProperty(CHARACTER_SET_ENCODING, "UTF-8"); setProperty(WRITE_XML_DECLARATION, false); This results in the exception being thrown. -- 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, 1 month

19
33
0 / 0

[JBoss JIRA] Created: (JBWS-1814) Dynamic Encryption based on clients input

by Magesh Kumar B (JIRA)

Dynamic Encryption based on clients input ----------------------------------------- Key: JBWS-1814 URL: http://jira.jboss.com/jira/browse/JBWS-1814 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-2.0.1, jbossws-1.2.1 Reporter: Magesh Kumar B Let's say that Bob runs the web service and Alice has a client that uses the web service. Now John would also like to use the web service. John would create: johns.keystore ---------------- john - keyPair (pub+priv) bob - trustedCertEntry (pub) johns.truststore ---------------- john - trustedCertEntry (just john's public key) In addition, Bob's keystore would be updated to: bobs.keystore ---------------- bob - keyPair (public + private key) alice - trustedCertEntry (just alice's public key) john - trustedCertEntry (just john's public key) This does not pose a problem for encrypting the request from the client side since both Alice and John use Bob's public key to encrypt the message, and Bob of course uses his pirvate key to decrypt the message. But how is the response message encrypted? JBossWS apparently does not support multiple clients because the certificate used by the server to encrypt the response is specified statically in jboss-wsse-server.xml. -- 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, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (JBWS-2070) Add attachment interop endpoint for MTOM and SwaRef

by Heiko Braun (JIRA)

Add attachment interop endpoint for MTOM and SwaRef --------------------------------------------------- Key: JBWS-2070 URL: http://jira.jboss.com/jira/browse/JBWS-2070 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Heiko Braun -- 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, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (JBWS-2302) Verify dependencies on outstanding Metro issues

by Alessio Soldano (JIRA)

Verify dependencies on outstanding Metro issues ----------------------------------------------- Key: JBWS-2302 URL: https://jira.jboss.org/jira/browse/JBWS-2302 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Fix For: jbossws-metro-3.0.4 Before releasing we should check if some of the Metro issue we created have been solved, so that the corresponding JBossWS issue can be solved. -- 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, 9 months

3
22
0 / 0

[JBoss JIRA] Created: (JBWS-2397) Fix jbws1797 testcase

by Alessio Soldano (JIRA)

Fix jbws1797 testcase --------------------- Key: JBWS-2397 URL: https://jira.jboss.org/jira/browse/JBWS-2397 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Alessio Soldano Priority: Minor Fix For: jbossws-metro-3.0.6 The JBWS1797TestCase is about .NET friendly part names; it's in framework but has never been executed with the metro integration stack because of the missing wrapper generation on both client and server side. Now that's possible and reveals that the test should be written better to support different message names in the wsdls generated by different stacks (or to have the same generated message names). -- 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, 9 months

1
6
0 / 0

[JBoss JIRA] Created: (JBWS-2068) Interop endpoints

by Heiko Braun (JIRA)

Interop endpoints ----------------- Key: JBWS-2068 URL: http://jira.jboss.com/jira/browse/JBWS-2068 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jbossws-3.0.2 Reporter: Heiko Braun Collection of interop related subtasks -- 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
8
0 / 0

[JBoss JIRA] Created: (JBWS-2049) Provide a comprehensive test case for WS-RM

by Richard Opalka (JIRA)

Provide a comprehensive test case for WS-RM ------------------------------------------- Key: JBWS-2049 URL: http://jira.jboss.com/jira/browse/JBWS-2049 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-3.0.2 Supersedes JBWS-1700 -- 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
6
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-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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2008