Thank you.
Ryan Zoerner
On Mon, Jul 4, 2011 at 4:40 AM, Florent BENOIT wrote:
> Hi,
>
> If you need details about EasyBeans/CXF integration, you may also ask on
> easybe...@ow2.org mailing list
> I can also answer on this ML ;-)
>
> Regards,
>
> Florent
>
>
> On 07/01/2011 04:40 PM, Sergey Be
Hi,
If you need details about EasyBeans/CXF integration, you may also ask on
easybe...@ow2.org mailing list
I can also answer on this ML ;-)
Regards,
Florent
On 07/01/2011 04:40 PM, Sergey Beryozkin wrote:
Hi Ryan
On Fri, Jul 1, 2011 at 2:36 PM, Ryan Zoerner wrote:
Hi Sergey,
Yes
Hi Ryan
On Fri, Jul 1, 2011 at 2:36 PM, Ryan Zoerner wrote:
> Hi Sergey,
>
> Yes, I've been looking at that package and exploring the same issues. I see
> that there is
> an EasyBeansCXFBootstrap. I am unsure whether the bootstrap is what is
> directly
> instantiated by a server such as Jetty or
Correction, I found it searching for which class instantiates
CXFEJBWebserviceEndpoint,
which class instantiates that, etc.
Ryan
Hi Sergey,
Yes, I've been looking at that package and exploring the same issues. I see
that there is
an EasyBeansCXFBootstrap. I am unsure whether the bootstrap is what is
directly
instantiated by a server such as Jetty or Tomcat. I found it, tracing
constructor calls
out from the CXFEJBWebservice
Hi Ryan
On Wed, Jun 29, 2011 at 9:19 PM, Ryan Zoerner wrote:
> Hi Sergey,
>
>>>The fact you have seen EJB-related annotations being associated with a
>>>given CRI instance in debugger simply confirms the fact JVM retains
>>>them. But the sole responsibility of CRI is to model a JAX-RS root
>>>res
Also, for academic interest's sake, here is, to me, a novel idea for
restructuring a class, which implements one subclass for each refactored
method, each of which contains all submethods:
http://pages.cs.wisc.edu/~zoerner/downloads/dev/samples/EJB/idea_to_simplify_a_class_for_readability/
Hi Sergey,
>>The fact you have seen EJB-related annotations being associated with a
>>given CRI instance in debugger simply confirms the fact JVM retains
>>them. But the sole responsibility of CRI is to model a JAX-RS root
>>resource or subresource. It can not deal with with how a given
>>resource
Hi Ryan
On Wed, Jun 29, 2011 at 6:25 AM, Ryan Zoerner wrote:
> Sergey,
>
> I might be able to prove you wrong about which annotations are scanned from
> the class for the cri? I had evidence to the contrary.
>
The fact you have seen EJB-related annotations being associated with a
given CRI instan
Sergey,
I might be able to prove you wrong about which annotations are scanned from
the class for the cri? I had evidence to the contrary.
Also, it might be just fine to return the factory, as in this
resourceProvider here:
http://pages.cs.wisc.edu/~zoerner/downloads/dev/samples/EJB/EJBResourceP
Hi Ryan
On Tue, Jun 28, 2011 at 3:23 AM, Ryan Zoerner wrote:
> When I was debugging the jax-rs example, I placed an @EJB annotation in my
> Customer class and it showed up in the annotations in cri. Hence, any
> lifecycle-defining annotations would show up also?
>
Yes, we discussed it earlier
When I was debugging the jax-rs example, I placed an @EJB annotation in my
Customer class and it showed up in the annotations in cri. Hence, any
lifecycle-defining annotations would show up also?
Hi Ryan
On Mon, Jun 27, 2011 at 5:58 PM, Ryan Zoerner wrote:
> Sergey,
>
> I have seen the Bean Invoker in cxf. I have just come across the class
> EJBHomeCallFactory in EasyBeans.
>
> I am wondering if it might suit our needs to use this, BeanInvoker, and make
> BeanInvoker extend JAXRSInvoker.
Sergey,
I have seen the Bean Invoker in cxf. I have just come across the class
EJBHomeCallFactory in EasyBeans.
I am wondering if it might suit our needs to use this, BeanInvoker, and make
BeanInvoker extend JAXRSInvoker.
What do you think?
If not, I am currently putting together a resourceProv
14 matches
Mail list logo
