July 2011 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3275) AddressingFeature required Client should throw exception when the wsa header is missing in the inbound message

by Jim Ma (JIRA)

AddressingFeature required Client should throw exception when the wsa header is missing in the inbound message --------------------------------------------------------------------------------------------------------------- Key: JBWS-3275 URL: https://issues.jboss.org/browse/JBWS-3275 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.4.1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.0 Related CXF issue: https://issues.apache.org/jira/browse/CXF-3458 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBWS-2338) Review our SPI abstractsions and interfaces

by Richard Opalka (JIRA)

Review our SPI abstractsions and interfaces ------------------------------------------- Key: JBWS-2338 URL: https://jira.jboss.org/jira/browse/JBWS-2338 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Affects Versions: jbossws-native-3.0.4, jbossws-metro-3.0.4, jbossws-cxf-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 Terminology: DA = Deployment Aspect Issues: * WSFRuntime isn't good abstraction and should be removed from our SPI because it doesn't integrate with JBossAS deployers architecture very well (it's issue is it depends on web container runtime which can be unavailable at AS start time (e.g. there can be multiple webservice archives in deploy directory that are started before web container is available) * We moved some servlet dependent DAs to servlet lifecycle init()/destroy() methods. The problem of it is it executes DAs for whole deployment, not just particular deployed endpoint. (IOW we execute the same DAs multiple times if there are more than one webservice endpoints in deployment. This need SPI review and repair) -- 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

12 years, 5 months

3
12
0 / 0

[JBoss JIRA] Created: (JBWS-3235) org.jboss.ws.core.soap.SOAPFaultImpl should be Serializable

by david.boeren (JIRA)

org.jboss.ws.core.soap.SOAPFaultImpl should be Serializable ----------------------------------------------------------- Key: JBWS-3235 URL: https://issues.jboss.org/browse/JBWS-3235 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.4.1 Reporter: david.boeren Priority: Trivial Fix For: jbossws-native-4.0 org.jboss.ws.core.soap.SOAPFaultImpl is currently not Serializable at runtime, which is counterintuitive since descendants of Throwable generally are, and all descendants of Throwable are marked as implementing the Serializable interface. There is a workaround to extract the message and place it in a different Exception class but this is an extra step that should not be necessary. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-3120) Virtual host feature have been removed in AS 6 series

by Richard Opalka (JIRA)

Virtual host feature have been removed in AS 6 series ----------------------------------------------------- Key: JBWS-3120 URL: https://jira.jboss.org/browse/JBWS-3120 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-native-4.0, jbossws-metro-4.0, jbossws-cxf-4.0 We should remove the test from our test suite and update our SPI accordingly to remove this feature for AS 6 -- 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

12 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-2570) @SchemaValidation annotation does not work if schemaLocation property is not specified

by Nick Gudushauri (JIRA)

@SchemaValidation annotation does not work if schemaLocation property is not specified -------------------------------------------------------------------------------------- Key: JBWS-2570 URL: https://jira.jboss.org/jira/browse/JBWS-2570 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: jboss 4.2.3.GA jbossws-native-3.0.5.GA Reporter: Nick Gudushauri Steps to reproduce: 1. Create simpe JAX-WS service 2. Annotate it with @SchemaValidation annotation WITHOUT specifying optional schemaLocation property (In such case schema should be extracted from the WSDL) 3. Send test request As the result no schema validation is performed and you will see the following messages in log: 17:07:13,421 INFO [SOAPBodyElementDoc] Validating: DOM_VALID 17:07:13,421 WARN [SchemaExtractor] Cannot find element: {http://schemas.xmlsoap.org/wsdl/}types 17:07:13,625 INFO [UCCServicesBean] Invoking UCC registerClearingOrder service by cer 17:07:14,515 INFO [SOAPBodyElementDoc] Validating: DOM_VALID 17:07:14,515 WARN [SchemaExtractor] Cannot find element: {http://schemas.xmlsoap.org/wsdl/}types The problem root is that org.jboss.ws.extensions.validation.SchemaExtractor class could not load 'types' element from WSDL as this element does not present in WSDL directly but imported via 'import' element. -- 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

12 years, 6 months

6
9
0 / 0

[JBoss JIRA] Created: (JBWS-3256) Failed to load users/passwords/role files

by Richard Opalka (JIRA)

Failed to load users/passwords/role files ----------------------------------------- Key: JBWS-3256 URL: https://issues.jboss.org/browse/JBWS-3256 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Fix For: jbossws-native-4.0 12:16:56,434 ERROR [org.jboss.security.auth.spi.UsersRolesLoginModule] (http-nucleus%2F127.0.0.1-8080-1) Failed to load users/passwords/role files: java.io.IOException: No properties file: users.properties or defaults: defaultUsers.properties found at org.jboss.security.auth.spi.Util.loadProperties(Util.java:201) [picketbox-4.0.0.Alpha4.jar:4.0.0.Alpha4] at org.jboss.security.auth.spi.UsersRolesLoginModule.loadUsers(UsersRolesLoginModule.java:186) [picketbox-4.0.0.Alpha4.jar:4.0.0.Alpha4] at org.jboss.security.auth.spi.UsersRolesLoginModule.createUsers(UsersRolesLoginModule.java:200) [picketbox-4.0.0.Alpha4.jar:4.0.0.Alpha4] at org.jboss.security.auth.spi.UsersRolesLoginModule.initialize(UsersRolesLoginModule.java:127) [picketbox-4.0.0.Alpha4.jar:4.0.0.Alpha4] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_20] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.6.0_20] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_20] at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_20] at javax.security.auth.login.LoginContext.invoke(LoginContext.java:771) [:1.6.0_20] at javax.security.auth.login.LoginContext.access$000(LoginContext.java:203) [:1.6.0_20] at javax.security.auth.login.LoginContext$4.run(LoginContext.java:698) [:1.6.0_20] at javax.security.auth.login.LoginContext$4.run(LoginContext.java:696) [:1.6.0_20] at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_20] at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:695) [:1.6.0_20] at javax.security.auth.login.LoginContext.login(LoginContext.java:594) [:1.6.0_20] at org.jboss.security.plugins.auth.JaasSecurityManagerBase.defaultLogin(JaasSecurityManagerBase.java:553) [picketbox-4.0.0.Alpha4.jar:4.0.0.Alpha4] at org.jboss.security.plugins.auth.JaasSecurityManagerBase.authenticate(JaasSecurityManagerBase.java:487) [picketbox-4.0.0.Alpha4.jar:4.0.0.Alpha4] at org.jboss.security.plugins.auth.JaasSecurityManagerBase.isValid(JaasSecurityManagerBase.java:365) [picketbox-4.0.0.Alpha4.jar:4.0.0.Alpha4] at org.jboss.as.web.security.JBossWebRealm.authenticate(JBossWebRealm.java:88) [jboss-as-web-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.authenticator.BasicAuthenticator.authenticate(BasicAuthenticator.java:180) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:660) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at java.lang.Thread.run(Thread.java:636) [:1.6.0_20] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (JBWS-3246) Resuscitate JSON

by Richard Opalka (JIRA)

Resuscitate JSON ---------------- Key: JBWS-3246 URL: https://issues.jboss.org/browse/JBWS-3246 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-integration, jbossws-native Reporter: Richard Opalka Fix For: jbossws-native-4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-3294) Remove ws-eventing implementation from native

by Richard Opalka (JIRA)

Remove ws-eventing implementation from native --------------------------------------------- Key: JBWS-3294 URL: https://issues.jboss.org/browse/JBWS-3294 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka The jbossws-native ws-eventing implementation is not being maintained / supported. Even more the WS-Eventing spec. is considered deprecated. The upcoming WS-Eventing from WS-RA specification is it's successor. See http://www.w3.org/2002/ws/ra/snapshots/cr/wseventing.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-3276) Implement support for POJO endpoints with no web.xml in archive

by Richard Opalka (JIRA)

Implement support for POJO endpoints with no web.xml in archive --------------------------------------------------------------- Key: JBWS-3276 URL: https://issues.jboss.org/browse/JBWS-3276 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Fix For: jbossws-native-4.0, jbossws-cxf-4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-3280) Avoid building Spring Bus when deployment has no spring descriptor

by Alessio Soldano (JIRA)

Avoid building Spring Bus when deployment has no spring descriptor ------------------------------------------------------------------ Key: JBWS-3280 URL: https://issues.jboss.org/browse/JBWS-3280 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano The DescriptorDeploymentAspect currently relies on Spring availability in the classloader for deciding to generate a default jbossws-cxf.xml. Generally speaking, we should probably go the "Spring" way only when the deployment comes with a jbossws-cxf.xml (and spring is actually available ;-)), so the user explicitly asked for that. We might even evaluate changing the logic in JBossWSBusFactory to avoid using Spring when no spring descriptor is found (basically the same the CXF 2.4 SpringBusFactory does in public Bus createBus(String cfgFiles[], boolean includeDefaults) and we override in our JBossWS version of that factory). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues July 2011