I've hit a little bit of a roadblock dealing with an EJB3 persistent Entity that is also returned via an operation on one of my JAX-RPC Service endpoints. The problem is this; the class being returned has a CMR to another EJB3 Entity. Let's say the model looks like this:
Invoice <>---> LineItem (Invoice has a Collection of LineItems) In order to set this CMR up, you have to use a java.util.Collection. The problem here is that when I run wscompile, it (wscompile) notices that it needs to return Invoice from one of my Service Endpoints and complains that one of it's (Invoice's) properties is a Collection. So, it's looking like I can have only one or the other here. I can either stop using the explicit CMR to or I can stop returning that object via my endpoint. Neither one of those solutions are very palatable. I'm sure that I could just code a JAX-RPC compliant version (DTO like) of Invoice, but that seems a waste. Is there a solution out there to this problem that I'm missing? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919700#3919700 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919700 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
