So changing this around seems to correct it. I'm not sure why though, to
my knowledge it shouldn't have been using a proxy.
public class ChangeProcessAction {
private StatusService statusService;
private OrderService orderService;
private Status status;
private Integer orderId;
Ill give this a whirl, and you're probably right, but this used to work
while using DBCP. Any idea as to why this would be broken in c3p0? I
tried to do some digging under the hood but couldn't find sources the
classes that were breaking.
Thanks,
-Tim
Greg Lindholm wrote:
Wild guess you
Wild guess you are trying to serialize (with JSON plugin) a
Hibernate proxy object.
Maybe your object has a reference to another lazy loaded object or collection.
Using reflection on a proxy object is usually a bad idea.
You may need to clone the object (to get a real one) first before
serial
Hello,
I just recently switched to c3p0 and it fixed some other issues I
was having with dbcp, but another has arisen.
It seems to be a combination of using the c3p0 data source along
with the JSON plugin. Here's my (slightly shortened) stacktrace:
Caused by: org.apache.struts2.json.JSO
4 matches
Mail list logo
