April 2011 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3201) WSConsume does not generate operation fault in WSDL when the WS method throws java.lang.Exception.

by Marek Baluch (JIRA)

WSConsume does not generate operation fault in WSDL when the WS method throws java.lang.Exception. -------------------------------------------------------------------------------------------------- Key: JBWS-3201 URL: https://issues.jboss.org/browse/JBWS-3201 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.1.2 Reporter: Marek Baluch When we have the following WS: @WebService(name="BiddingService", targetNamespace="http://jboss.org/bidding") public class BiddingBackend { // ... @WebMethod(operationName = "makeBid") public Boolean makeBid(@WebParam(name = "itemName") String itemName, @WebParam(name = "offer") Integer offer) throws java.lang.Exception { // ... } } then the generated WSDL does not contain a fault in it's binding. It's as the method would not throw an Exception. If the method throws a descendant of java.lang.Exception then the resulting WSDL contains everything. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-3279) Unify CXFServletExt and CXFNonSpringServletExt

by Alessio Soldano (JIRA)

Unify CXFServletExt and CXFNonSpringServletExt ---------------------------------------------- Key: JBWS-3279 URL: https://issues.jboss.org/browse/JBWS-3279 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Priority: Minor Fix For: jbossws-cxf-4.0 Once the Apache CXF 2.4 integration is done, there's no need anymore for 2 different extensions of the CXF endpoint transport servlet. So we can unify the spring and non-spring version and remove the previously required abstraction in AS integration for selecting the servlet to use when (re)writing the endpoint web.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-3227) handlers configuration file not found on classpath

by Richard Opalka (JIRA)

handlers configuration file not found on classpath -------------------------------------------------- Key: JBWS-3227 URL: https://issues.jboss.org/browse/JBWS-3227 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Richard Opalka Fix For: jbossws-native-4.0, jbossws-cxf-4.0 12:03:31,683 ERROR [org.jboss.msc] (pool-2-thread-5) MSC-00001: Failed to start service jboss.deployment.unit.jaxws-jbws3034.war.INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit.jaxws-jbws3034.war.INSTALL: Failed to process phase INSTALL of deployment "jaxws-jbws3034.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:112) 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: javax.xml.ws.WebServiceException: javax.xml.ws.WebServiceException: Could not find the handler configuration file ../../../../../../handlers.xml specified by @HandlerChain annotation at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:343) [cxf-rt-frontend-jaxws.jar:2.3.2] at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:62) [jbossws-cxf-server.jar:4.0.0-SNAPSHOT] at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:239) [cxf-rt-frontend-jaxws.jar:2.3.2] at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:489) [cxf-rt-frontend-jaxws.jar:2.3.2] at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:112) [jbossws-cxf-server.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:102) [jbossws-cxf-server.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:119) [jbossws-cxf-server.jar:4.0.0-SNAPSHOT] at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.internalDeploy(AspectDeploymentProcessor.java:77) [jboss-as-webservices-server-integration-7.0.0.Alpha2-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.jboss.as.webservices.deployers.TCCLDeploymentProcessor.deploy(TCCLDeploymentProcessor.java:41) [jboss-as-webservices-server-integration-7.0.0.Alpha2-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108) ... 4 more Caused by: javax.xml.ws.WebServiceException: Could not find the handler configuration file ../../../../../../handlers.xml specified by @HandlerChain annotation at org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilder.buildHandlerChainFromClass(AnnotationHandlerChainBuilder.java:88) [cxf-rt-frontend-jaxws.jar:2.3.2] at org.apache.cxf.jaxws.handler.AnnotationHandlerChainBuilder.buildHandlerChainFromClass(AnnotationHandlerChainBuilder.java:284) [cxf-rt-frontend-jaxws.jar:2.3.2] at org.apache.cxf.jaxws.JaxWsServerFactoryBean.buildHandlerChain(JaxWsServerFactoryBean.java:215) [cxf-rt-frontend-jaxws.jar:2.3.2] at org.apache.cxf.jaxws.JaxWsServerFactoryBean.init(JaxWsServerFactoryBean.java:194) [cxf-rt-frontend-jaxws.jar:2.3.2] at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:184) [cxf-rt-frontend-jaxws.jar:2.3.2] at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:415) [cxf-rt-frontend-jaxws.jar:2.3.2] at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:315) [cxf-rt-frontend-jaxws.jar:2.3.2] ... 13 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2317) $JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing to re-create classes.

by Darran Lofthouse (JIRA)

$JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing to re-create classes. ------------------------------------------------------------------------------------------- Key: JBWS-2317 URL: https://jira.jboss.org/jira/browse/JBWS-2317 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro, jbossws-native Affects Versions: jbossws-metro-3.0.3, jbossws-native-3.0.3 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.0.4, jbossws-metro-3.0.4 The JAXB implementation contains a package of classes to optimise field and method access by dynamically generating classes to avoid reflection, this has a start-up performance hit but then leads to an optimised runtime. The package is: - 'com.sun.xml.bind.v2.runtime.reflect.opt' Within the Injector class is a HashMap to maintain a cache of these classes against the classloader they were created for: - private static final Map<ClassLoader,WeakReference<Injector>> injectors = Collections.synchronizedMap(new WeakHashMap<ClassLoader,WeakReference<Injector>>()); A WeakReference has been used to wrap the value to prevent the value retaining a reference to the ClassLoader and then preventing garbage collection and leading to a leak. The problem is that nothing retains a reference to the Injector so as this is wrapped with a WeakReference it is garbage collected. I will attach to this case a new version of Injector.java. The fix switches to using a Strong reference to the Injector so it is not garbage collected. To maintain the original requirements the Injector will no longer hold a reference to the ClassLoader and will instead make use of the one passed in. Within the Injector the HashMap of classes will reference the Class with a WeakReference. If we get a WeakReference with no class it means the class was previously loaded but garbage collected, in this case try to load the class by name from the classloader - if this fails then redefine the class. -- 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, 6 months

3
9
0 / 0

[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, 6 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, 6 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, 6 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, 6 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, 6 months

2
9
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, 7 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 April 2011