So I spent sometime with a fellow coworker this morning, "non tapestry
developer, but spring developer" and we discussed these issues I ran into
over the weekend. He was able to provide me with some basic info enabling me
to overcome the majority of my issues and understandings, but still a little
confused on one last question. 

He say's what I'm calling a factory is actually a service locator and that
AutoMateParser should be defined as a service in the AppModule. 

He also stated the objects I use to pass in through the constructor now need
to be passed in through set methods and that I could use super.set to pass
up through the extended classes which all makes sense to me now. "basic java
knowledge I should already know :( " 

The last question where I'm still a little confused is related to using
services inside extended classes. Because I'm declaring AutoMateParser.class
as a service, but extending say Parser.class, would I be able to inject my
services inside my extended class without having to declare Parser.class in
my AppModule a service? My assumption would be yes since the compiler sees
Parser.class as just AutoMateParser.class at runtime, but I'm not sure how
tapestry would see it. 

If my above assumption is incorrect, should I be extending Parser.class or
should I be Injecting Parser.class into AutoMateParser as a tapestry
service? This would be much less ideal though.

Pointing out thread safety, I wouldn't actually be using @Inject on my
properties as describe above, but rather constructor service injection with
final. Hopefully my understanding on that is clear as well. 

Thanks Guys for all the help. Looking forward to a Tap5 class at some point.  





--
View this message in context: 
http://tapestry.1045711.n5.nabble.com/Question-tapestry-service-tp5715573p5715600.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to