CXF & Spring Transactions
I'm coming from Spring-Webservices. I like that CXF supports contract-last since I'm in a prototype, rapid development phase for my work project. But I've noticed that weird things happen when using CXF with Spring Transactions. It appears that after so many web service calls, the DBCP pool is exhausted and connections aren't returned. This wasn't happening with Spring-Webservices. I've tried the 2.1-incubator-SNAPSHOT as well. It needs to be said that I am filtering out the Spring-2.0.6 dependencies and opting for 2.5. I'm using Spring's @Transactional annotation, JAXB, JaxWsProxyFactoryBean on client, jaxws:endpoint on server, Hibernate 3.1 and Oracle 9.2.0.8. -- View this message in context: http://www.nabble.com/CXF---Spring-Transactions-tp15814197p15814197.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF & Spring Transactions
I have interfaces with @WebService annotations. Each implementation implements the interfaces, and each has @WebService(endPointInterface), along with @Transactional from Spring. Is that enough information? Glen Mazza-2 wrote: > > Can you mock out the web service calls to confirm that it is CXF eating > up your DBCP pool and nothing something else? > > Glen > > Am Montag, den 03.03.2008, 13:19 -0800 schrieb Michael McCaskill: >> I'm coming from Spring-Webservices. I like that CXF supports >> contract-last >> since I'm in a prototype, rapid development phase for my work project. >> But >> I've noticed that weird things happen when using CXF with Spring >> Transactions. >> >> It appears that after so many web service calls, the DBCP pool is >> exhausted >> and connections aren't returned. This wasn't happening with >> Spring-Webservices. I've tried the 2.1-incubator-SNAPSHOT as well. It >> needs >> to be said that I am filtering out the Spring-2.0.6 dependencies and >> opting >> for 2.5. I'm using Spring's @Transactional annotation, JAXB, >> JaxWsProxyFactoryBean on client, jaxws:endpoint on server, Hibernate 3.1 >> and >> Oracle 9.2.0.8. > > > -- View this message in context: http://www.nabble.com/CXF---Spring-Transactions-tp15814197p15833351.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF & Spring Transactions
I have found the root of the problem, which fortunately isn't CXF related but a Spring-AOP (AspectJ) problem. Thanks. -- View this message in context: http://www.nabble.com/CXF---Spring-Transactions-tp15814197p15850223.html Sent from the cxf-user mailing list archive at Nabble.com.
Contract-last, empty List null
I've checked the response from my server side web service method. It is indeed not null and empty. But the client gets a null object back. I tried using the CXF 2.1-SNAPSHOT (for JAXB 2.1) but I couldn't get my services to work. What else can I try short of writing XSDs? -- View this message in context: http://www.nabble.com/Contract-last%2C-empty-List-null-tp15850232p15850232.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF & Spring Transactions
I was having an Aspect do some things using a @Before annotation. It seems it was interfering with the flow of things. It turns out this happens with Spring-WS as well, which is how I found out. I simply disabled the aspect and it is working (for the most part). I just have to fix my aspect. David Castañeda wrote: > > Can you explain it? > > how is your configuration now? > > -- > David Castañeda R. > > -- View this message in context: http://www.nabble.com/CXF---Spring-Transactions-tp15814197p15852485.html Sent from the cxf-user mailing list archive at Nabble.com.
