March 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2402) Upgrade jUDDI to 2.0rc5

by Alessio Soldano (JIRA)

Upgrade jUDDI to 2.0rc5 ----------------------- Key: JBWS-2402 URL: https://jira.jboss.org/jira/browse/JBWS-2402 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.0.5 We should upgrade jUDDI dependency to 2.0rc5 to satisfy the SOA-P requirements. See the forum thread for more details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
17
0 / 0

[JBoss JIRA] Created: (JBWS-2247) Write test for JBWS-1190 from scratch using MessageContext properties

by Alessio Soldano (JIRA)

Write test for JBWS-1190 from scratch using MessageContext properties --------------------------------------------------------------------- Key: JBWS-2247 URL: http://jira.jboss.com/jira/browse/JBWS-2247 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro Reporter: Alessio Soldano The JBWS-1190 test currently should be re-written using the message context properties (looking at the data dir is not a valid solution for metro and cxf). Also please note that the information coming from the jbossws/services console might be misleading. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
5
0 / 0

[JBoss JIRA] Created: (JBWS-2203) Implement standard message context properties

by Thomas Diesler (JIRA)

Implement standard message context properties --------------------------------------------- Key: JBWS-2203 URL: http://jira.jboss.com/jira/browse/JBWS-2203 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-native-3.0.2 Implement properties public static final String WSDL_DESCRIPTION = "javax.xml.ws.wsdl.description"; public static final String WSDL_SERVICE = "javax.xml.ws.wsdl.service"; public static final String WSDL_PORT = "javax.xml.ws.wsdl.port"; public static final String WSDL_INTERFACE = "javax.xml.ws.wsdl.interface"; public static final String WSDL_OPERATION = "javax.xml.ws.wsdl.operation"; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2227) Investigate why multiple virtual hosts test fails on CXF

by Richard Opalka (JIRA)

Investigate why multiple virtual hosts test fails on CXF -------------------------------------------------------- Key: JBWS-2227 URL: http://jira.jboss.com/jira/browse/JBWS-2227 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Richard Opalka Fix For: jbossws-cxf-3.0.3 See jaxws/jbws1178 test -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-1655) Add support for endpoint address rewriting

by Thomas Diesler (JIRA)

Add support for endpoint address rewriting ------------------------------------------ Key: JBWS-1655 URL: http://jira.jboss.com/jira/browse/JBWS-1655 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-xfire Affects Versions: xfire-1.2.6 Reporter: Thomas Diesler A jaxws endpoint that uses @WebService.wsdlLocation need to have the SOAP address rewriten to correspond to the actual address of the endpoint -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

5
18
0 / 0

[JBoss JIRA] Created: (JBWS-2507) Support generics in wrapper classes

by Alessio Soldano (JIRA)

Support generics in wrapper classes ----------------------------------- Key: JBWS-2507 URL: https://jira.jboss.org/jira/browse/JBWS-2507 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, tools-jaxws Affects Versions: jbossws-cxf-3.1.0 Reporter: Alessio Soldano Fix For: jbossws-cxf-3.1.1 This is basically the same as JBWS-2477 except it's with JBossWS-CXF stack. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-2508) WSProvide output is not correctly redirected

by Alessio Soldano (JIRA)

WSProvide output is not correctly redirected -------------------------------------------- Key: JBWS-2508 URL: https://jira.jboss.org/jira/browse/JBWS-2508 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, tools-jaxws Affects Versions: jbossws-cxf-3.1.0 Reporter: Alessio Soldano Fix For: jbossws-cxf-3.1.1 The WSProvide output (more generally the cxf tool output) is not redirected to a given stream. We should make this possible (plus making the WSProviderTestCase less verbose...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
5
0 / 0

[JBoss JIRA] Created: (JBWS-2382) Fix JBossWS deployers processing

by Richard Opalka (JIRA)

Fix JBossWS deployers processing -------------------------------- Key: JBWS-2382 URL: https://jira.jboss.org/jira/browse/JBWS-2382 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Affects Versions: jbossws-cxf-3.0.4, jbossws-metro-3.0.4, jbossws-native-3.0.4, jbossws-cxf-3.0.3 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.0.5, jbossws-metro-3.0.5, jbossws-cxf-3.0.5 In general all your processing in the deployers should just be based on metadata available to deployers or configuration on the deployers. You shouldn't be looking at any services. e.g. suppose the war had a dependency on an ejb from some other application then its not going to be started until that ejb exists regardless of when jbossweb.sar gets started. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2370) Ensure correct JBossWS startup if there are Webservice archived in deploy directory during JBossAS bootstrap

by Richard Opalka (JIRA)

Ensure correct JBossWS startup if there are Webservice archived in deploy directory during JBossAS bootstrap ------------------------------------------------------------------------------------------------------------ Key: JBWS-2370 URL: https://jira.jboss.org/jira/browse/JBWS-2370 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Affects Versions: jbossws-cxf-3.0.4, jbossws-metro-3.0.4, jbossws-native-3.0.4 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.0.5, jbossws-metro-3.0.5, jbossws-cxf-3.0.5 During deployment of the endpoints declared in my wars a call is made to AbstractServerConfig.getConnectorPort(). This fetches the WS Server MBean and tries to lookup objects of type "jboss.web:type=Connector,*". At the point where the lookup fails the jboss.web MBean has only one entry for the WebServer. In the run that I managed to debug the type=Connector entries were added at a later point. So, some of the subsequent calls to getConnectorPort() succeeded and also the AS bootstrap did not hang. I was unable to debug a case where the bootstrap did hang. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2521) Refactor / rewrite ServiceObjectFactory

by Alessio Soldano (JIRA)

Refactor / rewrite ServiceObjectFactory --------------------------------------- Key: JBWS-2521 URL: https://jira.jboss.org/jira/browse/JBWS-2521 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-3.1.1 The jbossws-cxf ServiceObjectFactory needs to be cleaned: - Bus retrieval: this is currently performed through reflection on the Service class and following cast to cxf ServiceImpl; leveraging the BusFactory should be enough to get the default bus that is used by the cxf ProviderImpl for every Service creation - ServiceRef stub properties setup: this is currently performed through reflection on Service class to get the ServiceDelegate and then chaning the ServiceDelegate instance at runtime with a custom onesetting the properties. Instead of doing this hack, we should evaluate leveraging the CXF configuration for runtime constructed objects (http://cwiki.apache.org/CXF20DOC/configuration-of-runtime-constructed-obj...). IOW cxf ServiceImpl looks for a bean named portName.toString() + ".jaxws-client.proxyFactory" to configure the JaxWsProxyFactoryBean used to build the port and that factory bean allows for setting the stub properties. We might be able to generate on the fly and supply a bean configuration to the cxf bus for having our stub properties automatically configured by the already existing cxf configuration system. - perhaps even the handler chain configuration can be achieved in a way similar to the described in the previous point. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues March 2009