From: Matteo B. <m....@on...> - 2012-01-18 14:26:15
|
OK, so Unified Invoker should be the right way to go... Thanks a lot, MB Il 18/01/2012 15:13, Bill Burke ha scritto: > You shouldn't be using resteasy as an RPC mechanism. REST is very > message oriented where your message format is an HTTP request or > response. It is not RPC and you just won't be able to get a one-to-one > mapping between an EJB remote interface and REST/Resteasy. > > On 1/18/12 3:27 AM, Matteo Bruni wrote: >> Any hint on this issue? >> >> MB >> >> Il 29/12/2011 16:03, Matteo Bruni ha scritto: >>> Hi, I'm approaching Resteasy since we're migrating our application from >>> JBoss4 to JBoss6, and we were using the unified invoker servlet to >>> access EJBs via HTTP (since most of our customers, though this is a java >>> client application, have firewall/proxy restrictions that don't allow >>> them to connect directly via a socket to the server). Before trying to >>> configure a unified invoker on JBoss6, I was looking for some other way >>> to accomplish this task, and stumbled upon Resteasy, which, even though >>> not designed to do these duties, could be an easy and quick way to set >>> up HTTP method invocation. >>> So I started annotating with @Path, @POST (even if it isn't probably >>> suited for this, but we are mapping Stateless Session EJBs, which don't >>> have a role separation like Entity beans could have, their methods don't >>> map "creation", "removal", "update" and "find" actions and thus I'm >>> using POST verb for all methods indistinctly) and such, but discovered, >>> reading the specs, that there can be only ONE method parameter (the so >>> called "entity parameter") that is not annotated with @*Param, for which >>> my custom MessageBodyReader/Writer is used (I would like to use standard >>> Java Serialization to pass any kind of Object to my beans), but I'm >>> having several parameters, and if I annotate them with @*Param, they >>> can't be streamed to a custom media type like the one I'm trying to >>> create, but if I don't I get an error probably caused by infringing the >>> specs. >>> >>> My problem is: what should I do to invoke those methods with several >>> params? Do I need to write wrappers, which accept ONE parameter (which >>> could be a POJO containing references to original parameters instances) >>> and that invoke the EJB unwrapping the POJO param? Am I looking in the >>> wrong direction and I didn't notice another (probably more correct) way >>> to do this? >>> >>> Thanks in advance, >>> Matteo Bruni >>> >>> ------------------------------------------------------------------------------ >>> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex >>> infrastructure or vast IT resources to deliver seamless, secure access to >>> virtual desktops. With this all-in-one solution, easily deploy virtual >>> desktops for less than the cost of PCs and save 60% on VDI infrastructure >>> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox >>> _______________________________________________ >>> Resteasy-users mailing list >>> Res...@li... >>> https://lists.sourceforge.net/lists/listinfo/resteasy-users >> >> ------------------------------------------------------------------------------ >> Keep Your Developer Skills Current with LearnDevNow! >> The most comprehensive online learning library for Microsoft developers >> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, >> Metro Style Apps, more. Free future releases when you subscribe now! >> http://p.sf.net/sfu/learndevnow-d2d >> _______________________________________________ >> Resteasy-users mailing list >> Res...@li... >> https://lists.sourceforge.net/lists/listinfo/resteasy-users |