July 2013 - jbossws-issues - Jboss List Archives

[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 commented on JBWS-3675: --------------------------------------- JBoss AS 7.2.0.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 * [PLFED-390] PicketLink STS chokes on WS-Policy 1.5 tags * [AS7-537] Fixed on AS 8 or greater * [JBWS-3560] fastinfoset module is required in as720 * 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

10 years, 9 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 commented on JBWS-3675: --------------------------------------- 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

10 years, 9 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:46 PM: ----------------------------------------------------------------- JBoss AS 7.1.2.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 as712 * 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 as712 # 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

10 years, 9 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 commented on JBWS-3675: --------------------------------------- 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 as712 # 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

10 years, 9 months

1
0
0 / 0

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

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3675: ------------------------------------- Summary: 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3671) AbstractServerConfig keep stale reference to server config after reboot

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3671?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3671: ----------------------------------------------- Emmanuel Hugonnet (ehsavoie) <ehugonne(a)redhat.com> changed the Status of [bug 959426|https://bugzilla.redhat.com/show_bug.cgi?id=959426] from MODIFIED to POST > AbstractServerConfig keep stale reference to server config after reboot > ----------------------------------------------------------------------- > > Key: JBWS-3671 > URL: https://issues.jboss.org/browse/JBWS-3671 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.1.1 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > As a consequence of JBWS-3576 fix, the AbstractServerConfig's reference to the AS container ServerConfig might turn into a stale object if the server is reloaded through management. We need to clean up the static references in such cases. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3671) AbstractServerConfig keep stale reference to server config after reboot

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3671?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3671: ----------------------------------------------- Emmanuel Hugonnet (ehsavoie) <ehugonne(a)redhat.com> changed the Status of [bug 959426|https://bugzilla.redhat.com/show_bug.cgi?id=959426] from NEW to MODIFIED > AbstractServerConfig keep stale reference to server config after reboot > ----------------------------------------------------------------------- > > Key: JBWS-3671 > URL: https://issues.jboss.org/browse/JBWS-3671 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.1.1 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > As a consequence of JBWS-3576 fix, the AbstractServerConfig's reference to the AS container ServerConfig might turn into a stale object if the server is reloaded through management. We need to clean up the static references in such cases. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3671) AbstractServerConfig keep stale reference to server config after reboot

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3671?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3671: ----------------------------------------------- Emmanuel Hugonnet (ehsavoie) <ehugonne(a)redhat.com> made a comment on [bug 959426|https://bugzilla.redhat.com/show_bug.cgi?id=959426] https://github.com/jbossas/jboss-eap/pull/259 > AbstractServerConfig keep stale reference to server config after reboot > ----------------------------------------------------------------------- > > Key: JBWS-3671 > URL: https://issues.jboss.org/browse/JBWS-3671 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.1.1 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > As a consequence of JBWS-3576 fix, the AbstractServerConfig's reference to the AS container ServerConfig might turn into a stale object if the server is reloaded through management. We need to clean up the static references in such cases. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3655) wsdlLocation in ejb-jar throws error for schema import

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3655?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3655: ---------------------------------- Fix Version/s: jbossws-cxf-4.2 > wsdlLocation in ejb-jar throws error for schema import > ------------------------------------------------------ > > Key: JBWS-3655 > URL: https://issues.jboss.org/browse/JBWS-3655 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: jbossws-cxf-4.1.3 > Reporter: Mustafa Musaji > Assignee: Jim Ma > Fix For: jbossws-cxf-4.2 > > Attachments: awesome.zip > > > The use case is as follows: > EAR that contains EJB-JAR and JAR. The JAR contains wsdl in META-INF but referenced from wsdlLocation in EJB-JAR to avoid JBoss generating it's own WSDL without external schema). On deployment the error we get is: > {noformat} > Caused by: java.io.IOException: JBAS015526: Child 'META-INF/wsdl/Awesome_schema1.xsd' not found for VirtualFile: "/content/awesome.ear/awesome-ejb-0.0.1-SNAPSHOT.jar" > at org.jboss.as.webservices.util.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:61) > at org.jboss.as.webservices.util.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:71) > at org.jboss.ws.common.deployment.ResourceResolverImpl.resolve(ResourceResolverImpl.java:76) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:228) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:253) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:257) > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:92) > ... 14 more > {noformat} > Removing the wsdlLocation from the ejb-jar fixes this but the use case is that JBoss should be able to load the schema from the classpath since the wsdl was loaded from the classpath. > I will attach a test case to the JIRA to replicate this behaviour. It's a maven build that use cxf-java2ws-plugin to generate the xsd imports and WSDL in the JAR file. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3655) wsdlLocation in ejb-jar throws error for schema import

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3655?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3655: ---------------------------------- Component/s: jbossws-cxf > wsdlLocation in ejb-jar throws error for schema import > ------------------------------------------------------ > > Key: JBWS-3655 > URL: https://issues.jboss.org/browse/JBWS-3655 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.1.3 > Reporter: Mustafa Musaji > Assignee: Jim Ma > Fix For: jbossws-cxf-4.2 > > Attachments: awesome.zip > > > The use case is as follows: > EAR that contains EJB-JAR and JAR. The JAR contains wsdl in META-INF but referenced from wsdlLocation in EJB-JAR to avoid JBoss generating it's own WSDL without external schema). On deployment the error we get is: > {noformat} > Caused by: java.io.IOException: JBAS015526: Child 'META-INF/wsdl/Awesome_schema1.xsd' not found for VirtualFile: "/content/awesome.ear/awesome-ejb-0.0.1-SNAPSHOT.jar" > at org.jboss.as.webservices.util.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:61) > at org.jboss.as.webservices.util.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:71) > at org.jboss.ws.common.deployment.ResourceResolverImpl.resolve(ResourceResolverImpl.java:76) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:228) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:253) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:257) > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:92) > ... 14 more > {noformat} > Removing the wsdlLocation from the ejb-jar fixes this but the use case is that JBoss should be able to load the schema from the classpath since the wsdl was loaded from the classpath. > I will attach a test case to the JIRA to replicate this behaviour. It's a maven build that use cxf-java2ws-plugin to generate the xsd imports and WSDL in the JAR file. -- 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

10 years, 9 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