Can you please open a JIRA with both JAXRS and Aegis being listed as affected components. I will then create a test and will see if Benson's help is needed...
thanks, Sergey -----Original Message----- From: Alan Hazelton [mailto:[email protected]] Sent: Thu 1/7/2010 12:43 AM To: [email protected] Subject: RE: Issue with multiple REST methods having List<T> arguments I'm using Aegis. My resource is defined like this: @Path("/") public class SomeResource { @POST @Path("/foo/update") void postFoo(List<Foo> list) {} @POST @Path("/bar/update") void postBar(List<Bar> list) {} } So there is no conflict in the message paths. When I stop the server in the debugger I can see that in the org.apache.cxf.aegis.type.TypeUtil class the getReadTypeStandalone() method is invoked to get the top level type. In the first case it will be ArrayOfFoo and the type is located and my method called with the correct list object un-marshalled from XML. In the second case, the ArrayOfBar is not found in the AegisContext and null is returned by the getReadTypeStandalone method. The part that really confuses me is that if at runtime (after restarting the server) I invoke the postBar method before invoking the postFoo method, the ArrayOfBar type is located but not the ArrayOfFoo type. -- View this message in context: http://old.nabble.com/Issue-with-multiple-REST-methods-having-List%3CT%3E-arguments-tp27023942p27055337.html Sent from the cxf-user mailing list archive at Nabble.com.
