May 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3648) WS-Policy code-first improvements and tooling

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3648: ------------------------------------- Summary: WS-Policy code-first improvements and tooling Key: JBWS-3648 URL: https://issues.jboss.org/browse/JBWS-3648 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, productivity Reporter: Alessio Soldano Fix For: jbossws-cxf-4.3 I'd like to see some kind of ws-policy oriented tooling in JBossWS. Ideally we should provide some mechanisms for basic code-first development; currently stuff like ws-security configuration through policies is actually contract based: the user is expected to either provide a wsdl with proper policies or to use policy attachment, which is basically the same, writing the actual policy assertion is required. An idea could be to have a group of pre-defined policy assertions' sets for known scenarios (for ws-security those could be based e.g. on the Oasis WS-Security Policy Examples [1]). Each set would be composed of 'placement points' with a policy to be attached at each of those points. We'd then possibly have a custom CXF FactoryBeanListener to be registered in the FactoryBeanListenerManager; the new listener would perform something similar to what the PolicyAnnotationListener does (based on the @Policies/@Policy in the code), that is attaching policies to the proper attach points. An additional step would be to support merging (effective policy through Neethi?) multiple sets at the same time (say, you want e.g. a specific ws-security set plus a ws-rm set). With such thing, we could provide the initial sets and let users pick the sets they want for a given endpoint (perhaps through a custom annotation, or possibly better specifying the sets' names within a property in a selected Endpoint Config). The initial policy sets could be stored as xml files in one of the jbossws-cxf jars and we could provide a mechanism for reading additional ones from the current classpath (to let users add additional ones). Finally, this would open up to further tooling improvements; e.g. 1) wsprovide could be enhanced to process the @EndpointConfig annotation, get the policy sets and produce a ws-policy enabled wsdl, 2) we could even provide an 'educational' gui tool showing assertions enabled/disabled depending on the selected sets, etc. [1] http://docs.oasis-open.org/ws-sx/security-policy/examples/ws-sp-usecases-... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3647) Client/EndpointConfig in ServerConfig should be fully thread-safe lists

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3647: ------------------------------------- Summary: Client/EndpointConfig in ServerConfig should be fully thread-safe lists Key: JBWS-3647 URL: https://issues.jboss.org/browse/JBWS-3647 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-cxf-4.1.0.Final Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3645) WorkQueueManager is not registered in JMX Server when cxf.management is enabled

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3645?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-3645: ------------------------- Description: MBean of WorkQueueManger is not registered when If cxf.management is enabled in jboss-webservices.xml. was: If the cxf.management is enabled from jboss-webservices.xml, the MBean of WorkQueueManger is not registered. When I force to register this Bean, there is exception thrown. It's possibly a bug in apache cxf: 00:08:28,155 ERROR [stderr] (MSC service thread 1-1) javax.management.NotCompliantMBeanException: MBean class org.apache.cxf.bus.managers.WorkQueueImplMBeanWrapper does not implement DynamicMBean, and neither follows the Standard MBean conventions (javax.management.NotCompliantMBeanException: Class org.apache.cxf.bus.managers.WorkQueueImplMBeanWrapper is not a JMX compliant Standard MBean) nor the MXBean conventions (javax.management.NotCompliantMBeanException: org.apache.cxf.bus.managers.WorkQueueImplMBeanWrapper: Class org.apache.cxf.bus.managers.WorkQueueImplMBeanWrapper is not a JMX compliant MXBean) 00:08:28,155 ERROR [stderr] (MSC service thread 1-1) at com.sun.jmx.mbeanserver.Introspector.checkCompliance(Introspector.java:173) 00:08:28,156 ERROR [stderr] (MSC service thread 1-1) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:317) 00:08:28,156 ERROR [stderr] (MSC service thread 1-1) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:513) 00:08:28,156 ERROR [stderr] (MSC service thread 1-1) at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.registerMBean(PluggableMBeanServerImpl.java:552) 00:08:28,157 ERROR [stderr] (MSC service thread 1-1) at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:320) 00:08:28,157 ERROR [stderr] (MSC service thread 1-1) at org.apache.cxf.management.jmx.InstrumentationManagerImpl.registerMBeanWithServer(InstrumentationManagerImpl.java:331) 00:08:28,157 ERROR [stderr] (MSC service thread 1-1) at org.apache.cxf.management.jmx.InstrumentationManagerImpl.register(InstrumentationManagerImpl.java:229) 00:08:28,158 ERROR [stderr] (MSC service thread 1-1) at org.apache.cxf.management.jmx.InstrumentationManagerImpl.register(InstrumentationManagerImpl.java:246) 00:08:28,158 ERROR [stderr] (MSC service thread 1-1) at org.apache.cxf.management.jmx.InstrumentationManagerImpl.register(InstrumentationManagerImpl.java:239) 00:08:28,158 ERROR [stderr] (MSC service thread 1-1) at org.apache.cxf.bus.managers.WorkQueueManagerImpl.addNamedWorkQueue(WorkQueueManagerImpl.java:188) 00:08:28,159 ERROR [stderr] (MSC service thread 1-1) at org.jboss.wsf.stack.cxf.configuration.BusHolder.setAdditionalWorkQueues(BusHolder.java:197) 00:08:28,159 ERROR [stderr] (MSC service thread 1-1) at org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:112) 00:08:28,159 ERROR [stderr] (MSC service thread 1-1) at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:90) 00:08:28,160 ERROR [stderr] (MSC service thread 1-1) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:129) 00:08:28,160 ERROR [stderr] (MSC service thread 1-1) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:67) 00:08:28,160 ERROR [stderr] (MSC service thread 1-1) at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:75) 00:08:28,161 ERROR [stderr] (MSC service thread 1-1) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) 00:08:28,161 ERROR [stderr] (MSC service thread 1-1) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) 00:08:28,161 ERROR [stderr] (MSC service thread 1-1) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) 00:08:28,162 ERROR [stderr] (MSC service thread 1-1) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 00:08:28,162 ERROR [stderr] (MSC service thread 1-1) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 00:08:28,162 ERROR [stderr] (MSC service thread 1-1) at java.lang.Thread.run(Thread.java:722) > WorkQueueManager is not registered in JMX Server when cxf.management is enabled > ------------------------------------------------------------------------------- > > Key: JBWS-3645 > URL: https://issues.jboss.org/browse/JBWS-3645 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.1.3 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: jbossws-cxf-4.2 > > > MBean of WorkQueueManger is not registered when If cxf.management is enabled in jboss-webservices.xml. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3645) WorkQueueManager is not registered in JMX Server when cxf.management is enabled

by Jim Ma (JIRA)

Jim Ma created JBWS-3645: ---------------------------- Summary: WorkQueueManager is not registered in JMX Server when cxf.management is enabled Key: JBWS-3645 URL: https://issues.jboss.org/browse/JBWS-3645 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-4.1.3 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.2 If the cxf.management is enabled from jboss-webservices.xml, the MBean of WorkQueueManger is not registered. When I force to register this Bean, there is exception thrown. It's possibly a bug in apache cxf: 00:08:28,155 ERROR [stderr] (MSC service thread 1-1) javax.management.NotCompliantMBeanException: MBean class org.apache.cxf.bus.managers.WorkQueueImplMBeanWrapper does not implement DynamicMBean, and neither follows the Standard MBean conventions (javax.management.NotCompliantMBeanException: Class org.apache.cxf.bus.managers.WorkQueueImplMBeanWrapper is not a JMX compliant Standard MBean) nor the MXBean conventions (javax.management.NotCompliantMBeanException: org.apache.cxf.bus.managers.WorkQueueImplMBeanWrapper: Class org.apache.cxf.bus.managers.WorkQueueImplMBeanWrapper is not a JMX compliant MXBean) 00:08:28,155 ERROR [stderr] (MSC service thread 1-1) at com.sun.jmx.mbeanserver.Introspector.checkCompliance(Introspector.java:173) 00:08:28,156 ERROR [stderr] (MSC service thread 1-1) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:317) 00:08:28,156 ERROR [stderr] (MSC service thread 1-1) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:513) 00:08:28,156 ERROR [stderr] (MSC service thread 1-1) at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.registerMBean(PluggableMBeanServerImpl.java:552) 00:08:28,157 ERROR [stderr] (MSC service thread 1-1) at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:320) 00:08:28,157 ERROR [stderr] (MSC service thread 1-1) at org.apache.cxf.management.jmx.InstrumentationManagerImpl.registerMBeanWithServer(InstrumentationManagerImpl.java:331) 00:08:28,157 ERROR [stderr] (MSC service thread 1-1) at org.apache.cxf.management.jmx.InstrumentationManagerImpl.register(InstrumentationManagerImpl.java:229) 00:08:28,158 ERROR [stderr] (MSC service thread 1-1) at org.apache.cxf.management.jmx.InstrumentationManagerImpl.register(InstrumentationManagerImpl.java:246) 00:08:28,158 ERROR [stderr] (MSC service thread 1-1) at org.apache.cxf.management.jmx.InstrumentationManagerImpl.register(InstrumentationManagerImpl.java:239) 00:08:28,158 ERROR [stderr] (MSC service thread 1-1) at org.apache.cxf.bus.managers.WorkQueueManagerImpl.addNamedWorkQueue(WorkQueueManagerImpl.java:188) 00:08:28,159 ERROR [stderr] (MSC service thread 1-1) at org.jboss.wsf.stack.cxf.configuration.BusHolder.setAdditionalWorkQueues(BusHolder.java:197) 00:08:28,159 ERROR [stderr] (MSC service thread 1-1) at org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:112) 00:08:28,159 ERROR [stderr] (MSC service thread 1-1) at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:90) 00:08:28,160 ERROR [stderr] (MSC service thread 1-1) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:129) 00:08:28,160 ERROR [stderr] (MSC service thread 1-1) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:67) 00:08:28,160 ERROR [stderr] (MSC service thread 1-1) at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:75) 00:08:28,161 ERROR [stderr] (MSC service thread 1-1) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) 00:08:28,161 ERROR [stderr] (MSC service thread 1-1) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) 00:08:28,161 ERROR [stderr] (MSC service thread 1-1) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) 00:08:28,162 ERROR [stderr] (MSC service thread 1-1) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 00:08:28,162 ERROR [stderr] (MSC service thread 1-1) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 00:08:28,162 ERROR [stderr] (MSC service thread 1-1) at java.lang.Thread.run(Thread.java:722) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3644) Review SPI resolution mechanism

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3644: ------------------------------------- Summary: Review SPI resolution mechanism Key: JBWS-3644 URL: https://issues.jboss.org/browse/JBWS-3644 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.2 See thread at http://lists.jboss.org/pipermail/jbossws-dev/2013-May/002163.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3643) Review EndpointRegistry container integration

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3643?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3643: ---------------------------------- Issue Type: Task (was: Feature Request) > Review EndpointRegistry container integration > --------------------------------------------- > > Key: JBWS-3643 > URL: https://issues.jboss.org/browse/JBWS-3643 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > See thread at http://lists.jboss.org/pipermail/jbossws-dev/2013-May/002163.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3643) Review EndpointRegistry container integration

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3643: ------------------------------------- Summary: Review EndpointRegistry container integration Key: JBWS-3643 URL: https://issues.jboss.org/browse/JBWS-3643 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Fix For: jbossws-cxf-4.2 See thread at http://lists.jboss.org/pipermail/jbossws-dev/2013-May/002163.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3569) WSDL produced for a multi-port service contains invalid port addresses in clustered configuration

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3569?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3569: ----------------------------------------------- Honza Fnukal <hfnukal(a)redhat.com> made a comment on [bug 905410|https://bugzilla.redhat.com/show_bug.cgi?id=905410] Fixed in EAP 6.1.0. There is jbossws 4.1.3 > WSDL produced for a multi-port service contains invalid port addresses in clustered configuration > ------------------------------------------------------------------------------------------------- > > Key: JBWS-3569 > URL: https://issues.jboss.org/browse/JBWS-3569 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Chris Laprun > Assignee: Alessio Soldano > Priority: Critical > Fix For: jbossws-cxf-4.1.1 > > > Using a loadbalancer fronted cluster and the loadbalancer URL for the WSDL results in ports containing the node URLs instead of the loadbalancer's. > I've tried using the dynamic WSDL rewriting as described in https://docs.jboss.org/author/display/AS71/Advanced+User+Guide but this results in invalid URLs for the ports (with {{jbossws.undefined.host}} as the host name *and* the cluster node port) that haven't been used to access the WSDL, the port used to access the WSDL has the proper address though. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3569) WSDL produced for a multi-port service contains invalid port addresses in clustered configuration

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3569?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3569: ----------------------------------------------- Honza Fnukal <hfnukal(a)redhat.com> changed the Status of [bug 905410|https://bugzilla.redhat.com/show_bug.cgi?id=905410] from ASSIGNED to ON_QA > WSDL produced for a multi-port service contains invalid port addresses in clustered configuration > ------------------------------------------------------------------------------------------------- > > Key: JBWS-3569 > URL: https://issues.jboss.org/browse/JBWS-3569 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Chris Laprun > Assignee: Alessio Soldano > Priority: Critical > Fix For: jbossws-cxf-4.1.1 > > > Using a loadbalancer fronted cluster and the loadbalancer URL for the WSDL results in ports containing the node URLs instead of the loadbalancer's. > I've tried using the dynamic WSDL rewriting as described in https://docs.jboss.org/author/display/AS71/Advanced+User+Guide but this results in invalid URLs for the ports (with {{jbossws.undefined.host}} as the host name *and* the cluster node port) that haven't been used to access the WSDL, the port used to access the WSDL has the proper address though. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3641) cxf InInterceptors annotation not firing

by David Lin (JIRA)

[ https://issues.jboss.org/browse/JBWS-3641?page=com.atlassian.jira.plugin.... ] David Lin edited comment on JBWS-3641 at 5/22/13 8:58 PM: ---------------------------------------------------------- Please see the attached source code, it is deployed as war file was (Author: dlin12): Please see the attached maven project > cxf InInterceptors annotation not firing > ---------------------------------------- > > Key: JBWS-3641 > URL: https://issues.jboss.org/browse/JBWS-3641 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Environment: jboss 7.1.1 final > jdk 1.6.0_43 > mac os 10.6.8 > Reporter: David Lin > Labels: annotation, interceptor > Attachments: hellows.tar > > > Implement the web service using the jax-ws with cxf InInterceptor as following > @WebService(serviceName = "HelloService", > portName = "HelloServicePort", > name = "HelloService", > endpointInterface = "simple.service.HelloService", > targetNamespace = "urn:common:hello") > @InInterceptors(interceptors="org.apache.cxf.interceptor.LoggingInInterceptor") > public class HelloServiceImpl implements HelloService { > @WebMethod > public String sayHello() { > return "Hello World"; > } > } > The META-INF/MANIFEST.MF is as following > Manifest-Version: 1.0 > Dependencies: org.jboss.ws.cxf.jbossws-cxf-client services export > The web service is working fine but the interceptor is not firing. Tested in jboss 7.1.1 Final and 7.1.0 Final. > The jbossws-cxf module does no have the test case for the interceptor annotation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 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 May 2013