[GitHub] cxf pull request: Fix a typo in FIXED_PARAMETER_ORDER

2016-03-19 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/cxf/pull/122


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Re: [VOTE] - Release Apache CXF Build Utils 3.2.0

2016-03-19 Thread Colm O hEigeartaigh
We have at least 7 binding +1 votes, and two non-binding +1 votes, and no
other votes. This vote has passed + I'll do the release.

Colm.

On Tue, Mar 15, 2016 at 9:50 PM, Andrei Shakirin 
wrote:

> +1,
>
> Regards,
> Andrei.
>
> > -Original Message-
> > From: Colm O hEigeartaigh [mailto:cohei...@apache.org]
> > Sent: Dienstag, 15. März 2016 11:56
> > To: dev@cxf.apache.org
> > Subject: [VOTE] - Release Apache CXF Build Utils 3.2.0
> >
> > This is a vote to release Apache CXF Build Utils 3.2.0. It just contains
> some
> > plugin updates. The reason behind the release is to avoid introducing an
> old
> > Apache Ant dependency to downstream projects, which has a security
> > advisory against it. The plugin updates requires a move to JDK 7, hence
> > 3.2.0 rather than 3.1.1.
> >
> > Git tag:
> >
> > https://git-wip-us.apache.org/repos/asf?p=cxf-build-
> > utils.git;a=commit;h=d2cd514af6e8ff296786ca7ca33cd5aff5fcd830
> >
> > Maven artifacts:
> >
> > https://repository.apache.org/content/repositories/orgapachecxf-1064/
> >
> > +1 from me.
> >
> > Colm.
> >
> >
> > --
> > Colm O hEigeartaigh
> >
> > Talend Community Coder
> > http://coders.talend.com
>



-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com


[GitHub] cxf pull request: [CXF-5193] Fix anonymous fixed IDL type handling

2016-03-19 Thread grgrzybek
GitHub user grgrzybek opened a pull request:

https://github.com/apache/cxf/pull/123

[CXF-5193] Fix anonymous fixed IDL type handling



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/grgrzybek/cxf CXF-5193

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cxf/pull/123.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #123


commit e0bff66bc8b10a8fc30cdb02a44c6bea90d5915b
Author: Grzegorz Grzybek 
Date:   2016-03-17T12:41:25Z

[CXF-5193] Fix anonymous fixed IDL type handling




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Camel CXF-RS resource method called twice when using performInvocation

2016-03-19 Thread Phillip Rhodes
Camel gang:

I'm using the Camel CXFRS support to publish a REST service using Camel.
What I want is for the incoming request to actually invoke my service
class, and the response from that to go into the Camel route for further
processing.  That appears to happen just fine when using the
performInvocation=true option, BUT... when I do that, it appears that the
method on the resource class is called twice for each incoming REST call.

My beans.xml looks like this:

-



http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:camel="http://camel.apache.org/schema/spring";
xmlns:cxf="http://camel.apache.org/schema/cxf";
xmlns:jaxrs="http://cxf.apache.org/jaxrs";
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
http://camel.apache.org/schema/cxf
http://camel.apache.org/schema/cxf/camel-cxf.xsd
http://cxf.apache.org/jaxrs
http://cxf.apache.org/schemas/jaxrs.xsd";>





http://localhost:9090/CxfRsRouterTest/route";
serviceClass="com.fogbeam.exp.camel.cxfrs.jaxrs.beans.CustomerService"
loggingFeatureEnabled="true" loggingSizeLimit="20">















 ---

and the Java code for the class in question looks like this:

---
@Path("/customerservice/")
@Consumes( MediaType.APPLICATION_JSON )
@Produces( MediaType.APPLICATION_JSON )
public class CustomerService
{
private static long invocationCount = 0;
Map customers = new HashMap();
@POST
@Path("/customers/")
public Customer insertCustomer(Customer customer) {

System.out.println( "invocationCount: " + (invocationCount++));
System.out.println("\ninvoking insertCustomer, Customer
name is: " + customer.getName() +
"\n*" );

customers.put(customer.getId(), customer);

return customer;
}

}
---

When I run this, the Camel process logs as follows:

Mar 19, 2016 9:32:30 PM org.apache.cxf.endpoint.ServerImpl initDestination
INFO: Setting the server's publish address to be
http://localhost:9090/CxfRsRouterTest/route
Mar 19, 2016 9:32:55 PM org.apache.cxf.interceptor.LoggingInInterceptor
INFO: Inbound Message

ID: 1
Address:
http://localhost:9090/CxfRsRouterTest/route/customerservice/customers
Encoding: UTF-8
Http-Method: POST
Content-Type: application/json
Headers: {accept-encoding=[gzip,deflate], connection=[keep-alive],
Content-Length=[39], content-type=[application/json],
Host=[localhost:9090], User-Agent=[CxfRSClientMain]}
Payload: { "id":"123", "name"
--
invocationCount: 0

invoking insertCustomer, Customer name is: Phillip Rhodes
*
invocationCount: 1

invoking insertCustomer, Customer name is: Phillip Rhodes
*
Mar 19, 2016 9:32:56 PM org.apache.cxf.interceptor.LoggingOutInterceptor
INFO: Outbound Message
---
ID: 1
Response-Code: 200
Content-Type: application/json
Headers: {Content-Type=[application/json], Date=[Sun, 20 Mar 2016 01:32:55
GMT]}
Messages: (message truncated to 20 bytes)

Payload: {"id":123,"name":"Ph
--


This behavior seems wrong to me.  I wouldn't expect my service method to be
called twice when somebody hits the REST endpoint.  Can anybody confirm if
this is invalid, and if so, comment if there's a way to fix this?  Or is it
a bug in Camel or CXF?Any and all help is much appreciated.

This is using Camel 2.16.2, FWIW.

Also, there's a question up on StackOverflow from somebody having what
appears to be the same issue.

http://stackoverflow.com/questions/35958121/apache-camel-cxfrsendpoint-performinvocation-setting-triggers-invokation-twice


Thanks,

Phil
---
This message optimized for indexing by NSA PRISM