December 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2891) JAX-WS Detect and report duplicate wrapper classes

by Darran Lofthouse (JIRA)

JAX-WS Detect and report duplicate wrapper classes -------------------------------------------------- Key: JBWS-2891 URL: https://jira.jboss.org/jira/browse/JBWS-2891 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.3.0 >From the JAX-WS specification section 3.6.2.1 regarding Document Wrapped: - Conformance (Default wrapper bean names): In the absence of customizations, the wrapper request bean class MUST be named the same as the method and the wrapper response bean class MUST be named the same as the method with a "Response" suffix. The first letter of each bean name is capitalized to follow Java class naming conventions. Conformance (Wrapper bean name clash): Generated bean classes must have unique names within a pack- age and MUST NOT clash with other classes in that package. Clashes during generation MUST be reported as an error and require user intervention via name customization to correct. Note that some platforms do not distiguish filenames based on case so comparisons MUST ignore case. However if two services in the same package have the same operation there is an overlap of the generated wrappers which then causes the schemas between the two WSDLS to overlap. Using the @RequestWrapper and @ResponseWrapper annotations does separate the wrappers which also corrects the WSDLs, from the JAX-WS spec 'Conformance' paragraphs above this conflict should have been identified and reported as an error during deployment. -- 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

13 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-3179) InvocationHandlerJAXWS is responsible for endpoint injections & lifecycle

by Richard Opalka (JIRA)

InvocationHandlerJAXWS is responsible for endpoint injections & lifecycle ------------------------------------------------------------------------- Key: JBWS-3179 URL: https://jira.jboss.org/browse/JBWS-3179 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Richard Opalka Assignee: Richard Opalka Priority: Minor Fix For: jbossws-cxf-3.4.1 JBossWS CDI integration is operating upon InvocationHandler abstraction. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-3142) ServiceObjectFactory have to clean up threads after it's job is finished

by Richard Opalka (JIRA)

ServiceObjectFactory have to clean up threads after it's job is finished ------------------------------------------------------------------------ Key: JBWS-3142 URL: https://jira.jboss.org/browse/JBWS-3142 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Richard Opalka Assignee: Richard Opalka Priority: Critical Fix For: jbossws-cxf-3.4.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-3177) Provide CDI Integration Points

by Richard Opalka (JIRA)

Provide CDI Integration Points ------------------------------ Key: JBWS-3177 URL: https://jira.jboss.org/browse/JBWS-3177 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-3.4.1, jbossws-native-3.4.1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3175) Can't change Client Config using StubExt setConfigName

by Stephan Heffner (JIRA)

Can't change Client Config using StubExt setConfigName ------------------------------------------------------ Key: JBWS-3175 URL: https://jira.jboss.org/browse/JBWS-3175 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss 5.1.0.GA, Java 6u22, Linux 64bit Reporter: Stephan Heffner After a migration from JBoss 4.2.3.GA to a JBoss 5.1.0.GA environment, one of my WebService clients doesn't work anymore. After some research I've seen, that the required selection of the JAXWS Client Config "HTTP 1.0 Client" has no effect: QName namespace = new QName(namespaceURI, webServiceName); URL endpoint = new URL(ceWsdl); sampleService = new SampleServiceService(endpoint, namespace); externalServicePort = vcService.getVideoCenterServicePort(); StubExt stubExt = (StubExt) externalServicePort; stubExt.setConfigName("HTTP 1.0 Client"); log.debug(stubExt.getConfigName()); Log still contains "Standard Client" We used this selection to configure the chunksize to 0 (= disable). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-3174) CXF stack doesn't pick up cxf.xml in the classpath to create spring bus

by Jim Ma (JIRA)

CXF stack doesn't pick up cxf.xml in the classpath to create spring bus ----------------------------------------------------------------------- Key: JBWS-3174 URL: https://jira.jboss.org/browse/JBWS-3174 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.4.0.CR1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.0 DescriptorDeplomentAspect loads the /cxf.xml in the classpath and put it in the deployment attachment as cxf endpoint deployment descriptor. This stops the META-INF/jbossws-cxf.xml or WEB-INF/jbossws-cxf.xml which co-exists with /cxf.xml being loaded to create CXF bus. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3173) Duplicated jaxb / jaxws / jaxrpc api jars after install against AS 6 CR1

by Alessio Soldano (JIRA)

Duplicated jaxb / jaxws / jaxrpc api jars after install against AS 6 CR1 ------------------------------------------------------------------------ Key: JBWS-3173 URL: https://jira.jboss.org/browse/JBWS-3173 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Reporter: Alessio Soldano Priority: Minor Fix For: jbossws-cxf-3.4.1, jbossws-native-3.4.1 http://community.jboss.org/message/573269 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 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 December 2010