Hmm, good question. Are it some db services that you are accessing..? like warp?
<filter> <filter-name>guiceFilter</filter-name> <filter-class>com.wideplay.warp.servlet.WebFilter</filter-class> </filter> Then just map it to everything: <filter-mapping> <filter-name>guiceFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> 2009/8/28 Bas Gooren <b...@iswd.nl>: > Yeah, I've built Wicket pages which return XML responses before, so that's > not the problem. > > But since I have to adhere to a certain WSDL and hand-constructing the SOAP > response seems like the wrong thing to do, I was hoping that there might be > a way to say > > class WebservicePage extends WebPage { > public WebservicePage() { > SoapService service = new SoapService( Impl.class ); // Possibly guice > injected > service.handle( HttpServletRequest ... ); // Get the servlet request > through wicket > } > } > > But since that is wrapping a handler in a handler, it's not very clean > either. Anyway, the main issue remains: since I have google guice nicely set > up within Wicket, how do I build a webservice which has access to guice > injection? I am not using spring, and switching this application to spring > is not going to happen. > > I have found JAX-WS Guice integration (see > https://jax-ws-commons.dev.java.net/guice/), so maybe I can find a way to > make it use the wicket-guice injector. > > Bas > > ----- Original Message ----- From: "nino martinez wael" > <nino.martinez.w...@gmail.com> > To: <users@wicket.apache.org> > Sent: Friday, August 28, 2009 2:04 PM > Subject: Re: Wicket + Webservice > > >> doh, took a closer look at the blog, it's already described there.. So >> you know that wicket can return XML >> >> 2009/8/28 nino martinez wael <nino.martinez.w...@gmail.com>: >>> >>> Ahh ok, you can also make a web page return xml. Im not sure how SOAP >>> communicates. But this might be the way for you... >>> >>> 2009/8/28 Bas Gooren <b...@iswd.nl>: >>>> >>>> Nino, >>>> >>>> I read a blog post by Bruno borges on this (see >>>> http://code.google.com/p/wicket-rest/). But in my case I need to adhere >>>> to a >>>> WSDL provided by the payment provider. The WSDL specifies a SOAP >>>> binding, so >>>> that's what I need to implement. >>>> >>>> Bas >>>> >>>> ----- Original Message ----- From: "nino martinez wael" >>>> <nino.martinez.w...@gmail.com> >>>> To: <users@wicket.apache.org> >>>> Sent: Friday, August 28, 2009 1:16 PM >>>> Subject: Re: Wicket + Webservice >>>> >>>> >>>>> Going for the web page, you could in theory do REST... But how smooth >>>>> it are i do not know.. >>>>> >>>>> regards Nino >>>>> >>>>> 2009/8/28 Bas Gooren <b...@iswd.nl>: >>>>>> >>>>>> I would like to integrate a webservice callable by others into my >>>>>> existing Wicket application. >>>>>> The reason is that I'm integration a third-party payment provider and >>>>>> they provide a callback mechanism in the form of a WSDL I need to >>>>>> implement. >>>>>> >>>>>> Now I've taken a look at enunciate, which looks great btw, but it >>>>>> seems >>>>>> to operate next to wicket instead of integrated with wicket: as a >>>>>> separate >>>>>> filter. >>>>>> >>>>>> I'd like to be able to control the location where the webservice is >>>>>> mounted from wicket, and access my guice-injected services through >>>>>> wicket-guice integration. This way I have easy access to all the >>>>>> services >>>>>> and daos in my application >>>>>> >>>>>> The questions I have are: >>>>>> - is it possible to handle an incoming webservice request through a >>>>>> WebPage implementation? >>>>>> - if not, what would be a good alternative? (given the requirement >>>>>> that >>>>>> I'd like to be able to use the wicket-guice injector) >>>>>> >>>>>> Bas >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>>>> For additional commands, e-mail: users-h...@wicket.apache.org >>>>> >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>>> For additional commands, e-mail: users-h...@wicket.apache.org >>>> >>>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org