Re: some thoughts that I wanted to post, in regards to RP, CRI, Exceptions, and a class scanner

Hi Ryan On Tue, May 24, 2011 at 6:28 AM, Ryan Zoerner ryanzoer...@gmail.com wrote: I have some thoughts that I wanted to post to the dev list. Here they are: The RP will need to choose between lifecylces, possibly just selecting which existing cxf resourceProvider to choose, based upon

Re: some thoughts that I wanted to post, in regards to RP, CRI, Exceptions, and a class scanner

This is what I had in mind for an RP constructor: Incidentally, EJB annotations show up in the cri. under ClassResourceInfo.elementData[i].resourceClass.declaredAnnotations.table[j]. h.type.name and

Re: some thoughts that I wanted to post, in regards to RP, CRI, Exceptions, and a class scanner

Also, I suppose that you could just use AnnotationUtils on o in the formal params and then find out isEJB() and ejbLifecycle from that. Ryan

Re: some thoughts that I wanted to post, in regards to RP, CRI, Exceptions, and a class scanner

you will note that nabble mangled the ); in my email, which is what caused me to think of this. Ryan

some thoughts that I wanted to post, in regards to RP, CRI, Exceptions, and a class scanner

I have some thoughts that I wanted to post to the dev list. Here they are: The RP will need to choose between lifecylces, possibly just selecting which existing cxf resourceProvider to choose, based upon annotation. The annotations may be found in the class resource info object, obtainable from