Thanks! Tried that, the method is never hit when I set a breakpoint and the
services aren't exposed. I have tried putting other contribute methods in
that module class and they're hit, just not the one below. I did not make
any changes...

On Wed, Jun 23, 2010 at 11:36 AM, Igor Drobiazko
<igor.drobia...@gmail.com>wrote:

> You can contribute to the configuration of ApplicationContextCustomizer
> service.
>
>    public static void contributeApplicationContextCustomizer(
>            OrderedConfiguration<ApplicationContextCustomizer> config) {
>
>        ApplicationContextCustomizer customizer = new
> ApplicationContextCustomizer() {
>            public void customizeApplicationContext(
>                    ServletContext servletContext,
>                    ConfigurableWebApplicationContext appContext) {
>                appContext.setConfigLocation("classpath:myContext.xml");
>            }
>        };
>        config.add("MyApplicationContextCustomizer", customizer);
>    }
>
>
> On Wed, Jun 23, 2010 at 10:22 AM, Inge Solvoll <inge.tapes...@gmail.com
> >wrote:
>
> > Hi!
> >
> > One of my coworkers has produced a new library (jar) that contains a
> bunch
> > of java classes and a spring xml file. I would really like to be able to
> > use
> > the normal T5-style dropin for this jar, autoloading the services into my
> > app registry without the need for further wiring. But there's a spring
> xml
> > file involved, so that won't work out of the box.
> >
> > I'm considering rewriting the classes to support Tapestry IOC instead of
> > Spring, but that seems a bit unnecessary, considering that spring can be
> > integrated into Tapestry IOC. So, is there a way to create the spring
> > context from the xml file, and load the provided spring beans into the T5
> > module?
> >
> > I'm looking at the TapestrySpringFilter for leads, but as far as I can
> see,
> > it only provides support for getting the spring context from the servlet
> > context...
> >
>
>
>
> --
> Best regards,
>
> Igor Drobiazko
> http://tapestry5.de/blog
>

Reply via email to