I'm having this same problem. I don't understand why a jaxrpc-mapping.xml would be necessary for this, if I'm using JSR-181 annotations. I don't have any other configuration files, it's all in annotations. If I comment out all the remote-methods that have JavaBeans as return types or parameters, it all works great. But as soon as I pass one of my JavaBeans as an argument, I get the same error as has been posted here already by adam. The JavaBeans I'm talking about all have public no-arg constructors, getter/setter methods for all fields (which are String or primitives), and they don't implement java.rmi.Remote.
>From http://java.sun.com/developer/technicalArticles/J2EE/j2ee_ws/ anonymous wrote : | JAX-RPC also supports something called a value type, which is a class that can be passed between a client and a service as a parameter or a return value. A value type must follow these rules: | | * It must have a public default constructor. | * It must not implement java.rmi.Remote. | * Its fields must be JAX-RPC supported types. Also, a public field cannot be final or transient, and a non-public field must have the corresponding getter and setter methods. | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3948241#3948241 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3948241 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
