Re: [picocontainer-dev] Introducing JType

Hi Paul,

Cool :)  No probs with shading it into PicoContainer, I can understand
the dependency conundrum.

Yes, there's a few TODOs in there which I'd like to properly consider
and resolve before releasing an initial version.  There's also a bunch
of features I'd like to add in future which I'll start adding issues
for.  I use this project internally at work too so I'd like to get an
early release out the door and then subsequent ones to fill in any
gaps.  I'd prefer to use a <1.0.0 version scheme to indicate that the
API is not yet stable with a 1.0.0 final to cast it in stone.

I've also got interest in the project from the Hibernate Bean
Validator team so I'd have to coordinate releases and features with
them too.  But more the merrier, it'd be good to centralise the effort
require to work with Types in a common library like this.  And to have
PicoContainer on board too :)

Cheers,

Mark

2009/2/27 Paul Hammant <[email protected]>:
> Mark,
>
> Nice work, and 93% coverage :)
>
> Yes we could use this in PicoContainer.  We'd mode likely 'shade' it into
> the jar as we do with Paranamer.  Thus the packaging for it would become
> (with full acknowledgements) :
>
>   org.picocontainer.types.*  (or similar)
>
> You've marked a few things as TODO in respect of serialization.  We may/may
> not need that to be in place happen I think.
>
> PicoContainer is BSD license, and yours is Apache 2.0, so they are
> compatible.
>
> Lastly, you're not released yet.  What do you think about your schedule and
> version numbering ?
>
> Thoughts?
>
> Regards,
>
> - Paul
>
> On Feb 27, 2009, at 1:02 PM, Mark Hobson wrote:
>
>> Hi there,
>>
>> I've recently open-sourced a small Java 5 type library that may be of
>> use to improve PicoContainer's support for generic types.  Here's some
>> of the features that you may be interested in:
>>
>> * It provides a Type equivalent of Class.isAssignableFrom that handles
>> parameterized types.  This could be used to improve injection when a
>> component demands a type such as PaymentMethod<CreditCard> when
>> multiple PaymentMethod implementations are registered in the
>> container.
>>
>> * It provides a generic type literal Generic<T> which can be used to
>> achieve the same type-safe component registrations a la Guice's
>> TypeLiteral<T>.
>>
>> * It provides a type factory Types which can be used to easily create
>> implementations of the various Type subtypes.
>>
>> It is currently hosted here: http://code.google.com/p/jtype/
>>
>> Hope this is of interest and let me know if you need any more info.
>>
>> Cheers,
>>
>> Mark
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>   http://xircles.codehaus.org/manage_email
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>   http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email