avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hawkes" <jhaw...@adsnm.com>
Subject Re: [RT] Auto-configuring components
Date Fri, 23 Jan 2004 17:15:39 GMT
So, for example:

public class MyComponent {

    /**
     * @@ConfigurableField ("@my-field")
     */
    private String myField;

    /**
     * @@ConfigurableField ("@my-other-field")
     */
    private int myOtherField;

    private MyComponent() {
    }

    public MyComponent(String myField, int myOtherField) {
        this.myField = myField;
        this.myOtherField = myOtherField;
    }
}

And the container would use the private, no-args constructor?  Interesting
idea...


----- Original Message ----- 
From: "Hamilton Verissimo de Oliveira (Engenharia - SPO)"
<hamilton.oliveira@agenciaclick.com.br>
To: "Avalon Developers List" <dev@avalon.apache.org>
Sent: Friday, January 23, 2004 11:04 AM
Subject: Re: [RT] Auto-configuring components


> -----Mensagem original-----
> De: Jonathan Hawkes [mailto:jhawkes@adsnm.com]
>
> > But you're exactly right.  I think it's a neat feature, but it makes it
> > impossible to use your components without a fancy container impl.
>
> Exactly the opposite. Supporting a different IoC level would enable one to
> use or not a container.
>
> When you a really small project, IMO its a burden to put a container there
> just to use one service.
>
>
>
> --
> hammett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Mime
View raw message