15/02: RESTEasy problems
Category: JBoss Seam | Posted by: JohnHaselden
Well, not so much problems, but a problem - I can't persist!
Having decided to use RESTEasy on a project we're currently working on rather than using the hand-rolled implementation of REST we were using previously. For read operations, this isn't a problem - however I'm not able to persist any updates.
This is becoming such a problem that I'm getting really, really close to ripping out the update part and going back to the hand-rolled solution just for this area as too much time has been invested to get to this point to revert every other retrieval mechanism. Plus that part works reasonably well (although returning XML doesn't seem as simple as it should be).
If anyone else has some insight into this particular problem, please let me know before I spend a couple of days implementing a replacement solution.
Some background: we're using POJOs, Seam 2.1.0 SP1 and PostgreSQL on JBoss 4.2.3. The persist call grabs the next value from hibernate_sequence but doesn't write anything else into the logs. The one class we're trying to persist has the @ID as a long, one String and a Float object.
Having decided to use RESTEasy on a project we're currently working on rather than using the hand-rolled implementation of REST we were using previously. For read operations, this isn't a problem - however I'm not able to persist any updates.
This is becoming such a problem that I'm getting really, really close to ripping out the update part and going back to the hand-rolled solution just for this area as too much time has been invested to get to this point to revert every other retrieval mechanism. Plus that part works reasonably well (although returning XML doesn't seem as simple as it should be).
If anyone else has some insight into this particular problem, please let me know before I spend a couple of days implementing a replacement solution.
Some background: we're using POJOs, Seam 2.1.0 SP1 and PostgreSQL on JBoss 4.2.3. The persist call grabs the next value from hibernate_sequence but doesn't write anything else into the logs. The one class we're trying to persist has the @ID as a long, one String and a Float object.
Comments
JohnHaselden wrote:
Possibly for another project, but the majority of stuff we're working on at the moment is Seam focussed.
17/02 16:56:51
JohnHaselden wrote:
I needed to add the @Transactional annotation to the method.