May 2011 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3157) Feature for controlling chunked encoding

by Alessio Soldano (JIRA)

Feature for controlling chunked encoding ---------------------------------------- Key: JBWS-3157 URL: https://jira.jboss.org/browse/JBWS-3157 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-3.4.1 We should basically see if it's possible to make the org.jboss.ws.feature.ChunkedEncodingFeature available for jbossws-cxf too. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2728) Review JBossWS EJB integration

by Richard Opalka (JIRA)

Review JBossWS EJB integration ------------------------------- Key: JBWS-2728 URL: https://jira.jboss.org/jira/browse/JBWS-2728 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1 We're depending on EJB real deployers. We need to investigate whether we really need to depend on these EJB deployers. Maybe using JBoss meta data will could sufficient? Some time ago also Adrian Brock wrote (see http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4059197#4059197): --- Even after this, there are lots of issues about whether webservices should be depending on things like ejb3 at all. It should certainly have access to its metadata for deployment purposes, which is one of the reasons we have started a "metadata" project so projects can share each others models. --- The only possible problem that comes to my mind is whether we're able to implement JBossWS injections without depending on EJB real deployers? -- 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, 7 months

2
8
0 / 0

[JBoss JIRA] Created: (JBWS-3219) Unexpected element 'security-domain' encountered

by Richard Opalka (JIRA)

Unexpected element 'security-domain' encountered ------------------------------------------------ Key: JBWS-3219 URL: https://issues.jboss.org/browse/JBWS-3219 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Fix For: jbossws-native-4.0, jbossws-cxf-4.0 15:39:27,123 ERROR [org.jboss.msc] (pool-2-thread-5) MSC-00001: Failed to start service jboss.deployment.unit.jaxws-jbws1702.war.PARSE: org.jboss.msc.service.StartException in service jboss <------>at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:89) <------>at org.jboss.msc.service.ServiceInstanceImpl$StartTask.run(ServiceInstanceImpl.java:1163) <------>at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_20] <------>at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_20] <------>at java.lang.Thread.run(Thread.java:636) [:1.6.0_20] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to parse "/content/jaxws-jbws1702.war/WEB-INF/jboss-web.xml" <------>at org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:66) <------>at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:85) <------>... 4 more Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[6,56] Message: Unexpected element 'security-domain' encountered <------>at org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109) <------>at org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser.parse(JBossWebMetaDataParser.java:154) <------>at org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:64) <------>... 5 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-3200) soap:address rewrite from Spring configuration

by Alessio Soldano (JIRA)

soap:address rewrite from Spring configuration ---------------------------------------------- Key: JBWS-3200 URL: https://issues.jboss.org/browse/JBWS-3200 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 JBWS-2777 configured from the spring cxf.xml / jbossws-cxf.xml. This should be possible starting from Apache CXF 2.3.2, see https://issues.apache.org/jira/browse/CXF-2770 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2627) Provide more CXF WS-RM integration tests to verify QoS

by Richard Opalka (JIRA)

Provide more CXF WS-RM integration tests to verify QoS ------------------------------------------------------ Key: JBWS-2627 URL: https://jira.jboss.org/jira/browse/JBWS-2627 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.2.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, 8 months

2
9
0 / 0

[JBoss JIRA] Created: (JBWS-3291) Native stack have to support endpoints with overloaded methods

by Richard Opalka (JIRA)

Native stack have to support endpoints with overloaded methods --------------------------------------------------------------- Key: JBWS-3291 URL: https://issues.jboss.org/browse/JBWS-3291 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.0.0.Beta1 The solution will for every overloaded method generate unique wsdl:definition/wsdl:binding/wsdl:operation/soap:operation@soapAction suffix which will be base64 encoded method params list. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
9
0 / 0

[JBoss JIRA] Created: (JBWS-3293) Handler not invoked in WS call on the client side when using dispatch and creating service without WSDL

by Richard Opalka (JIRA)

Handler not invoked in WS call on the client side when using dispatch and creating service without WSDL ------------------------------------------------------------------------------------------------------- Key: JBWS-3293 URL: https://issues.jboss.org/browse/JBWS-3293 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.0 Anil Saldhana wrote: --- Hi, In PicketLink, we are creating a Dispatch without considering the WSDL as follows: ============= Service jaxwsService = Service.create(service); jaxwsService.addPort(portName, SOAPBinding.SOAP11HTTP_BINDING, config.getEndPointAddress()); Dispatch<Source> dispatch = jaxwsService.createDispatch(portName, Source.class, Mode.PAYLOAD); ========== Now, I want to inject one of my Jaxws handlers: =========== Binding binding = dispatch.getBinding(); BinaryTokenHandler binaryTokenHandler = new BinaryTokenHandler(); handlers.add(binaryTokenHandler); binding.setHandlerChain(handlers); ============ But the outgoing WS call does not go through my handler. But, if the Dispatch was created with the knowledge of WSDL something like: ============ Service service = Service.create(wsdl, serviceName); WSTest port = service.getPort(new QName("http://ws.trust.test.picketlink.org/", "WSTestBeanPort"), WSTest.class); BindingProvider bp = (BindingProvider)port; bp.getRequestContext().put(SAML2Constants.SAML2_ASSERTION_PROPERTY, assertion); List<Handler> handlers = bp.getBinding().getHandlerChain(); handlers.add(new SAML2Handler()); bp.getBinding().setHandlerChain(handlers); =============== Then I see that the handler is invoked during the WS call on the client side. Any thoughts? This is driving me nuts for 10 days now. :) Regards, Anil --- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-3289) Refactor packages to be in sync. with new abstractions

by Richard Opalka (JIRA)

Refactor packages to be in sync. with new abstractions ------------------------------------------------------ Key: JBWS-3289 URL: https://issues.jboss.org/browse/JBWS-3289 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-4.0.0.Beta1, jbossws-native-4.0.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
6
0 / 0

[JBoss JIRA] Created: (JBWS-3290) Add Schema Validation for SOAP Headers

by Kyle Lape (JIRA)

Add Schema Validation for SOAP Headers -------------------------------------- Key: JBWS-3290 URL: https://issues.jboss.org/browse/JBWS-3290 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Kyle Lape Would like to validate SOAP headers against XML Schemas. This would work similar to how SOAP payloads are currently validated. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3277) Unexpected bytes are serialized in MTOM attachment when the mime type is text/xml

by Jim Ma (JIRA)

Unexpected bytes are serialized in MTOM attachment when the mime type is text/xml --------------------------------------------------------------------------------- Key: JBWS-3277 URL: https://issues.jboss.org/browse/JBWS-3277 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.4.1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-native-4.0 Send the DOMRequest with text/xml mime type content, public class MTOMRequest { private String id; @XmlMimeType("text/xml") protected Source content; public Source getContent() { return content; } Server throws TransformerException : 1:32:46,033 ERROR [STDERR] javax.xml.transform.TransformerException: org.xml.sax.SAXParseException: Content is not allowed in trailing section. 21:32:46,033 ERROR [STDERR] at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:502) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues May 2011