Questions regarding the implementation of a 2-endpoint Customer and CustomerService CXF JAX-RS web application

2011-05-12 Thread Ryan Zoerner
Sergey, I have the following question regarding the project. - - Customer: - Per-request reso

RE: Expose MBeans in CXF

2011-05-12 Thread Shenglin Qiu
Hi Sergey: Here is the todo list which you have assigned: 1. Have one JAX-WS and JAX-RS endpoints 2. Have your JMXServer as a separate endpoint 3. Injecting a bus reference and registering a listener Your Tips: 1. In the method where bus is injected, get ServerLifeCycleManager.class extensio

Re: Custom Reuqest Param Name for Bean Request Object

2011-05-12 Thread Biju Nair
Which version of CXF you are working on? I was working with 2.3.1. On Thu, May 12, 2011 at 1:08 PM, Sergey Beryozkin wrote: > Hi > > On Thu, May 12, 2011 at 8:21 PM, Biju Nair wrote: > > Just to clarify, > > > > the user bean will be something like, > > class User{ > > Map params; > > } > > >

Re: Custom Reuqest Param Name for Bean Request Object

2011-05-12 Thread Sergey Beryozkin
Hi On Thu, May 12, 2011 at 8:21 PM, Biju Nair wrote: > Just to clarify, > > the user bean will be something like, > class User{ >   Map params; > } > > Request Data will be user.params.k1=v1&*user.*params.k2=v2 Yes if User is a nested bean, otherwise just params.k1=v1¶ms.k2=v2 if we have FormPa

Re: Custom Reuqest Param Name for Bean Request Object

2011-05-12 Thread Biju Nair
Just to clarify, the user bean will be something like, class User{ Map params; } Request Data will be user.params.k1=v1&*user.*params.k2=v2 Finally, the params map will have [{k1=v1},{k2=v2}] Right? I will check this and let you know. Biju B On Thu, May 12, 2011 at 10:52 AM, Sergey Beryoz

Re: Custom Reuqest Param Name for Bean Request Object

2011-05-12 Thread Sergey Beryozkin
Hi On Thu, May 12, 2011 at 5:55 PM, Biju Nair wrote: > Yes I understood that we don't need two solution for same problem :). > > Just want you let know, if you try to put something like > "testaddress.City=Pleasanton&testAddress.stateName=CA" > testAddress.stateName will not be populated. What I

Re: Custom Reuqest Param Name for Bean Request Object

2011-05-12 Thread Biju Nair
Yes I understood that we don't need two solution for same problem :). Just want you let know, if you try to put something like "testaddress.City=Pleasanton&testAddress.stateName=CA" testAddress.stateName will not be populated. What I saw in your code is, for first parameter the TestAddress instanc

Re: Expose MBeans in CXF

2011-05-12 Thread Sergey Beryozkin
Hi Shenglin Thanks for the update. Can you please copy the summary from the previous email, where one possible approach going forward was discussed and describe what you've done so far in context of that summary ? Looks like you are progressing well, however I'm not exactly sure what exactly you a

Expose MBeans in CXF

2011-05-12 Thread Shenglin Qiu
Hi Sergey: I have tested my current code and these are working fine: http://localhost:8080/demoserver/jaxserver/jmxserver/port/%22UserServiceImpl%22 http://localhost:8080/demoserver/jaxserver/jmxserver/type/Bus.Service.Endpoint I will work on this " sign which is %22 in the URL and try to remove

Re: Basic Http Demo and the refactoring that I did, in the course of figuring out how it worked.

2011-05-12 Thread Ryan Zoerner
Cheers for the suggestion. Ryan On Thu, May 12, 2011 at 4:47 AM, Sergey Beryozkin wrote: > Hi Ryan > > On Thu, May 12, 2011 at 10:42 AM, Ryan Zoerner > wrote: > > In the paragraph, with the hyperlink to the jaxrs demo, I said this: > > > > >

Re: Basic Http Demo and the refactoring that I did, in the course of figuring out how it worked.

2011-05-12 Thread Sergey Beryozkin
Hi Ryan On Thu, May 12, 2011 at 10:42 AM, Ryan Zoerner wrote: > In the paragraph, with the hyperlink to the jaxrs demo, I said this: > > --- > > The client opens a printStream that is associated with the conne

Re: Custom Reuqest Param Name for Bean Request Object

2011-05-12 Thread Sergey Beryozkin
Hi On Wed, May 11, 2011 at 5:34 PM, Biju Nair wrote: > Thanks for the reply. > > Just for clarification, > If I have a Employee bean as follows, > class Employee{ >    String name; >    Address homeAddress; >   //getters and setters are there > } > > class Address{ >    String line1; >   String l

Re: Basic Http Demo and the refactoring that I did, in the course of figuring out how it worked.

2011-05-12 Thread Ryan Zoerner
In the paragraph, with the hyperlink to the jaxrs demo, I said this: --- The client opens a printStream that is associated with the connection, and from that connection the client obtains the return informatio

Re: Server output as a result of the CustomInvoker and Client output after parameterization refactoring of Client, CustomerService, and Order

2011-05-12 Thread Sergey Beryozkin
Hi Ryan Brilliant, you are moving fast now. So, as agreed, customize the demo a bit more (add two jaxrs endpoints, use subresource locator for the 2nd endpoint which uses Customer as the root resource), make sure you can use request URIs from Java and browser clients, including the case where cust

Re: Basic Http Demo and the refactoring that I did, in the course of figuring out how it worked.

2011-05-12 Thread Sergey Beryozkin
Hi Ryan This all very good and I hope the CXF dev community will be happy to see your progress and help when needed, please see some comments inline. Please keep updating us with your progress as often as possible, just one suggestion is to minimize the amount of copied code or traces, etc, copy

Re: demo.jaxrs.server.CustomInvoker

2011-05-12 Thread Sergey Beryozkin
Hi Ryan Your analysis is good, I'm not entirely sure why you had to copy the code for retrieving the resource provider, but overall it looks fine, so yes, you are right, the combination of custom resource provider and/or invoker should help us with the EJB integration. Perhaps some of JAXRSInvoker

Server output as a result of the CustomInvoker and Client output after parameterization refactoring of Client, CustomerService, and Order

2011-05-12 Thread Ryan Zoerner
This is follow-up info to the things that I discussed here: http://cxf.547215.n5.nabble.com/Basic-Http-Demo-and-the-refactoring-that-I-did-in-the-course-of-figuring-out-how-it-worked-td4389413.html and here: http://cxf.547215.n5.nabble.com/demo-jaxrs-server-CustomInvoker-td4389484.html --

demo.jaxrs.server.CustomInvoker

2011-05-12 Thread Ryan Zoerner
In the course of the assignment that Sergey provided me with, I augmented the http-demo, which I talked a bit here: http://cxf.547215.n5.nabble.com/Basic-Http-Demo-and-the-refactoring-that-I-did-in-the-course-of-figuring-out-how-it-worked-td4389413.html Now, the purpose of this customInvoker was