August 2014 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3530) Add some hints to the code generated by cxf using wsconsume to tune generated code before use

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3530?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3530: ---------------------------------- Fix Version/s: (was: jbossws-cxf-5.0) > Add some hints to the code generated by cxf using wsconsume to tune generated code before use > --------------------------------------------------------------------------------------------- > > Key: JBWS-3530 > URL: https://issues.jboss.org/browse/JBWS-3530 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.0.2 > Environment: JBossWS CXF > Reporter: Mustafa Musaji > Assignee: Jim Ma > Priority: Trivial > Labels: webservices > > The generated code when using wsconsume is not really meant for use in production environment with the statically initialized wsdlLocation and the error that will be logged when this the Service object is first initialized. > {code:title=WSService.java|borderStyle=solid} > static { > URL url = null; > try { > url = new URL("file:/directory/to/wsdl/WSTestEJB/ejbModule/META-INF/WSProvider.wsdl"); > } catch (MalformedURLException e) { > java.util.logging.Logger.getLogger(WSProviderService.class.getName()) > .log(java.util.logging.Level.INFO, > "Can not initialize the default wsdl from {0}", "file:/directory/to/wsdl/WSTestEJB/ejbModule/META-INF/WSProvider.wsdl"); > } > WSDL_LOCATION = url; > } > {code} > This is a request to amend the log level to "DEBUG" and/or have wsconsume create a hint of sorts to tune this class before use in a container. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3785) Add option for forcing https protocol when rewriting soap:addres in WSDL

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3785?page=com.atlassian.jira.plugin.... ] Jim Ma commented on JBWS-3785: ------------------------------ New element <wsdl-uri-scheme> is added to standalone.xml in WFLY9. This feature is only supported in the future WFLY9 release. > Add option for forcing https protocol when rewriting soap:addres in WSDL > ------------------------------------------------------------------------ > > Key: JBWS-3785 > URL: https://issues.jboss.org/browse/JBWS-3785 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Jim Ma > Fix For: jbossws-cxf-5.0 > > > In some cases it might be useful having an option in the ServerConfig for forcing the use of https protocol when rewriting the WSDL soap:address. > That would basically override the current protocol selection mechanism in SoapAddressRewriteHelper#getRewrittenPublishedEndpointUrl method, which looks at the protocol in the provided wsdl (if any) and the one for the endpoint address (which is computed considering the transport guarantee specified through either annotations or descriptors). The new option would add a server-wide configuration overriding anything (if set to true, all soap:address location attributes for any endpoint deployed on the server will use https protocol). > This jira implies also adding a new element to the webservices subsystem of the application server. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

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

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3514?page=com.atlassian.jira.plugin.... ] Jim Ma commented on JBWS-3514: ------------------------------ This can be supported with cxf annotation @FactoryType(FactoryType.Type.Session) . For more details, please look at test :org.jboss.test.ws.jaxws.samples.session.SessionEndpointTestCase > HTTP session scope support > -------------------------- > > Key: JBWS-3514 > URL: https://issues.jboss.org/browse/JBWS-3514 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Jim Ma > Fix For: jbossws-cxf-5.0 > > > 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.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3819) Allow parametrization of web connector created within TS execution

by Jan Blizňák (JIRA)

[ https://issues.jboss.org/browse/JBWS-3819?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-3819: ------------------------------ Environment: EAP 6.3.0 (jbossws-cxf-4.3.0.Final-redhat-3, jbossweb-7.4.8.Final-redhat-4) (was: EAP 6.3.0 (jbossweb-7.4.8.Final-redhat-4)) > Allow parametrization of web connector created within TS execution > ------------------------------------------------------------------ > > Key: JBWS-3819 > URL: https://issues.jboss.org/browse/JBWS-3819 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.3 > Environment: EAP 6.3.0 (jbossws-cxf-4.3.0.Final-redhat-3, jbossweb-7.4.8.Final-redhat-4) > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Priority: Minor > Attachments: patch.diff > > > During execution of TS there is new 'https' connector created for several testcases. This connector has hardcoded protocol value {{HTTP/1.1}} which means use JIO conector (org.apache.coyote.http11.Http11Protocol), this is done in [https://source.jboss.org/browse/JBossWS/container/jboss72/tags/jbossws-jb...] > If we want to test with NIO connector enabled (org.apache.coyote.http11.Http11NioProtocol), we can do it only by changing already existing connectors before TS execution, but not for the new ones created during execution. > The simple solution here is to allow overriding connector protocol class by system property. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3819) Allow parametrization of web connector created within TS execution

by Jan Blizňák (JIRA)

[ https://issues.jboss.org/browse/JBWS-3819?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-3819: ------------------------------ Assignee: Alessio Soldano > Allow parametrization of web connector created within TS execution > ------------------------------------------------------------------ > > Key: JBWS-3819 > URL: https://issues.jboss.org/browse/JBWS-3819 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.3 > Environment: EAP 6.3.0 (jbossweb-7.4.8.Final-redhat-4) > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Priority: Minor > Attachments: patch.diff > > > During execution of TS there is new 'https' connector created for several testcases. This connector has hardcoded protocol value {{HTTP/1.1}} which means use JIO conector (org.apache.coyote.http11.Http11Protocol), this is done in [https://source.jboss.org/browse/JBossWS/container/jboss72/tags/jbossws-jb...] > If we want to test with NIO connector enabled (org.apache.coyote.http11.Http11NioProtocol), we can do it only by changing already existing connectors before TS execution, but not for the new ones created during execution. > The simple solution here is to allow overriding connector protocol class by system property. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3819) Allow parametrization of web connector created within TS execution

by Jan Blizňák (JIRA)

[ https://issues.jboss.org/browse/JBWS-3819?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-3819: ------------------------------ Attachment: patch.diff simple patch example > Allow parametrization of web connector created within TS execution > ------------------------------------------------------------------ > > Key: JBWS-3819 > URL: https://issues.jboss.org/browse/JBWS-3819 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.3 > Environment: EAP 6.3.0 (jbossweb-7.4.8.Final-redhat-4) > Reporter: Jan Blizňák > Priority: Minor > Attachments: patch.diff > > > During execution of TS there is new 'https' connector created for several testcases. This connector has hardcoded protocol value {{HTTP/1.1}} which means use JIO conector (org.apache.coyote.http11.Http11Protocol), this is done in [https://source.jboss.org/browse/JBossWS/container/jboss72/tags/jbossws-jb...] > If we want to test with NIO connector enabled (org.apache.coyote.http11.Http11NioProtocol), we can do it only by changing already existing connectors before TS execution, but not for the new ones created during execution. > The simple solution here is to allow overriding connector protocol class by system property. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3819) Allow parametrization of web connector created within TS execution

by Jan Blizňák (JIRA)

Jan Blizňák created JBWS-3819: --------------------------------- Summary: Allow parametrization of web connector created within TS execution Key: JBWS-3819 URL: https://issues.jboss.org/browse/JBWS-3819 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Affects Versions: jbossws-cxf-4.3 Environment: EAP 6.3.0 (jbossweb-7.4.8.Final-redhat-4) Reporter: Jan Blizňák Priority: Minor During execution of TS there is new 'https' connector created for several testcases. This connector has hardcoded protocol value {{HTTP/1.1}} which means use JIO conector (org.apache.coyote.http11.Http11Protocol), this is done in [https://source.jboss.org/browse/JBossWS/container/jboss72/tags/jbossws-jb...] If we want to test with NIO connector enabled (org.apache.coyote.http11.Http11NioProtocol), we can do it only by changing already existing connectors before TS execution, but not for the new ones created during execution. The simple solution here is to allow overriding connector protocol class by system property. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3750) Add ability to rewrite path in WSDL URL references

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-3750?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-3750: -------------------------------- Reverted commit in https://svn.jboss.org/repos/jbossws/container/wildfly80/branches/jbossws-... from revision 18824 back to 18812. New, "Committed revision 18832." > Add ability to rewrite path in WSDL URL references > -------------------------------------------------- > > Key: JBWS-3750 > URL: https://issues.jboss.org/browse/JBWS-3750 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Kyle Lape > Assignee: R Searls > Fix For: jbossws-cxf-5.0 > > Attachments: feature-doc-fragment.txt > > > Currently JBossWS/CXF have the ability to configure a custom host and/or port to use when populating the soap:address and schemaLocation items in a WSDL. This request is to add the ability to configure a custom URL path in addition to the host and port. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3750) Add ability to rewrite path in WSDL URL references

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-3750?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-3750: -------------------------------- repo's spi and common's commit has been pushed to nexus so I made the cxf-tunk commit https://svn.jboss.org/repos/jbossws/stack/cxf/trunk Committed revision 18830. Also the needed addition to wfly ./build/src/main/resources/docs/schema/jboss-as-webservices_1_3.xsd was squashed in the the pull request. > Add ability to rewrite path in WSDL URL references > -------------------------------------------------- > > Key: JBWS-3750 > URL: https://issues.jboss.org/browse/JBWS-3750 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Kyle Lape > Assignee: R Searls > Fix For: jbossws-cxf-5.0 > > Attachments: feature-doc-fragment.txt > > > Currently JBossWS/CXF have the ability to configure a custom host and/or port to use when populating the soap:address and schemaLocation items in a WSDL. This request is to add the ability to configure a custom URL path in addition to the host and port. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

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 commented on JBWS-3514: --------------------------------------- Setting dependency on jira for upgrading to CXF to 3.0.2 because of change [1] required. [1] https://fisheye6.atlassian.com/changelog/cxf?cs=9bc81ab1d1bc5a521fdb0468a... > HTTP session scope support > -------------------------- > > Key: JBWS-3514 > URL: https://issues.jboss.org/browse/JBWS-3514 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Jim Ma > Fix For: jbossws-cxf-5.0 > > > 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.2.6#6264)

10 years, 3 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 August 2014