On Tue, 08 Apr 2014 10:04:20 -0300, Chris Mylonas <[email protected]>
wrote:
Hi t5 aficionados,
Hi!
Am I correct in following this thread...that it is best to think of
@inject as "lazy" inject? (After constructor)
No. It's not lazy because the injection is done before the service
instance.
If so, without knowledge of tapestry internally, sounds like a familiar
gotcha like onActivate/setupRender and instantiation/fetching-stuff
I'm sorry, but the analogy is completely off.
That plastic morphing sounds like a can of worms btw
Actually, no, this isn't related to Plastic at all. That NPE would happen
in the exact same way in Spring.
Again, service classes are *not* transformed by Plastic at all. Instead,
it creates proxies that delegate method calls to the service instances.
Just Tapestry pages, components, mixins and classes in the base package
are transformed.
Chasing-those-exceptions is never fun, although I'd prefer to do that
than compliance documentation and openssl heartbleed shenanigans! Cant
believe it'll be Wednesday soon!
Whoosh! :D
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
