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)"
<[EMAIL PROTECTED]>
To: "Avalon Developers List" <[EMAIL PROTECTED]>
Sent: Friday, January 23, 2004 11:04 AM
Subject: Re: [RT] Auto-configuring components
> -----Mensagem original-----
> De: Jonathan Hawkes [mailto:[EMAIL PROTECTED]
>
> > 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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
