I've been poking around trying to figure out a good "harmonious" way to provide a set of "web service" URLs as part of an application. By "web service" I don't necessarily mean any particular approach (SOAP or whatever) at this point. What I would like is to have some mechanism that could make an incoming HTTP POST to a service URL end up looking more-or-less like a plain old action invocation (possibly with the payload in the form of a FileBean).
So I'm thinking that one way to do this would be to use a filter that does something like what the multipart filter does. It'd have to interpret any sort of authentication header and then package up the payload as a parameter. Does that seem like a bad idea for some reason? I'm not terribly experienced with Stripes, and the web service APIs I'm familiar with are implemented as independent servlets. Seems to me that it's not unlikely that somebody's done something similar. -- Turtle, turtle, on the ground, Pink and shiny, turn around. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
