November 2014 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3850) Move SubjectCreatingPolicyInterceptor to PRE_PROTOCOL interceptor phase

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3850?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3850: ---------------------------------- Fix Version/s: jbossws-cxf-5.0.0.Beta2 (was: jbossws-cxf-5.0) > Move SubjectCreatingPolicyInterceptor to PRE_PROTOCOL interceptor phase > ----------------------------------------------------------------------- > > Key: JBWS-3850 > URL: https://issues.jboss.org/browse/JBWS-3850 > Project: JBoss Web Services > Issue Type: Enhancement > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0.0.Beta2 > > > We should move the SubjectCreatingPolicyInterceptor to PRE_PROTOCOL interceptor phase. That would make it to run before the HandlerAuthInterceptor, hence allowing WS-Security based authentication before handlers auth check and execution. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3803) Revisit doc on running JBWS testsuite in IDE

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3803?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3803: ---------------------------------- Fix Version/s: jbossws-cxf-5.0.0.Beta2 (was: jbossws-cxf-5.0) > Revisit doc on running JBWS testsuite in IDE > -------------------------------------------- > > Key: JBWS-3803 > URL: https://issues.jboss.org/browse/JBWS-3803 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf, productivity > Reporter: Alessio Soldano > Assignee: R Searls > Fix For: jbossws-cxf-5.0.0.Beta2 > > > At the time of JBossWS 3, we put some efforts on the IDE integration and the page at [1] was produced. That page basically does not apply anymore; we need to provide proper directions on how to run the jbossws testsuite in the IDE nowadays (with the eclipse / maven plugins we have today and the current project structure). > The last part of the old webpage is about the project generation, which is to be replaced by the jbossws maven archetype, so that's not part of the task here. > [1] https://community.jboss.org/wiki/JBossWS-SetupyourIDE -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3841) Upgrade to Woodstox 4.4.1

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3841?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3841: ---------------------------------- Fix Version/s: jbossws-cxf-5.0.0.Beta2 (was: jbossws-cxf-5.0) > Upgrade to Woodstox 4.4.1 > ------------------------- > > Key: JBWS-3841 > URL: https://issues.jboss.org/browse/JBWS-3841 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3851) WSDL publisher incorrectly attempt to publish external HTTPS schema import

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3851?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3851: ---------------------------------- Fix Version/s: jbossws-cxf-5.0.0.Beta2 (was: jbossws-cxf-5.0) > WSDL publisher incorrectly attempt to publish external HTTPS schema import > -------------------------------------------------------------------------- > > Key: JBWS-3851 > URL: https://issues.jboss.org/browse/JBWS-3851 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3 > Reporter: R Searls > Assignee: R Searls > Fix For: jbossws-cxf-5.0.0.Beta2 > > > WSDL publisher incorrectly attempt to publish external HTTPS schema import > See lone 210 in src/main/java/org/jboss/ws/common/utils/AbstractWSDLFilePublisher.java > repo https://svn.jboss.org/repos/jbossws/common/trunk > 210 if (schemaLocation.length() > 0 && schemaLocation.startsWith("http://") > This should be > 210 if (schemaLocation.length() > 0 && schemaLocation.startsWith("http://") == false && schemaLocation.startsWith("https://") == false) > This is related to https://issues.jboss.org/browse/JBWS-3827 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3832) Different default Spring descriptor name for creating client and server Bus instances

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3832?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3832: ---------------------------------- Fix Version/s: jbossws-cxf-5.0.0.Beta2 (was: jbossws-cxf-5.0) > Different default Spring descriptor name for creating client and server Bus instances > ------------------------------------------------------------------------------------- > > Key: JBWS-3832 > URL: https://issues.jboss.org/browse/JBWS-3832 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0.0.Beta2 > > Attachments: JBWS-3832-TEST_DRAFT.patch, JBWS-3832.diff > > > When Spring integration is enabled, the CXF Bus factory uses the same name to lookup descriptor defining the bus to be used for clients or endpoints (usually cxf.xml). Generally speaking, we might want to have the JAX-WS clients end up always using different Spring descriptors then any other consumer of the CXF Spring Bus factory. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3840) jboss-webservices.xml support for Apache CXF interceptor properties

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3840?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3840: ---------------------------------- Fix Version/s: jbossws-cxf-5.0.0.Beta2 (was: jbossws-cxf-5.0) > jboss-webservices.xml support for Apache CXF interceptor properties > ------------------------------------------------------------------- > > Key: JBWS-3840 > URL: https://issues.jboss.org/browse/JBWS-3840 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0.0.Beta2 > > > This basically implies extending the support for Apache CXF interceptor setup through properties to the jboss-webservices.xml descriptor. This would allow declaring interceptors to be added to the deployment bus and hence processing messages sent to and going out of any endpoint included in the deployment. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3826) Add support for encoding option in JAX-WS tools

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3826?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3826: ---------------------------------- Fix Version/s: jbossws-cxf-5.0.0.Beta2 (was: jbossws-cxf-5.0) > Add support for encoding option in JAX-WS tools > ----------------------------------------------- > > Key: JBWS-3826 > URL: https://issues.jboss.org/browse/JBWS-3826 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jaxws-tools-maven-plugin, jbossws-cxf, tools-jaxws > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0.0.Beta2 > > > This relates to https://issues.apache.org/jira/browse/CXF-2450 . > Basically, unless the encoding option of cxf tools is specified, both cxf and xjc rely on the system encoding setup, defaulting to UTF-8 if nothing is set at system level. > On system with a specific encoding (e.g. Windows installed w/ Italian language), the "file.encoding" system property is set to a value different from UTF-8 (ISO-8859-1 for the italian setup). This can lead to generating sources which can't then be compiled using a more restrictive encoding like UTF-8. > Generally speaking it would hence be good to allow users specifying the desired encoding for the sources to be generated. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3836) Convention for automatic predefined client/endpoint configuration retrieval

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3836?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3836: ---------------------------------- Fix Version/s: jbossws-cxf-5.0.0.Beta2 (was: jbossws-cxf-5.0) > Convention for automatic predefined client/endpoint configuration retrieval > --------------------------------------------------------------------------- > > Key: JBWS-3836 > URL: https://issues.jboss.org/browse/JBWS-3836 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf, jbossws-integration, productivity > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0.0.Beta2 > > > "An alternative idea would be to provide a convention for automatically > reading a pre-defined client configuration, for instance based on the > SEI class FQN. So for instance, we could say that for a port retrieved > as follows > import org.foo.ServiceIface; > ... > Service service = Service.create(new URL("...?wsdl"), serviceQName); > ServiceIface port = (ServiceIface)service.getPort(portQName, > ServiceIface.class); > instead of directly going and fetching the > "Standard-Client-Configuration" from the container webservices > management model we'd first try getting a configuration named > "org.foo.ServiceIface" (still in the webservices model) and only > fallback to the "Standard-Client-Configuration" if that's not found. > That would allow for different configurations to clients without > touching their code; the only requirement is the clients run in-container." > http://lists.jboss.org/pipermail/jbossws-dev/2014-September/002211.html -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3514) HTTP session scope support

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3514?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3514: ---------------------------------- Fix Version/s: jbossws-cxf-5.0.0.Beta2 (was: jbossws-cxf-5.0) > HTTP session scope support > -------------------------- > > Key: JBWS-3514 > URL: https://issues.jboss.org/browse/JBWS-3514 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Jim Ma > Fix For: jbossws-cxf-5.0.0.Beta2 > > > Solerman Kaplon says: > "Hello everyone, after metro stack got discontinued and CXF becoming the de-facto stack for JbossWS, I'm missing the @HttpSessionScope annotation. Basically, it automatically adds the jsession id to every http response so sessions can be tracked as usual in HTTP. For instance, that allows one to carry CDI/Seam conversations over several WS requests, very useful for rich clients. I would like for something to be included by default in jboss ws to allow for the same level of usability. Right now, the only alternative is to manually fiddle with the webservice context and add the header yourself. Another level of automation would be a Message Handler of Interceptor to do the job. Any other ideas?" > See also: > http://weblogs.java.net/blog/kohsuke/archive/2006/10/bringing_state.html -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

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

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3805?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3805: ---------------------------------- Fix Version/s: jbossws-cxf-5.0.0.Beta2 (was: jbossws-cxf-5.0) > 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 > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0.0.Beta2 > > > 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.3.8#6338)

10 years

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 November 2014