Ok got a little further. I found out that the defaultContent can be set if
you add a List to the message content like so:
message.setContent(List.class, Arrays.asList(new String[] { "result" }));
Now I run into another problem that I described in another thread:
http://old.nabble.com/Response-object-is-null-td28859579.html
Thanx so far.
Ronald
Ronald Pieterse wrote:
>
> In the mean time I've been playing with an interceptor trying to do the
> thing I want and I succeeded in removing the Exception from the response.
> Now I also tried to put some new content (a string) in the message but
> that does not go well. When I debug I see that the Exception resided in
> the 'defaultContent' property of the message and when I put something in
> the message it resides in the 'content' of the message. Thus it does not
> appear in my response at all - the soap body remains empty.
>
> I can not find any setter for this property. How does this work? And is
> this a good way anyway to handle this kind of stuff or would you recommend
> using the invoker strategy?
>
> Thanx.
> Ronald
>
>
> dkulp wrote:
>>
>>
>> Hmm... can you package up a small test case. Not sure what is going on.
>> Could be a classloader issue, but I'm not sure.
>>
>> For the constructor, I would pass the impl bean of your service. That
>> would
>> be the "default" that the normal factory would end up doing.
>>
>> Dan
>>
>>
>
>
--
View this message in context:
http://old.nabble.com/Replace-Fault-with-custom-response-tp28751052p28860665.html
Sent from the cxf-user mailing list archive at Nabble.com.
