Re: T5: replacing the ComponentInstantiatorSource service

2007-09-14 Thread Tom Davies
Thanks for the help. On 14/09/2007, at 12:30 AM, Howard Lewis Ship wrote: Oh, then ComponentClassEnhancementWorker is almost certainly the way to go. At the moment I'm persisting with ComponentInstantiatorSource, as I can do *anything* to the class with that, and I'm still

Re: T5: replacing the ComponentInstantiatorSource service

2007-09-14 Thread Tom Davies
On 15/09/2007, at 1:09 PM, Tom Davies wrote: I think I need to explictly @Inject 'ConfigurationAliasContribution configuration', but I can't figure out what Id to use... No! The services injected into buildCalComponentInstantiator needed to be injected explictly! Got it now! Thanks

Re: T5: replacing the ComponentInstantiatorSource service

2007-09-13 Thread Tom Davies
On 13/09/2007, at 9:09 AM, Howard Lewis Ship wrote: I don't know much about CAL ... could this kind of thing be accomplished by extending the ComponentClassEnhancementWorker chain of command? Or is CAL based on the raw Javassist APIs? Hi Howard, I hadn't seen that class. It *almost*

T5: replacing the ComponentInstantiatorSource service

2007-09-12 Thread Tom Davies
Hi, I want to override the ComponentInstantiatorSource service with my own implementation (so that I can add another Translator to the Javassist ClassPool). It seems that I can't simply define a duplicate of the service in my own module, which is fair enough. What's the approach to use?

Re: T5: replacing the ComponentInstantiatorSource service

2007-09-12 Thread Tom Davies
On 13/09/2007, at 12:00 AM, Howard Lewis Ship wrote: I'd love to know why you want to do this ... it indicates to me that there needs to be some additional configuration available to CIS to support your needs. I don't know if I have a valid use-case, but what I'm doing is

Re: T5 on JDK 1.6 or newer

2007-08-26 Thread Tom Davies
On 25/08/2007, at 3:01 AM, Stephan Schwab wrote: We've been experiencing strange behaviour of our now growing application Savila and as well with another project we are working on. Both use Tapestry 5.0.5. Our development machines run with Mac OS X and we use JDK 1.5 that comes with it.