Re: Move trunk to 2.5 after 2.4.1?

sounds very good. regards, aki 2011/6/7 Dennis Sosnoski : > I've (mostly) completed a restructuring of the WS-RM code and tests to allow > interoperability with other stacks using WS-Addressing 1.5 with WS-RM 1.0, > and to add support for WS-RM 1.1/1.2. To avoid any compatibility issues I've > kep

Re: Expose MBeans in CXF

Hi Shenglin I'm not sure if I'm confusing you with the comments I'm making...The source has become cleaner, good progress there, but I'm not sure what are you doing there at all now. Why MBeanCollection has become a subresource ? What happened to our /mbean/{id} handler ? Recall, you had a subres

Re: Build failed in Jenkins: CXF-Trunk-JDK15 #2140

Hi, > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] >

Re: Build failed in Jenkins: CXF-Trunk-JDK15 #2140

hi, sorry. i'll be fixing it. regards, aki 2011/6/8 Sergey Beryozkin : > Hi, > >> [INFO] - >> [ERROR] COMPILATION ERROR : >> [INFO] - >> [ERROR] >>

Re: Build failed in Jenkins: CXF-Trunk-JDK15 #2140

Hi Aki On Wed, Jun 8, 2011 at 11:33 AM, Aki Yoshida wrote: > hi, > sorry. > i'll be fixing it. np at all; by the way - I'm not sure I'm right there about dropping explicit SOAPMessages refs, I was just hoping to get the coloc binding reused somehow for JAX-RS tests, etc in time. Hopefully you ca

Re: Build failed in Jenkins: CXF-Trunk-JDK15 #2140

Hi Sergey, I just dropped SOAPMessage. Most people would be using Source and the patch that I submitted was only supporting the Source usage. It makes sense to drop SOAPMessage. I had a reference to SOAPMessage in ColocUtil as I though I could eventually support the SOAPMessage as well. However,

Re: Build failed in Jenkins: CXF-Trunk-JDK15 #2140

Hi Aki On Wed, Jun 8, 2011 at 12:03 PM, Aki Yoshida wrote: > Hi Sergey, > I just dropped SOAPMessage. > > Most people would be using Source and the patch that I submitted was > only supporting the Source usage. It makes sense to drop SOAPMessage. > > I had a reference to SOAPMessage in ColocUtil

Re: Custom Reuqest Param Name for Bean Request Object

Did you get chance to look into the new code? Does it satisfy your requirement? Biju B On Sun, Jun 5, 2011 at 12:28 PM, Biju Nair wrote: > Updated JIRA with path and modified files for the new implementation... > > > On Fri, Jun 3, 2011 at 1:52 AM, Sergey Beryozkin wrote: > >> Your patch contai

Re: Custom Reuqest Param Name for Bean Request Object

Your patch has been applied with few minor modificatios. Many thanks for your help, apologies for a delay in dealing with it Have a look please at the client side, the proxies can 'unwrap' parameter beans, so InjectionUtils.fillInValuesFromBean maya need to be updated a bit for Map properties hand

RE: Expose MBeans in CXF

Hi Sergey: Sorry for replying a little bit late. But I reverted the code as you mentioned /mbean/{id} must not be changed. Code has be synced to github: https://github.com/dabaipang/services /** * Specification: * Function 1: *Jmx Server: *sub-resource locator *http://local

Re: Custom Reuqest Param Name for Bean Request Object

I will look into the fillInValues... and will accomodate the Map. On Wed, Jun 8, 2011 at 1:24 PM, Sergey Beryozkin wrote: > Your patch has been applied with few minor modificatios. > Many thanks for your help, apologies for a delay in dealing with it > > Have a look please at the client side, th