May 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-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-2157) Child nodes truncated when using jaxb to marshall data into a SOAP header

by Andrew Dinn (JIRA)

Child nodes truncated when using jaxb to marshall data into a SOAP header -------------------------------------------------------------------------- Key: JBWS-2157 URL: http://jira.jboss.com/jira/browse/JBWS-2157 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.1 Reporter: Andrew Dinn I wish to serialise a CoordinationContext type (a complex type defined in the OASIS WS-COOR 1.1 spec) into a SOAP message header as follows: <code> final JAXBContext jaxbCtx = getJaxbContext(); final SOAPMessage soapMessage = context.getMessage(); final SOAPEnvelope soapEnvelope = soapMessage.getSOAPPart().getEnvelope(); SOAPHeader soapHeader = soapEnvelope.getHeader() ; if (soapHeader == null) { soapHeader = soapEnvelope.addHeader() ; } Marshaller marshaller = jaxbCtx.createMarshaller(); marshaller.marshal(coordinationContext, soapHeader); </code> The problem is that the header gets inserted without any children. What happens is that the marshaller creates a SOAP tree top down consisting of SOAPElementImpl instances. It inserts these nodes into the tree below the SOAPHeader as it creates them. So, when the first node is created a call to SOAPHeader.addchild() is made. This call deteccts that the supplied node is of the wrong type so it substitutes a SOAPHeaderElementImpl. It attempts to copy the supplied node's substructure but the marshaller has not created the children at this point. -- 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

13 years

4
7
0 / 0

[JBoss JIRA] Created: (JBWS-2192) Asynchronous calls not thread safe

by Thomas Diesler (JIRA)

Asynchronous calls not thread safe ---------------------------------- Key: JBWS-2192 URL: http://jira.jboss.com/jira/browse/JBWS-2192 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Thomas Diesler Fix For: jbossws-native-3.0.3 Darran sais: I am currently looking at a support case where the customer is getting a number of errors with asynchronous JAX-WS invocations using a AsyncHandler. I am running a couple of test cases against the two EAP releases and I am able to reproduce the behaviour that the customer is seeing but I just quickly wanted to double check what should be thread safe. I have an async method on the SEI that returns a Future instance and takes an AsyncHandler as a parameter: - @WebMethod(operationName = "lookup") public Future<?> lookupAsync(final Person person, AsyncHandler<TelephoneNumber> handler); This pattern seems to suggest that after the call has been made any further interaction will be with the Future instance or the handler which then makes it look as though the Port is free to service other requests. However if I submit multiple requests using the same Port then the outgoing requests start to get mixed up. Should it be possible to re-use the same Port / SEI Proxy for multiple calls without worries of messages being mixed up? I would have thought if the Port was not supposed to be re-used the get methods for the response would be on the Port instance and not need to use this returned interface. I have attached the client I am using to reproduce the errors. Creating a new Port for each request does overcome this issue but they are trying to avoid this especially as the existing Port should have passed the last request off to another thread for processing. -- 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

13 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-2102) javax.xml.ws.addressing package not available in JBossWS-Metro

by Andrew Dinn (JIRA)

javax.xml.ws.addressing package not available in JBossWS-Metro -------------------------------------------------------------- Key: JBWS-2102 URL: http://jira.jboss.com/jira/browse/JBWS-2102 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jbossws-metro-1.0.1 Reporter: Andrew Dinn The AddressingProperties and related API classes in the javax.xml.ws.addressing package are not available in JBossWS-Metro. These are needed for the Web Services Transactions 1.1 implementation to operate over the Metro stack. -- 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

14 years, 2 months

4
23
0 / 0

[JBoss JIRA] Created: (JBWS-1949) MEtro MTOM ignores content-type on attachment part

by Heiko Braun (JIRA)

MEtro MTOM ignores content-type on attachment part -------------------------------------------------- Key: JBWS-1949 URL: http://jira.jboss.com/jira/browse/JBWS-1949 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-metro Affects Versions: jbossws-2.0.3 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-2.1.0 It turns everything into application/octet-stream on a DataHandler instance, even though the attachment part contains an explicit content-type. -- 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

14 years, 2 months

4
17
0 / 0

[JBoss JIRA] Created: (JBWS-2131) WebServiceException: Failed to build METRO runtime model

by Thomas Diesler (JIRA)

WebServiceException: Failed to build METRO runtime model -------------------------------------------------------- Key: JBWS-2131 URL: http://jira.jboss.com/jira/browse/JBWS-2131 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Affects Versions: jbossws-metro-1.0.1 Reporter: Thomas Diesler [tdiesler@tdvaio trunk]$ ant -Dtest=jaxws/jbws1702 test 19:24:24,883 ERROR [MainDeployer] Could not start deployment: file:/home/tdiesler/svn/jbossws/stack/metro/trunk/output/tests/libs/jaxws-jbws1702.war javax.xml.ws.WebServiceException: Failed to build METRO runtime model at org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect.create(RuntimeModelDeploymentAspect.java:136) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118) at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97) at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) -- 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

14 years, 2 months

3
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues May 2008