jbossws-issues April 2013

jbossws-issues@lists.jboss.org

1 participants
25 discussions

[JBoss JIRA] (JBWS-3619) Backport the RemoteDeployer timeout setting to 7.x integration layer

by Jim Ma (JIRA)

Jim Ma created JBWS-3619: ---------------------------- Summary: Backport the RemoteDeployer timeout setting to 7.x integration layer Key: JBWS-3619 URL: https://issues.jboss.org/browse/JBWS-3619 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Affects Versions: jbossws-cxf-4.1.3 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.2 Back port the https://issues.jboss.org/browse/AS7-6816 to 7.x integration layer -- 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

1
0
0 / 0

[JBoss JIRA] (JBWS-3512) Try WS-I Basic Security Profile (BSP) tools

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3512?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3512: ---------------------------------- Priority: Critical (was: Major) > Try WS-I Basic Security Profile (BSP) tools > ------------------------------------------- > > Key: JBWS-3512 > URL: https://issues.jboss.org/browse/JBWS-3512 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf, productization > Reporter: Alessio Soldano > Priority: Critical > Fix For: jbossws-cxf-4.2 > > > We should try the WS-I BSP tools and try to get an idea of where we are with JBossWS / Apache CXF: http://www.ws-i.org/deliverables/workinggroup.aspx?wg=testingtools -- 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

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 reopened JBWS-3138: ----------------------------------- sorry, forgot our tool facade is still to be fixed, reopening. > 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 > Assignee: Jim Ma > 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

1
0
0 / 0

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

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3598?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3598: ---------------------------------- Fix Version/s: (was: jbossws-cxf-4.2) > 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 > > 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

1
0
0 / 0

[JBoss JIRA] (JBWS-3524) Resolve system property references in jboss-webservices.xml

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3524?page=com.atlassian.jira.plugin.... ] Alessio Soldano reopened JBWS-3524: ----------------------------------- Sorry, erroneously closed, the ASIL for 7.x containers is still to be fixed. > Resolve system property references in jboss-webservices.xml > ----------------------------------------------------------- > > Key: JBWS-3524 > URL: https://issues.jboss.org/browse/JBWS-3524 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Kyle Lape > Assignee: Jim Ma > Fix For: jbossws-cxf-4.2 > > > It would be useful for jboss-webservices.xml to have the ability to resolve system property references. > Here's a particular use case: You have an EJB name defined in jboss-ejb3.xml like so: > {noformat} > <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:c="urn:clustering:1.0" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" version="3.1" impl-version="2.0"> > <enterprise-beans> > <session> > <ejb-name>Hello-${app.env}</ejb-name> > <ejb-class>com.jboss.examples.ejb3.HelloBean</ejb-class> > <session-type>Stateless</session-type> > </session> > </enterprise-beans> > </jboss:ejb-jar> > {noformat} > And now you want to reference it in jboss-webservices.xml: > {noformat} > <webservices xmlns="http://www.jboss.com/xml/ns/javaee"> > <port-component> > <ejb-name>Hello-${app.env}</ejb-name> > <port-component-uri>test</port-component-uri> > </port-component> > </webservices> > {noformat} > This currently does not work. -- 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

1
0
0 / 0

← Newer
1
2
3
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues April 2013