>
> I'm a bit confused :-). Here is what I meant:
>
>
> xmlns:s="http://users.com/rs";
> serviceName="s:UserService">
>
>
>
>
>
>
> implementor="#userService"
> xmlns:s="http://users.com/ws";
> serviceName="s:UserService"
>
HI Shenglin
>> - What you may want to do is to update InstrumentationManagerImpl to
>> be able to access the underlying MBeanServerConnection and have
>> InstrumentationManagerImpl inject into your JAX-RS resource, thus
>> letting the manager deal with JMS-specific configuration and
>> connection
="org.apache.cxf.management.jmx.InstrumentationManagerImpl">
>
>
>
>
> value="service:jmx:rmi:///jndi/rmi://localhost:9914/jmxrmi" />
>
> Pros: basic spring context, ease the configuration/implementation compare
ay that I am enrolled.
Thank you very much.
Regards:
Shenglin Qiu
> Does it make sense ? What do you think ?
>
Due to the large size of cxf, I will follow the steps from you. My thoughts
could be deviated, so please correct me at any time.
Your mentoring has delighted me since the b
Hi Sergey:
Happy Holiday!
I can't believe it's not a US holiday and at least people in MA have to work:(
I will ping you tomorrow.
Thank you very much!
Regards:
Shenglin Qiu
> Date: Mon, 25 Apr 2011 16:21:14 +0100
> Subject: Re: Revised Proposal: GSoC - (CXF-3388) Expos
Hi Shenglin
You are progressing very well, please see comments inline
On Mon, Apr 25, 2011 at 12:25 AM, Travis Roy wrote:
>
> Hi Sergey:
> I have made some progress according to your last email, due to the size of
> each file, I have to paste some of them below. As you can see, in my spring
> ap
Hi Sergey:
I have made some progress according to your last email, due to the size of each
file, I have to paste some of them below. As you can see, in my spring
application context, I deployed 2 testing Jax Rs services, UserServiceImpl and
CustomerServiceImpl, and then I attached my JmxServic
Hi
Introducing a collection wrapper is a not a bad idea - WADL will generate an
element for it, but it is not strictly needed. I was just suggesting to
introduce *our own* ObjectName wrapper, a bean which will only have a String
property initialized from JMX ObjectName.
Introducing a custom JAX-R
Yes, Sergey.
I am trying to do this, but so far, can't get rid of the replying on must have
@XmlRootElement annotation for ObjectName. Probably, I need to create some
testing purpose mbeans, register to InstrumentationManagerImpl, and see how
they work.
@XmlRootElement
public class ObjectNam
Hi
It is a good progress, I think you are on the right path.
Just to see that things are really working, introduce ObjectName and
ManagedComponent JAXB beans which will be initialized from JMX ObjectName
and ManagedComponent JMX objects.
That should be enough for GETs to start working. We will th
ree to setup anytime for further mentoring. (607-727-3067)I
> have checked out the source code, compiled and imported in eclispe, local
> setup is done.
>
>
> Thank you.
>
>
>
>
> Shenglin Qiu Date: Thu, 7 Apr 2011 10:10:16 +0100
> Subject: Re: Revised Proposal
, local setup is
done.
Thank you.
Shenglin Qiu Date: Thu, 7 Apr 2011 10:10:16 +0100
Subject: Re: Revised Proposal: GSoC - (CXF-3388) Expose CXF JMX MBeans as the
JAX-RS resources
From: sberyoz...@gmail.com
To: dabaip...@hotmail.com
Hi - that looks good, register it today please and then reply
12 matches
Mail list logo
