I have deployed an .ear file that runs stably on 4.0.3SP1 to 4.2.2GA. Following the deployment, most of my webservices operate correctly (using the same client I used with v4.0.3SP1). However when I try to call a webservice which uses a complex type (in this case, arrayType) Jboss throws the following exception: 2008-11-19 14:44:11,912 ERROR [org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC] SOAP request exception org.jboss.ws.WSException: Cannot obtain attribute: {http://schemas.xmlsoap.org/soap/encoding/}arrayType at org.jboss.ws.core.jaxrpc.binding.SOAPArrayDeserializer.getComponentTypeFromAttribute(SOAPArrayDeserializer.java:172) at org.jboss.ws.core.jaxrpc.binding.SOAPArrayDeserializer.deserialize(SOAPArrayDeserializer.java:70) at org.jboss.ws.core.binding.DeserializerSupport.deserialize(DeserializerSupport.java:60) at org.jboss.ws.core.soap.XMLContent.unmarshallObjectContents(XMLContent.java:180) at org.jboss.ws.core.soap.XMLContent.transitionTo(XMLContent.java:97) at org.jboss.ws.core.soap.SOAPContentElement.transitionTo(SOAPContentElement.java:140) at org.jboss.ws.core.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:171) at org.jboss.ws.core.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:263) at org.jboss.ws.core.EndpointInvocation.getRequestParamValue(EndpointInvocation.java:115) at org.jboss.ws.core.EndpointInvocation.getRequestPayload(EndpointInvocation.java:135) at org.jboss.ws.core.server.DelegatingInvocation.getArgs(DelegatingInvocation.java:82) at org.jboss.wsf.container.jboss42.DefaultInvocationHandler.invoke(DefaultInvocationHandler.java:102) at org.jboss.wsf.container.jboss42.DefaultInvocationHandlerJAXRPC.invoke(DefaultInvocationHandlerJAXRPC.java:57) at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:408) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122) at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) Any suggestions on what might be going on here are most appreciated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191324#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...