Hi Hugo,
It is exactly that and I didn't understand how to do that. Whatever I test,
it works but it is intrusive.
I re-read the documentation about tapestry-ioc and I still not understand
how to do that. I need an example of webapp with 3 layers around the ioc to
see how tapestry-ioc gives the
Ok, as you can see in the tapestry-ioc documentation there are three
ways of injecting dependencies into services. Only one of them is
actually intrusive, the As parameters to the service implementation
class' constructor (for autobuilt services) one. If you use this way
then you will need to
Sorry, I'm trying to understand enough well to develop my application
correctly.
So, imagine I have 2 classes ClassA and ClassB from 2 differents layers.
With the IoC in ClassA I should have just a member named ServiceClassB sab
with its getter and setter. ServiceClassB is the interface ClassB
Why don't you declare your ClassA as a service too ? This way you could
inject the ServiceClassB into it without any change on ClassA.
Michael Bernagou wrote:
Sorry, I'm trying to understand enough well to develop my application
correctly.
So, imagine I have 2 classes ClassA and ClassB from 2
On Mon, 17 Dec 2007 06:35:43 -0200, Michael Bernagou
[EMAIL PROTECTED] wrote:
It is exactly that and I didn't understand how to do that. Whatever I
test,
it works but it is intrusive.
I re-read the documentation about tapestry-ioc and I still not understand
how to do that. I need an example
On Mon, 17 Dec 2007 08:33:52 -0200, Michael Bernagou
[EMAIL PROTECTED] wrote:
public class UserModule {
public static ServiceClassB build(ServiceUserDao userDao){
ClassB cb = new ClassB(userDao);
return cb;
}
public static ServiceUserDao build() {
UserDao dao = new
Thanks for the TYPO Thiago. Also thanks for the project examples, I'll need
to wait beeing at home to test since the security system here at the office
block them to be download.
Making my ClassA a service? I'm going to try but it means ClassA will be
instanciate only by Tapestry-ioc else I will
I think the easiest way to implement that is to use auto-building and to
just declare each service dependencies in it's implementation class.
See the Binding and Autobuilding and Injecting Dependencies for
Autobuilt Services section here
m, i think there's something missing here
If i'm understanding correctly you want tapestry-ioc to manage all your
services (either presentation stuf, db stuff, etc) and you don't want it
to be intrusive. You don't want to reference any tapestry-ioc API inside
you service classes. Does
hi michael,
@Inject only works in Tapestry pages and components (and mixins).
By default Tapestry will use the field type as an id and lookup the
corresponding ioc service.
I assume your Web Service Container was not started by the ioc
container so it runs outside its control. Therefore you
So I have to call the current Registry (or to manage it myself) and call the
myRegistry.getService(MyService.class);
Hum, I think it's not ioc anymore if I have to setup my containers (Axis2,
Hibernate) to call the tapestry-ioc or I have to create a sort of middle
layer between the layer and the
Ok I'm going to investigate about that Registry.
So, what's the interrest to use tapestry-ioc instead of Spring ioc? If I
need my ioc to provide all the services I need, I cannot use tapestry-ioc
unless I need my other layers to call explicitely the ioc which is not
recommended when you want
this helps maybe it helps looking closer at springs integration
with web services.
g,
kris
Michael Bernagou [EMAIL PROTECTED]
14.12.2007 11:35
Bitte antworten an
Tapestry users users@tapestry.apache.org
An
Tapestry users users@tapestry.apache.org
Kopie
Thema
Re: IoC global question
So
On Fri, 14 Dec 2007 08:45:56 -0200, Kristian Marinkovic
[EMAIL PROTECTED] wrote:
i think choosing spring or tapestry-ioc is just a matter of taste. I do
use tapestry-ioc a lot because i develop tapestry 5 applications
and sometimes i do not need spring.
I beg to differ. Howard haven't used
14 matches
Mail list logo
