I am looking for something similar, because we use our data models as our messaging models and the problem is when you couple this with Hibernate...since we are using AOP Pointcuts, the transaction begins after CXF/JAXB has done the unmarshalling and the transaction ends before CXF/JAXB has done the marshalling. Therefore any lazy loaded objects that have not been touched throw a LazyInitializationException.
I want to be able to start a transaction thru a CXF interceptor/servlet, and then end the transaction after the marshalling has happened (but still be able to through a SOAP Fault if the transaction fails. Would this be easier with a filter or through interceptors? If through interceptors, any suggestions as to what phase I would need to do it so that I can keep the transaction open while the JAXB marshals the response and make sure a SOAP Fault still is thrown for a transaction error. -- View this message in context: http://cxf.547215.n5.nabble.com/cxf-and-spring-transaction-tp5521251p5713069.html Sent from the cxf-user mailing list archive at Nabble.com.
