Re: Proposal for component parameters handling in XML

Nah, remove the type information from both parameter
and dependency. They are provided by the reflection
API so there's no need to specify them in two places.
In fact, it could even cause problems.

 --- Konstantin Priblouda <kpriblouda-/[email protected]>
skrev: > 
> --- Jon Tirsén <jon_tirsen-/[email protected]> wrote:
> > I'd suggest a different xml-tag-name, like
> > "dependency". So you get:
> > <component class="">
> >   <parameter>...</parameter>
> >   <dependency key="..." />
> > </component>
> 
> 
> For sake of functional completeness, I would say:
> <parameter class="class name">whatever</parameter>
> ->
> implies attempt to instantiate constant parameter 
> with constructor accepting Strng contained in
> element
> ( the way it works now ) 
> 
> <dependency class="class name of key
> object">whatever</dependency>
> implies the same attempt like in parameter,
> but will be wrapped in component parameter.
> 
> 
> Though, current implementation of key implies that
> all
> component keys are strings...
> 
> regards,
> 
> =====
> ----[ Konstantin Pribluda ( ko5tik )
> ]----------------
> Zu Verstärkung meines Teams suche ich ab Sofort
> einen
> Softwareentwickler[In] für die Festanstellung. 
> Arbeitsort: Mainz 
> Skills:  Programieren, Kentnisse in
> OpenSource-Bereich
> ----[ http://www.pribluda.de
> ]------------------------
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Finance: Get your refund fast by filing
> online.
> http://taxes.yahoo.com/filing.html
> _______________________________________________
> nanocontainer-dev mailing list
> nanocontainer-dev-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org
>
http://lists.codehaus.org/mailman/listinfo/nanocontainer-dev 

Höstrusk och grå moln - köp en resa till solen på Yahoo! Resor på adressen http://se.docs.yahoo.com/travel/index.html