[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdi-dev] Annotation/class scanning metadata standard
|
Both ideas have been floated. I guess an API provides for the most flexibility. I'll revisit the extension API again.
Do you mean a persistent store of metadata, something like Jandex? That is, a standardized API
plus storage format? Or just an API that could possibly be implemented on top of persistent store (e.g. Jandex), reflection, javax.lang.model and possibly more?
If you're talking about the second, then the language model in the proposed Build Compatible Extension API would be a decent fit I think.
LT
I know we touched on the idea of having some API for accessing the class information along with the annotations, etc. Did we decide to look into providing an API for this?
The notion of having an annotation scanning metadata store is coming up again on the jakarta-platform-dev list.
cdi-dev mailing list
cdi-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdi-dev
cdi-dev mailing list
cdi-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdi-dev
