After deploying the seambay example in Jboss, I encountered the following error while invoking the webservice AuctionService from soapUI:
[com.sun.istack.SAXException2: A cycle is detected in the object graph. This will cause infinitely deep XML: org.jboss.seam.example.seambay.Auction@1df2b92 -> org.jboss.seam.example.seambay.AuctionImage@1d90a6e -> org.jboss.seam.example.seambay.Auction@1df2b92]
After looking at the annotations in Auction and AuctionImage it just is very clear: the association between the two classes is bidirectional; and thus causing the Marshaller to throw this error. (Because it cannot find out when to stop following references).
After googling/thinking I added an @XmlTransient annotation to AuctionImage#getAuction (see patch) , and thus breaking the loop when marshalling.
Now the webserive produces some result and is not giving errors anymore!
The problem-yet-to-solve (curious how you guys would solve): With this XmlTransient, xml2object unmarshalling is not fully supported anymore (I broke the loop...).