February 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3591) Provide WebServiceFeature for initializing JAXWS Port

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3591?page=com.atlassian.jira.plugin.... ] Alessio Soldano reopened JBWS-3591: ----------------------------------- > Provide WebServiceFeature for initializing JAXWS Port > ----------------------------------------------------- > > Key: JBWS-3591 > URL: https://issues.jboss.org/browse/JBWS-3591 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > We could have a WebServiceFeature extension allowing integrators to initialize JAXWS ports, e.g. by adding handlers. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3138) Better support for local WSDL deployment configurations (e.g., wsimport -clientjar)

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3138?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3138: --------------------------------------- http://weblogs.java.net/blog/ramapulavarthi/archive/2010/09/03/wsimport-c... > Better support for local WSDL deployment configurations (e.g., wsimport -clientjar) > ----------------------------------------------------------------------------------- > > Key: JBWS-3138 > URL: https://issues.jboss.org/browse/JBWS-3138 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-native, productivity, tools-jaxws > Affects Versions: jbossws-cxf-3.3.1, jbossws-native-3.3.1, jbossws-native-3.4.0.CR1 > Reporter: Ray Cardillo > Labels: jax-ws-catalog, local_wsdl, wsconsume, wsimport, wsimport_-clientjar, wsimport_clientjar, xml_catalog > Fix For: jbossws-cxf-4.2 > > > Developers who must deploy to disconnected or closed network environments often have challenges creating local WSDL deployment configurations. This is especially true when they want to create a shared library or use a shared configuration that several projects must all use. For example, if there are several J2EE web applications and web services that are all clients of a particular web service, most developers end up copying all of the required WSDL content to the WEB-INF/wsdl folder of each project and then using the wsdlLocation attribute to specify the local WSDL files. This type of strategy is difficult to maintain, and the only other option is to create a shared OASIS XML catalog library. However, using a shared OASIS XML catalog library can be very challenging because of the details involved... putting a properly compiled schema catalog JAR (with a properly configured jax-ws-catalog.xml file) in the WEB-INF/lib and having the container use that JAR to resolve references by configuring the service endpoint with a reference that will be resolved by the JAR. For more information about that, see the last reference provided below, but the details are tricky to say the least, and some containers actually have problems with this type of deployment configuration. > To help with this requirement, JAX-WS 2.2.2 RI has added a "-clientjar" option to the "wsimport" tool. This feature is extremely important to anyone facing these challenges, and offers a huge productivity boost, from several perspectives. For developers who know how to navigate the complexity of doing this, it helps by doing all of the labor intensive steps automatically (downloading the WSDL, creating correct resource references, compiling the JAR properly, annotating the binding properly, etc). For developers who do not know about these details, it is even more valuable because this option is not very well known, yet is something that should be a primary use case (supporting people on isolated networks). The requirement is often overlooked by the web services frameworks because they assume everyone will always have network access, but isolated networks are very common in certain communities. > See the following for more references: > http://www.java.net/print/476434 > http://wikis.sun.com/display/GlassFish/3.1Metro#3.1Metro-wsimport%5Cclien... > http://forums.java.net/jive/message.jspa?messageID=480624#480624 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3138) Better support for local WSDL deployment configurations (e.g., wsimport -clientjar)

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3138?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3138: ---------------------------------- Fix Version/s: jbossws-cxf-4.2 (was: jbossws-jaxws-tools-maven-plugin-1.1.1.GA) Component/s: (was: jaxws-tools-maven-plugin) > Better support for local WSDL deployment configurations (e.g., wsimport -clientjar) > ----------------------------------------------------------------------------------- > > Key: JBWS-3138 > URL: https://issues.jboss.org/browse/JBWS-3138 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-native, productivity, tools-jaxws > Affects Versions: jbossws-cxf-3.3.1, jbossws-native-3.3.1, jbossws-native-3.4.0.CR1 > Reporter: Ray Cardillo > Labels: jax-ws-catalog, local_wsdl, wsconsume, wsimport, wsimport_-clientjar, wsimport_clientjar, xml_catalog > Fix For: jbossws-cxf-4.2 > > > Developers who must deploy to disconnected or closed network environments often have challenges creating local WSDL deployment configurations. This is especially true when they want to create a shared library or use a shared configuration that several projects must all use. For example, if there are several J2EE web applications and web services that are all clients of a particular web service, most developers end up copying all of the required WSDL content to the WEB-INF/wsdl folder of each project and then using the wsdlLocation attribute to specify the local WSDL files. This type of strategy is difficult to maintain, and the only other option is to create a shared OASIS XML catalog library. However, using a shared OASIS XML catalog library can be very challenging because of the details involved... putting a properly compiled schema catalog JAR (with a properly configured jax-ws-catalog.xml file) in the WEB-INF/lib and having the container use that JAR to resolve references by configuring the service endpoint with a reference that will be resolved by the JAR. For more information about that, see the last reference provided below, but the details are tricky to say the least, and some containers actually have problems with this type of deployment configuration. > To help with this requirement, JAX-WS 2.2.2 RI has added a "-clientjar" option to the "wsimport" tool. This feature is extremely important to anyone facing these challenges, and offers a huge productivity boost, from several perspectives. For developers who know how to navigate the complexity of doing this, it helps by doing all of the labor intensive steps automatically (downloading the WSDL, creating correct resource references, compiling the JAR properly, annotating the binding properly, etc). For developers who do not know about these details, it is even more valuable because this option is not very well known, yet is something that should be a primary use case (supporting people on isolated networks). The requirement is often overlooked by the web services frameworks because they assume everyone will always have network access, but isolated networks are very common in certain communities. > See the following for more references: > http://www.java.net/print/476434 > http://wikis.sun.com/display/GlassFish/3.1Metro#3.1Metro-wsimport%5Cclien... > http://forums.java.net/jive/message.jspa?messageID=480624#480624 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3597) JBWS2241TestCase assumes AS allows invocation of no security role restricted methods

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3597?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3597: ---------------------------------- Description: The fix for https://issues.jboss.org/browse/AS7-6476 basically pointed out that 1) the testcase needs to be enhanced 2) the testcase assumes method with no security role restrictions (but with roles declared for the app) can be invoked, but that's not the default behaviour anymore on AS 7.2. (was: The fix for https://issues.jboss.org/browse/AS7-6476 basically pointed out that 1) the testcase needs to be enhanced 2) the testcase assumes method with no security role restrictions can be invoked, but that's not the default behaviour anymore on AS 7.2.) > JBWS2241TestCase assumes AS allows invocation of no security role restricted methods > ------------------------------------------------------------------------------------ > > Key: JBWS-3597 > URL: https://issues.jboss.org/browse/JBWS-3597 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > The fix for https://issues.jboss.org/browse/AS7-6476 basically pointed out that 1) the testcase needs to be enhanced 2) the testcase assumes method with no security role restrictions (but with roles declared for the app) can be invoked, but that's not the default behaviour anymore on AS 7.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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3598) Update scripts and hudson job to support AS8

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3598: ------------------------------------- Summary: Update scripts and hudson job to support AS8 Key: JBWS-3598 URL: https://issues.jboss.org/browse/JBWS-3598 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration, productization Reporter: Alessio Soldano Fix For: jbossws-cxf-4.2 We need to update the scripts for deploying/undeploying to AS 8 and now tagged AS 7.2.0.Final. The same applied for hudson jobs. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3597) JBWS2241TestCase assumes AS allows invocation of no security role restricted methods

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3597?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3597: --------------------------------------- https://source.jboss.org/changelog/JBossWS?cs=17304 > JBWS2241TestCase assumes AS allows invocation of no security role restricted methods > ------------------------------------------------------------------------------------ > > Key: JBWS-3597 > URL: https://issues.jboss.org/browse/JBWS-3597 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > The fix for https://issues.jboss.org/browse/AS7-6476 basically pointed out that 1) the testcase needs to be enhanced 2) the testcase assumes method with no security role restrictions can be invoked, but that's not the default behaviour anymore on AS 7.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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3597) JBWS2241TestCase assumes AS allows invocation of no security role restricted methods

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3597: ------------------------------------- Summary: JBWS2241TestCase assumes AS allows invocation of no security role restricted methods Key: JBWS-3597 URL: https://issues.jboss.org/browse/JBWS-3597 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.2 The fix for https://issues.jboss.org/browse/AS7-6476 basically pointed out that 1) the testcase needs to be enhanced 2) the testcase assumes method with no security role restrictions can be invoked, but that's not the default behaviour anymore on AS 7.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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3566) Upgrade to Apache CXF 2.7

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3566?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3566: ---------------------------------- Description: Apache CXF 2.7 migration guide: http://cxf.apache.org/docs/27-migration-guide.html > Upgrade to Apache CXF 2.7 > ------------------------- > > Key: JBWS-3566 > URL: https://issues.jboss.org/browse/JBWS-3566 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > Apache CXF 2.7 migration guide: http://cxf.apache.org/docs/27-migration-guide.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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3596) Provide testcase for WS-Discovery functionalities

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3596: ------------------------------------- Summary: Provide testcase for WS-Discovery functionalities Key: JBWS-3596 URL: https://issues.jboss.org/browse/JBWS-3596 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-4.2 This is about verifying WS-Discovery client functionalities when running with cxf integrated in jbossws. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3595) Provide testcase for SOAP-over-UDP functionalities

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3595: ------------------------------------- Summary: Provide testcase for SOAP-over-UDP functionalities Key: JBWS-3595 URL: https://issues.jboss.org/browse/JBWS-3595 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-4.2 This is about verifying SOAP-over-UDP when running with cxf integrated in jbossws. In any case we should not ship the Mina dependency 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, 2 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 2013