February 2012 - jbossws-issues - Jboss List Archives

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

1
6
0 / 0

[JBoss JIRA] Created: (JBWS-3249) Restore UsernameAuthorizationCustomFileTestCase on AS7

by Alessio Soldano (JIRA)

Restore UsernameAuthorizationCustomFileTestCase on AS7 ------------------------------------------------------ Key: JBWS-3249 URL: https://issues.jboss.org/browse/JBWS-3249 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 16:37:27,699 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."jaxws-samples-wsse-username-authorize-custom.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-samples-wsse-username-authorize-custom.war".INSTALL: Failed to process phase INSTALL of deployment "jaxws-samples-wsse-username-authorize-custom.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:109) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21] at java.lang.Thread.run(Thread.java:619) [:1.6.0_21] Caused by: java.lang.RuntimeException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'SecurityContextIn' defined in resource loaded through InputStream: Error setting property values; nested exception is org.springframework.beans.PropertyBatchUpdateException; nested PropertyAccessExceptions (1) are: PropertyAccessException 1: org.springframework.beans.MethodInvocationException: Property 'securityConfigFile' threw exception; nested exception is java.lang.SecurityException: Unable to load the configuration file login-config.xml at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:102) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:137) at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.internalDeploy(AspectDeploymentProcessor.java:77) at org.jboss.as.webservices.deployers.TCCLDeploymentProcessor.deploy(TCCLDeploymentProcessor.java:42) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:103) ... 4 more Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'SecurityContextIn' defined in resource loaded through InputStream: Error setting property values; nested exception is org.springframework.beans.PropertyBatchUpdateException; nested PropertyAccessExceptions (1) are: PropertyAccessException 1: org.springframework.beans.MethodInvocationException: Property 'securityConfigFile' threw exception; nested exception is java.lang.SecurityException: Unable to load the configuration file login-config.xml at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1361) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1086) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:517) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:580) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425) at org.jboss.wsf.stack.cxf.configuration.SpringBusHolder.loadAdditionalConfig(SpringBusHolder.java:179) at org.jboss.wsf.stack.cxf.configuration.SpringBusHolder.configure(SpringBusHolder.java:129) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:98) ... 8 more Caused by: org.springframework.beans.PropertyBatchUpdateException; nested PropertyAccessExceptions (1) are: PropertyAccessException 1: org.springframework.beans.MethodInvocationException: Property 'securityConfigFile' threw exception; nested exception is java.lang.SecurityException: Unable to load the configuration file login-config.xml at org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(AbstractPropertyAccessor.java:102) at org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(AbstractPropertyAccessor.java:58) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1358) ... 21 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
3
0 / 0

[JBoss JIRA] (JBWS-3432) WebservicesFactory can't parse webservices.xml with javaee:descriptionGroup references

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3432?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3432: --------------------------------------- Jim, this can be marked as solved, right? > WebservicesFactory can't parse webservices.xml with javaee:descriptionGroup references > -------------------------------------------------------------------------------------- > > Key: JBWS-3432 > URL: https://issues.jboss.org/browse/JBWS-3432 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration, jbossws-native > Reporter: Peter Skopek > Assignee: Jim Ma > Fix For: jbossws-cxf-4.0.2, jbossws-native-4.0.2 > > Attachments: picketlink-sts.war > > > webservices.xml with proper structure is refused to deploy due to parsing/validation error > {noformat} > <?xml version="1.0" encoding="UTF-8"?> > <webservices xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_web_services_1_3.xsd" > version="1.3"> > <description>PicketLink STS web service descriptor > </description> > <webservice-description> > <webservice-description-name> > PicketLinkSTS > </webservice-description-name> > <wsdl-file> > WEB-INF/wsdl/PicketLinkSTS.wsdl > </wsdl-file> > <port-component> > <description>PicketLink STS Port</description> > <port-component-name>PicketLinkSTSPort</port-component-name> > <wsdl-port xmlns:tns="urn:picketlink:identity-federation:sts">PicketLinkSTSPort</wsdl-port> >  > <service-impl-bean> > <servlet-link>PicketLinkSTS</servlet-link> > </service-impl-bean> > </port-component> > </webservice-description> > </webservices> > {noformat} > Deployer complains about both description tags (webservices/description and webservices/webservice-description/port-component/description). > See exception: > {noformat} > 18:46:59,061 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."picketlink-sts.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."picketlink-sts.war".PARSE: Failed to process phase PARSE of deployment "picketlink-sts.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] > Caused by: javax.xml.ws.WebServiceException: Failed to unmarshall:vfs:/content/picketlink-sts.war/WEB-INF/webservices.xml > at org.jboss.wsf.spi.metadata.webservices.WebservicesFactory.load(WebservicesFactory.java:143) > at org.jboss.wsf.spi.metadata.webservices.WebservicesFactory.loadFromVFSRoot(WebservicesFactory.java:126) > at org.jboss.as.webservices.deployers.WebservicesDescriptorDeploymentProcessor.deploy(WebservicesDescriptorDeploymentProcessor.java:48) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] > ... 5 more > Caused by: java.lang.IllegalStateException: Unexpected element: description > at org.jboss.wsf.spi.metadata.webservices.WebservicesFactory.parseWebservices(WebservicesFactory.java:237) > at org.jboss.wsf.spi.metadata.webservices.WebservicesFactory.parse(WebservicesFactory.java:203) > at org.jboss.wsf.spi.metadata.webservices.WebservicesFactory.load(WebservicesFactory.java:139) > ... 8 more > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3440) wsconsume chokes on wsdl containing element referring its schema

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3440: ------------------------------------- Summary: wsconsume chokes on wsdl containing element referring its schema Key: JBWS-3440 URL: https://issues.jboss.org/browse/JBWS-3440 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-4.0.2 This is basically the issue mentioned at http://stackoverflow.com/questions/7148591/microsoft-webservice-and-cxf-c... . The wsconsume (internally relying on CXF tooling) is failing to process wsdls containing <s:element ref="s:schema" /> where s:schema is the schema s:element is defined into. This looks to be an interoperability issue with Microsoft generated contracts. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
2
0 / 0

[JBoss JIRA] (JBWS-3442) Verify dependencies are up to date

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3442: ------------------------------------- Summary: Verify dependencies are up to date Key: JBWS-3442 URL: https://issues.jboss.org/browse/JBWS-3442 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Reporter: Alessio Soldano Assignee: Richard Opalka Fix For: jbossws-cxf-4.0.2, jbossws-native-4.0.2 This is a general task for checking the jbossws cxf/native dependencies are up to date / in synch with AS 710 after its release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3438) JAX-RPC & JAX-WS generated proxies have to be de/serializable

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3438: ------------------------------------ Summary: JAX-RPC & JAX-WS generated proxies have to be de/serializable Key: JBWS-3438 URL: https://issues.jboss.org/browse/JBWS-3438 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-4.0.2, jbossws-native-4.0.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
1
0 / 0

[JBoss JIRA] (JBWS-3437) WS Refs have to keep classloader reference

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3437: ------------------------------------ Summary: WS Refs have to keep classloader reference Key: JBWS-3437 URL: https://issues.jboss.org/browse/JBWS-3437 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-4.0.2, jbossws-native-4.0.2 WS Refs have to keep class loader reference because when calling WS refs using remote JNDI protocol the classloader that is available is associated with remote naming protocol module. In order to have access to application classloader we need to store its reference. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3436) Set Apache WSS4J and Santuario direct dependencies

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3436: ------------------------------------- Summary: Set Apache WSS4J and Santuario direct dependencies Key: JBWS-3436 URL: https://issues.jboss.org/browse/JBWS-3436 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano We need direct control in the jbossws-cxf pom.xml / build on the wss4j and xmlsec versions that are pulled in. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3424) CXF does not return status code 200 when Oneway webservice is invoked via HTTP

by Magesh Bojan (JIRA)

Magesh Bojan created JBWS-3424: ---------------------------------- Summary: CXF does not return status code 200 when Oneway webservice is invoked via HTTP Key: JBWS-3424 URL: https://issues.jboss.org/browse/JBWS-3424 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-4.0 Reporter: Magesh Bojan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

4
10
0 / 0

[JBoss JIRA] (JBWS-3433) Upgrade to Apache CXF 2.5.2

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3433: ------------------------------------- Summary: Upgrade to Apache CXF 2.5.2 Key: JBWS-3433 URL: https://issues.jboss.org/browse/JBWS-3433 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues February 2012