This content has been marked as final.
Show 7 replies
-
1. Re: A taster - jboss reflect docs
alesj Jan 20, 2009 4:34 AM (in response to ropalka)Nice. :-)
What's "ClassLoading SPI" doing there at the end?
ps: I'll read in more details asap ;-) -
2. Re: A taster - jboss reflect docs
ropalka Jan 20, 2009 4:38 AM (in response to ropalka)Feel free to modify the document where necessary. It's just first draft ;)
-
3. Re: A taster - jboss reflect docs
ropalka Jan 20, 2009 4:41 AM (in response to ropalka)"alesj" wrote:
What's "ClassLoading SPI" doing there at the end?
It's in the jboss-reflect/trunk SVN repo. The TODO at the end of document needs to be evaluated. -
4. Re: A taster - jboss reflect docs
alesj Jan 20, 2009 5:01 AM (in response to ropalka)Some better (more than just saying 'Nice') feedback:
* Initial diagram should show TypeInfo/ClassInfo as well
* TypeInfo's / ClassInfo's weak cache could be mentioned (TypeInfoFactory as a singleton)
* Joinpoint spi/api is deprecated? Adrian?
* Is Classadapter still good usage? It should be either enhanced or removed?
* Explain BeanAccessMode -
5. Re: A taster - jboss reflect docs
alesj Jan 20, 2009 5:06 AM (in response to ropalka)"richard.opalka@jboss.com" wrote:
"alesj" wrote:
What's "ClassLoading SPI" doing there at the end?
It's in the jboss-reflect/trunk SVN repo. The TODO at the end of document needs to be evaluated.
I think we can just remove this?
As I see CL project uses Translator from Commons. -
6. Re: A taster - jboss reflect docs
ropalka Jan 20, 2009 5:14 AM (in response to ropalka)"alesj" wrote:
Some better (more than just saying 'Nice') feedback:
* Initial diagram should show TypeInfo/ClassInfo as well
* TypeInfo's / ClassInfo's weak cache could be mentioned (TypeInfoFactory as a singleton)
* Joinpoint spi/api is deprecated? Adrian?
* Is Classadapter still good usage? It should be either enhanced or removed?
* Explain BeanAccessMode
OK, I'll do it soon (in my next spare time). -
7. Re: A taster - jboss reflect docs
ropalka Jan 20, 2009 5:15 AM (in response to ropalka)"alesj" wrote:
I think we can just remove this?
As I see CL project uses Translator from Commons.
If you're 100% sure it's not referenced from else where remove it ASAP to don't confuse other users of the API ;)