Em Sat, 19 Dec 2009 23:31:24 -0200, Piero Sartini <[email protected]>
escreveu:
I will try to come up with some integration module. What parts do you
think could be integrated?
Injecting services sounds doable... but when it comes to scopes I am
lost.
I thought of just instantiating Weld, getting all the declared beans and
add them to a Tapestry registry. You can take a look at tapestry-string to
draw some inspiration.
It would be great if scopes could be handled by 299 if present.. need
to dig into the
code to get a picture of how this works in tapestry.
Open the sources and search for uses of the @Scope annotation and classes
named *Scope.
You are right. But where do you find pure JavaSE?
Swing and command-line applications also benefit from IoC and DI. ;)
Not in the web world
- thats for sure :-)
Tapestry applications don't need to have any direct dependencies in the
Servlet API. If someone implements some HTTP server in Java not based in
the Servlet API (I guess there must be at least one around), you can adapt
Tapestry to work on it. Tapestry applications would work out of the box,
as long as they don't use the Servlet API directly.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
