I’d start with that, as we know that works. Maybe with a very minimal tweak to that
example, you can demonstrate your problem?
Mark
On 8 Jan 2014, at 19:30, Mark Proctor <mproctor(a)codehaus.org> wrote:
you have your marshal and unmarshal the wrong way around. Please
follow the example application:
https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/drools-c...
https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/drools-c...
Mark
On 8 Jan 2014, at 15:58, jroman <roman.jesus(a)wanadoo.es> wrote:
> Hi all,
>
> I am not sure if I have met a bug in kie-camel-xstream marshalling (drools
> 6.0.1). The use case is:
>
> Java client: MiniRESTClient.java
> - Build a list of commands, group them under a BatchExecutionCommand and
> send them to a camel route.
>
> Camel route: camel-client.xml
> - Marshal the commad, send it to a drools server and unmarshal the result.
>
>
> The problem is that the marshalling part seams to fail with:
>
>
> It seams that the xstream marshaler is building a java.util.ArrayList
> instead of the expected org.apache.cxf.message.MessageContentsList
>
> The funny thing is that, if I explicitly do the marshaling in the java
> client with:
>
>
>
> And remove the
>
> from the policy definition no exception is thrown and the client-server
> communication works as expected. Besides, I have the reverse policy in the
> server side and there is no problem there.
>
> Am I doing something wrong?
>
> I think I have attached everything needed to test the case: my_tests.zip
> <
http://drools.46999.n3.nabble.com/file/n4027607/my_tests.zip>
>
> Thanks for reading down to here and for any help you could provide.
>
>
>
>
> -----
> --
> jroman
> --
> View this message in context:
http://drools.46999.n3.nabble.com/Drools-6-0-1-xstream-marshaling-via-cam...
> Sent from the Drools: User forum mailing list archive at
Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-users