July 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3677) Save container registry in ServerConfigService.start() instead of install()

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3677?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-3677: ------------------------- Issue Type: Bug (was: Feature Request) > Save container registry in ServerConfigService.start() instead of install() > --------------------------------------------------------------------------- > > Key: JBWS-3677 > URL: https://issues.jboss.org/browse/JBWS-3677 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.2 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: jbossws-cxf-4.3 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3601) SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3601?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3601: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 913411|https://bugzilla.redhat.com/show_bug.cgi?id=913411] from MODIFIED to ON_QA > SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF > -------------------------------------------------------------- > > Key: JBWS-3601 > URL: https://issues.jboss.org/browse/JBWS-3601 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.0.2 > Environment: JBoss Enterprise Application Platform 6 > Reporter: Tadayoshi Sato > Assignee: Alessio Soldano > Labels: cxf > Fix For: jbossws-cxf-4.2 > > > Backport https://issues.apache.org/jira/browse/CXF-4790, which is the root cause. The code below doesn't render {{<soapenv:Subcode>}}. > {code} > import javax.xml.soap.SOAPConstants; > import javax.xml.soap.SOAPFactory; > import javax.xml.soap.SOAPFault; > import javax.xml.ws.soap.SOAPFaultException; > ... > SOAPFactory factory = SOAPFactory.newInstance(SOAPConstants.SOAP_1_2_PROTOCOL); > SOAPFault fault = factory.createFault("Operator not found", new QName(SOAPConstants.URI_NS_SOAP_1_2_ENVELOPE, "Receiver")); > fault.appendFaultSubcode(new QName("...", "OperatorNotFound")); > ... > throw new SOAPFaultException(fault); > {code} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3678) ReflectiveAttachmentRefScanner recursively scanning enums

by Simon Berthaiume (JIRA)

Simon Berthaiume created JBWS-3678: -------------------------------------- Summary: ReflectiveAttachmentRefScanner recursively scanning enums Key: JBWS-3678 URL: https://issues.jboss.org/browse/JBWS-3678 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Simon Berthaiume Priority: Minor Sorry if this isn't a top-notch bug report, I'm really not that familiar with JBoss and it's modules. The issue is that when starting JBoss (jboss-5.1.0.GA) with our webservices WAR was taking us a tremendous amount of time (25+ minutes vs ~5 minutes without) and they contain about nothing (just a WS to Bean bridge basically). After much investigation, I discovered that most of the startup time (75%+) was spent in the org.jboss.ws.extensions.xop.jaxws.ReflectiveAttachmentRefScanner.scanBean(Class xmlRoot) method; further investigation revealed that out issues were with Enum types. Scaning an enum type could be in the O(n^2) order of magnitude as it seems the method will call itself (recursively) on all values of the enum again and again (up to a point). We have some fairly large enums here (1000+ elements, could be bad design, but still) and when the scanner tried to scan them, it could take up to 35 seconds (not ms) for a single class. As a workaround I figured-out that adding the @XmlMimeType annotation to enum properties of classes used in our WS interfaces sort of solved our issues, the startup time went from 25-30 minutes to about 6.5 minutes. Not sure if this is a bug or a feature, but I though I should let the community know about this as I have never found any posts regarding that issue. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3677) Save container registry in ServerConfigService.start() instead of install()

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3677?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-3677: ------------------------- Summary: Save container registry in ServerConfigService.start() instead of install() (was: Save ContainerRegistry in ServerConfigService.start() instead of install()) > Save container registry in ServerConfigService.start() instead of install() > --------------------------------------------------------------------------- > > Key: JBWS-3677 > URL: https://issues.jboss.org/browse/JBWS-3677 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.2 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: jbossws-cxf-4.3 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3677) Save ContainerRegistry in ServerConfigService.start() instead of install()

by Jim Ma (JIRA)

Jim Ma created JBWS-3677: ---------------------------- Summary: Save ContainerRegistry in ServerConfigService.start() instead of install() Key: JBWS-3677 URL: https://issues.jboss.org/browse/JBWS-3677 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Affects Versions: jbossws-cxf-4.2 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.3 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3676) Minor dependency cleanup in jbossws-common

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/JBWS-3676?page=com.atlassian.jira.plugin.... ] Paul Gier commented on JBWS-3676: --------------------------------- Attached a patch for the 2.1 branch. The same change appears to be applicable to trunk. > Minor dependency cleanup in jbossws-common > ------------------------------------------ > > Key: JBWS-3676 > URL: https://issues.jboss.org/browse/JBWS-3676 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: productization > Reporter: Paul Gier > Assignee: Alessio Soldano > Attachments: 0001-JBWS-3676-Fix-dep-issue-in-jaxrpc-api.patch > > > jbossws-common has an undeclared compile time dependency on javax.xml:jaxrpc which is pulled in transitively via the ejb api. And it appears ejb-api is not used. > This should be changed to use the org.jboss.specs project version of the jaxrpc api directly. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3676) Minor dependency cleanup in jbossws-common

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/JBWS-3676?page=com.atlassian.jira.plugin.... ] Paul Gier updated JBWS-3676: ---------------------------- Assignee: Alessio Soldano > Minor dependency cleanup in jbossws-common > ------------------------------------------ > > Key: JBWS-3676 > URL: https://issues.jboss.org/browse/JBWS-3676 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: productization > Reporter: Paul Gier > Assignee: Alessio Soldano > Attachments: 0001-JBWS-3676-Fix-dep-issue-in-jaxrpc-api.patch > > > jbossws-common has an undeclared compile time dependency on javax.xml:jaxrpc which is pulled in transitively via the ejb api. And it appears ejb-api is not used. > This should be changed to use the org.jboss.specs project version of the jaxrpc api directly. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3676) Minor dependency cleanup in jbossws-common

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/JBWS-3676?page=com.atlassian.jira.plugin.... ] Paul Gier updated JBWS-3676: ---------------------------- Attachment: 0001-JBWS-3676-Fix-dep-issue-in-jaxrpc-api.patch > Minor dependency cleanup in jbossws-common > ------------------------------------------ > > Key: JBWS-3676 > URL: https://issues.jboss.org/browse/JBWS-3676 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: productization > Reporter: Paul Gier > Attachments: 0001-JBWS-3676-Fix-dep-issue-in-jaxrpc-api.patch > > > jbossws-common has an undeclared compile time dependency on javax.xml:jaxrpc which is pulled in transitively via the ejb api. And it appears ejb-api is not used. > This should be changed to use the org.jboss.specs project version of the jaxrpc api directly. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3676) Minor dependency cleanup in jbossws-common

by Paul Gier (JIRA)

Paul Gier created JBWS-3676: ------------------------------- Summary: Minor dependency cleanup in jbossws-common Key: JBWS-3676 URL: https://issues.jboss.org/browse/JBWS-3676 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: productization Reporter: Paul Gier jbossws-common has an undeclared compile time dependency on javax.xml:jaxrpc which is pulled in transitively via the ejb api. And it appears ejb-api is not used. This should be changed to use the org.jboss.specs project version of the jaxrpc api directly. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3675) JBossWS 4.2.0.Final errata

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3675?page=com.atlassian.jira.plugin.... ] Alessio Soldano edited comment on JBWS-3675 at 7/26/13 12:47 PM: ----------------------------------------------------------------- JBoss AS 7.1.3.Final * [CXF-1519] Explicitly set the namespace of a WebFault * [CXF-2006] RespectBinding feature and not understood required extensibility elements * [JBWS-2561] XOP request not properly inlined * [JBWS-2480] Soap attachments are dropped on server response * [JBWS-3493] WS-Trust tests w/ PicketLink STS require PL 2.1.2.Final or greater * [JBWS-3441] Support CDI interceptors for POJO JAX-WS services * [AS7-537] Fixed on AS 8 or greater * [JBWS-3560] fastinfoset module is required in as713 * FIXME: [CXF-1519] Explicitely set the namespace of a WebFault * FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding * FIXME: [CXF-4600] Exception inheritance not working over SOAP protocol * FIXME: [JBWS-3330] RMI class loader disabled / CNFE with remote classloader * [JBWS-3079] FIXME: Add support for https protocol was (Author: asoldano): JBoss AS 7.1.3.Final ## [CXF-1519] Explicitly set the namespace of a WebFault ## [CXF-2006] RespectBinding feature and not understood required extensibility elements ## [JBWS-2561] XOP request not properly inlined ## [JBWS-2480] Soap attachments are dropped on server response ## [JBWS-3493] WS-Trust tests w/ PicketLink STS require PL 2.1.2.Final or greater ## [JBWS-3441] Support CDI interceptors for POJO JAX-WS services ## [AS7-537] Fixed on AS 8 or greater ## [JBWS-3560] fastinfoset module is required in as713 ## FIXME: [CXF-1519] Explicitely set the namespace of a WebFault ## FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding ## FIXME: [CXF-4600] Exception inheritance not working over SOAP protocol ## FIXME: [JBWS-3330] RMI class loader disabled / CNFE with remote classloader ## [JBWS-3079] FIXME: Add support for https protocol > JBossWS 4.2.0.Final errata > -------------------------- > > Key: JBWS-3675 > URL: https://issues.jboss.org/browse/JBWS-3675 > 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 > > -- 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, 5 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 July 2013