Library Path Issues

2009-10-08 Thread Anthony Schexnaildre
I have developed part of a site that I would like to embed as a library inside another webapp. All seems to be fine except that when a page in the library uses a component in that library the tapestry blows up because of path problems. For example in a page in the included library I referen

Re: Tapestry 5.1.0.2 and tapestry-spring-security 2.0.1

2009-04-06 Thread Anthony Schexnaildre
I also would love to see first class support for spring security in tapestry. I am currently having to define all this in xml. Spring Webflow is cool but I would have though security would have been higher on the priority list. -Anthony On Apr 6, 2009, at 5:35 PM, Borut BolĨina wrote: I'

Re: Tapestry-Spring-Security and Tapestry 5.1.0.x

2009-03-24 Thread Anthony Schexnaildre
Someone else mentioned that they were having issues with the same thing no more than a week ago. I don't remember them having a solution either. -Anthony On Mar 24, 2009, at 10:23 PM, Thiago H. de Paula Figueiredo wrote: Hi! Is it just me or Tapestry-Spring-Security doesn't work with Tape

Re: Spring root context and Tap 5.1

2009-03-17 Thread Anthony Schexnaildre
ntext). -Anthony On Mar 17, 2009 3:47 PM, "Inge Solvoll" wrote: Does that configuration mean that you can't inject T5 IoC services into spring? On Tue, Mar 17, 2009 at 3:47 PM, Anthony Schexnaildre wrote: > Thank you. > > -Anthony > > > On Mar 17, 2009, at 10:36 AM, Andy Pahne wrote: > > >> I think the ...

Re: Spring root context and Tap 5.1

2009-03-17 Thread Anthony Schexnaildre
web.xml tapestry.use-external-spring-context true Anthony Schexnaildre schrieb: From my reading it seems Tap 5.1 is supposed to be backwards compatible with 5.0.18 but not quite there yet. I am running Tapestry in the same webapp as RestEasy. I am creating a root

Spring root context and Tap 5.1

2009-03-17 Thread Anthony Schexnaildre
From my reading it seems Tap 5.1 is supposed to be backwards compatible with 5.0.18 but not quite there yet. I am running Tapestry in the same webapp as RestEasy. I am creating a root spring context that both resteasy and tapestry share. I just added 5.1 to try it out and I get an exception