June 2014 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3806) Update deploy scripts to work with WFLY module.xml files using Maven artifact references

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3806?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3806: ---------------------------------- Fix Version/s: (was: jbossws-cxf-5.0) > Update deploy scripts to work with WFLY module.xml files using Maven artifact references > ---------------------------------------------------------------------------------------- > > Key: JBWS-3806 > URL: https://issues.jboss.org/browse/JBWS-3806 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > > WildFly master current builds into a distribution containing module.xml files that have references to Maven artifacts instead of local resource root jars. > The JBossWS deploy scripts hence needs to be updated accordingly. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3807) Move wsconsume execution to generate-test-sources phase of the build

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3807: ------------------------------------- Summary: Move wsconsume execution to generate-test-sources phase of the build Key: JBWS-3807 URL: https://issues.jboss.org/browse/JBWS-3807 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Components: jbossws-cxf, productization Reporter: Alessio Soldano Assignee: Alessio Soldano Priority: Minor Fix For: jbossws-cxf-5.0 The JBossWS-CXF build includes invocation of wsconsume Ant task to generate a client for some wsdl contracts. The task is currently run in generate-sources maven phase, instead of generate-test-sources, resulting in two executions for each build. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3806) Update deploy scripts to work with WFLY module.xml files using Maven artifact references

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3806: ------------------------------------- Summary: Update deploy scripts to work with WFLY module.xml files using Maven artifact references Key: JBWS-3806 URL: https://issues.jboss.org/browse/JBWS-3806 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-5.0 WildFly master current builds into a distribution containing module.xml files that have references to Maven artifacts instead of local resource root jars. The JBossWS deploy scripts hence needs to be updated accordingly. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3628) Add property expansion capability to .wsdl files

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-3628?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-3628: -------------------------------- The current proposed enhancement from cxf 2.7.11 will not work for CXF 3.0.0. This version of CXF is blocking access to the value of any wsdl "extension" stmt such as JndiConnectionFactoryNameType, JndiInitialContextFactoryType, and JndiURLType. It is doing this by generating on the fly proprietary classes using org.apache.cxf.common.util.ASMHelper, These classes JndiConnectionFactoryNameTypeExtensibility, JndiInitialContextFactoryTypeExtensibility, and JndiURLTypeExtensibility, provide access to all "extension" information except the value. WSDLManagerImpl loads from the bus an extension class ConfiguredBeanLocator. JAXBExtensionHelper is eventually called. This class has method, createExtensionClass which uses org.apache.cxf.common.util.ASMHelper to generate an alternate "extension" class on the fly. There is a serializer and deserializer associated with each class preforms the read and write the xml element. > Add property expansion capability to .wsdl files > ------------------------------------------------ > > Key: JBWS-3628 > URL: https://issues.jboss.org/browse/JBWS-3628 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: david.boeren > Assignee: R Searls > Priority: Minor > Fix For: jbossws-cxf-5.0 > > Attachments: JBWS-3628-JBossWS-WSDLFactory-tentative-patch.txt, JBWS-3628-tentative-patch-from-Rebecca.txt > > > The customer is doing JMS-based webservices using the following declarations in their wsdl file (referred to using the wsdllocation annotation): > <soapjms:jndiConnectionFactoryName>myqueue</soapjms:jndiConnectionFactoryName> <soapjms:jndiInitialContextFactory>com.vendor.InitialContextFactory</soapjms:jndiInitialContextFactory> > <soapjms:jndiURL>$MY_URL</soapjms:jndiURL> > The $MY_URL is the url of the messaging server. Since property replacement does not work for wsdl files they need to manually modify this before deploying and package separate versions of their app for each environment. If property expansion worked in the .wsdl this would no longer be necessary. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3805) Allow overriding soap:address rewrite options in jboss-webservices.xml

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3805: ------------------------------------- Summary: Allow overriding soap:address rewrite options in jboss-webservices.xml Key: JBWS-3805 URL: https://issues.jboss.org/browse/JBWS-3805 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-5.0 We should make is possible to override the soap:address rewrite configuration options in the management model with values in a deployement descriptor (jboss-webservices.xml). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3804) Remove some DeploymentAspect which is not needed

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3804?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-3804: ------------------------- Summary: Remove some DeploymentAspect which is not needed (was: Review DeploymentAspect is still needed) > Remove some DeploymentAspect which is not needed > ------------------------------------------------- > > Key: JBWS-3804 > URL: https://issues.jboss.org/browse/JBWS-3804 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: jbossws-cxf-5.0 > > > ResourceResolver is added to Endpoint in ResourceResolverDeploymentAspect , but BusDeploymentAspect retrieves resourceResolver directly from deployment. So ResourceResolverDeploymentAspectbe can be removed now. We need to look at if there is other DeploymentAspect should be removed and refactored a bit. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3804) Review DeploymentAspect is still needed

by Jim Ma (JIRA)

Jim Ma created JBWS-3804: ---------------------------- Summary: Review DeploymentAspect is still needed Key: JBWS-3804 URL: https://issues.jboss.org/browse/JBWS-3804 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-4.3 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-5.0 ResourceResolver is added to Endpoint in ResourceResolverDeploymentAspect , but BusDeploymentAspect retrieves resourceResolver directly from deployment. So ResourceResolverDeploymentAspectbe can be removed now. We need to look at if there is other DeploymentAspect should be removed and refactored a bit. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3802) Empty response returned when SOAP Fault is thrown from an endpoint having WS-Security Policy Signature profile

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3802?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBWS-3802: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1110631, https://bugzilla.redhat.com/show_bug.cgi?id=1111046, https://bugzilla.redhat.com/show_bug.cgi?id=1111048, https://bugzilla.redhat.com/show_bug.cgi?id=1111518 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1110631, https://bugzilla.redhat.com/show_bug.cgi?id=1111046, https://bugzilla.redhat.com/show_bug.cgi?id=1111048) > Empty response returned when SOAP Fault is thrown from an endpoint having WS-Security Policy Signature profile > -------------------------------------------------------------------------------------------------------------- > > Key: JBWS-3802 > URL: https://issues.jboss.org/browse/JBWS-3802 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.4, jbossws-cxf-4.3 > Reporter: Tadayoshi Sato > > Please port [CXF-5810|https://issues.apache.org/jira/browse/CXF-5810], which is the root cause of the issue, to JBoss WS. > When a web service has a WS-Security Signature policy in its WSDL and throws a SOAP Fault, it returns an empty HTTP response that has zero-length of content to client instead of the SOAP Fault. > This happens only with Signature policy and doesn't happen with any other WS-Security policies like UsernameToken, or without WS-Security. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3628) Add property expansion capability to .wsdl files

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3628?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3628: --------------------------------------- There's no need for any change in CXF in order for using a custom WSDLFactory. We can simply set the javax.wsdl.factory.WSDLFactory system property or add a proper META-INF/services/javax.wsdl.factory.WSDLFactory entry in our jbossws-cxf-client jar. > Add property expansion capability to .wsdl files > ------------------------------------------------ > > Key: JBWS-3628 > URL: https://issues.jboss.org/browse/JBWS-3628 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: david.boeren > Assignee: R Searls > Priority: Minor > Fix For: jbossws-cxf-5.0 > > Attachments: JBWS-3628-JBossWS-WSDLFactory-tentative-patch.txt, JBWS-3628-tentative-patch-from-Rebecca.txt > > > The customer is doing JMS-based webservices using the following declarations in their wsdl file (referred to using the wsdllocation annotation): > <soapjms:jndiConnectionFactoryName>myqueue</soapjms:jndiConnectionFactoryName> <soapjms:jndiInitialContextFactory>com.vendor.InitialContextFactory</soapjms:jndiInitialContextFactory> > <soapjms:jndiURL>$MY_URL</soapjms:jndiURL> > The $MY_URL is the url of the messaging server. Since property replacement does not work for wsdl files they need to manually modify this before deploying and package separate versions of their app for each environment. If property expansion worked in the .wsdl this would no longer be necessary. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3773) HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3773?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3773: ----------------------------------------------- Jan Blizňák <jbliznak(a)redhat.com> changed the Status of [bug 1077262|https://bugzilla.redhat.com/show_bug.cgi?id=1077262] from ON_QA to VERIFIED > HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set > ------------------------------------------------------------------------------ > > Key: JBWS-3773 > URL: https://issues.jboss.org/browse/JBWS-3773 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3.1, jbossws-cxf-5.0 > > > See https://issues.apache.org/jira/browse/CXF-5602 > The HttpServletContext retrieved from the WebServiceContext can have stale values when running on AS 7 (using JBossWeb) and processing WS-Addressing requests with non generic ReplyTo header props. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 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 June 2014