2.4.1-SNAPSHOT is the trunk version - so please check it out if you
decide to work on a pacth, I'll then backmerge it to
2.3.5-SNAPSHOT
Cheers, Sergey
On Thu, May 12, 2011 at 9:51 PM, Biju Nair wrote:
> Which version of CXF you are working on?
>
> I was working with 2.3.1.
>
> On Thu, May 12, 20
Hi Ryan
On Fri, May 13, 2011 at 2:25 AM, Ryan Zoerner wrote:
> Sergey,
>
> I have the following question regarding the project.
>
> -
> -
> Customer:
> -
Hi Sergey,
You mentioned that Customer should display a single customer. Does
CustomerService instantiate that Customer? By what mechanism? I created this
class to try and get around that problem. In the old demo, Customers were
instantiated in CustomerService, however, if you have CustomerService
Hi
On Fri, May 13, 2011 at 1:19 AM, Shenglin Qiu wrote:
>
> 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
Hi
On Fri, May 13, 2011 at 10:54 AM, Ryan Zoerner wrote:
> Hi Sergey,
>
> You mentioned that Customer should display a single customer. Does
> CustomerService instantiate that Customer?
I'm presuming we are talking about the 2nd endpoint ?
No, as I said in the previous email, it is the custom re
The full Customer.java class may be viewed here:
http://pages.cs.wisc.edu/~zoerner/downloads/dev/samples/customerservice/Customer.java
Thank you for your answer. I'm sorry, I didn't see it before I posted the
link.
Ryan
Very good, there's one simplification is that those methods with @GET
should just return 'this'.
Just make sure Customer id and name are set to some default values.
Your implementation is also correct though; if we rename Customer to
say Person then your code can handle the family hierarchy case,
Here are the links to the CustomerService.java and Client.java files that I
have in my development environment.
Also, here are the output files from the client and the server.
You can see from the header that the 400 status code happens fine.
I think that the xml error might be as a result of cx
Hi
On Fri, May 13, 2011 at 1:37 PM, Ryan Zoerner wrote:
> Here are the links to the CustomerService.java and Client.java files that I
> have in my development environment.
>
> Also, here are the output files from the client and the server.
>
> You can see from the header that the 400 status code
Hi,
While analyzing a problem in WS-RM, which I describe later, I
discovered this problem. I will mention it on this dev@cxf list
because potentially other components may be affected as well depending
on how they are using the instances of this class.
This EndpointImpl class extends AbstractAttrib
Hi,
Here is a link to Server.java, CustomerResourceProvider.java,
CustomInvoker.java, and, CustomExceptionMapper.java:
http://pages.cs.wisc.edu/~zoerner/downloads/dev/samples/jaxrs_basic_http_demo/Server.java
http://pages.cs.wisc.edu/~zoerner/downloads/dev/samples/jaxrs_basic_http_demo/CustomRes
Hi
> In addition, I found out that the browser is also receiving the 400 status
> code.
> At minimum, due to expecting text/xml, when it gets a blank screen, it says
> that it cannot parse it.
I don't think it is actually getting an empty 400, the fact CXF
transport sets Content-Header should not
Hi Sergey:
Here are what I had and although the output maybe simple, I checked outputs and
they look alright, need your opinions:)
1.
Request URL: this is from searching part of endpoint
service="{http://impl.service.ws.gsoc.cxf.apache.org/}CustomerServiceImpl";
http://localhost:8080/demoserve
i don't see the SVN branch.
I am trying to change in http://svn.apache.org/repos/asf/cxf/trunk - is that
ok? If not can you sen me the SVN link?
On Fri, May 13, 2011 at 1:48 AM, Sergey Beryozkin wrote:
> 2.4.1-SNAPSHOT is the trunk version - so please check it out if you
> decide to work on a pa
15 matches
Mail list logo
