Hi,
The JMS Transport was refactored from Spring to pure java in CXF 3.0.0.
You can configure the number of concurrent JMS consumers now using
concurrentConsumers option in JMS URI:
jms:queue:ExampleQueueName?concurrentConsumers=15
AFAIK PollingMessageListenerContainer creates the fixed thread p
CXF hasn’t “supported” Maven 2.x for a while. It may have worked, but that
would have been completely by accident, not something that was intentional or
tested. Building CXF has required 3.0.x for a very long time due to some
resolution issues with Maven 2.x. Since it wasn’t possible (easi
> On Nov 24, 2015, at 10:14 AM, Sergey Maslov wrote:
> I have a question about how Conduit is properly used and configured?
> I've prepared JMeter performance test with simultaneous requests and
> enabled the JVM debug.
> 1. I've noticed that there are only two Conduit objects for processing 20
>
Hi,
> -Original Message-
> From: Sergey Maslov [mailto:therealma...@gmail.com]
> Sent: Montag, 23. November 2015 05:54
> To: users@cxf.apache.org
> Subject: Re: Could message be broken before SAAJInInterceptor?
>
> Yes, we've checked it. It was received on the client side correctly.
Coul
Hi,
> -Original Message-
> From: tho huynh ngoc [mailto:ngocthob...@gmail.com]
> Sent: Montag, 23. November 2015 13:22
> To: users@cxf.apache.org
> Subject: Re: send Message object through Jax-ws
>
> Hi,
>
> I set @XmlRootElement annotation in MyDestination but i give the same error
> at
I'll look in detail at one of the existing tests where an external
binding is applied (I recall copying some JAXWS tooling code which
modifies the binding files), and will let you know, a bit later though
Thanks, Sergey
On 24/11/15 05:59, Vjacheslav V. Borisov wrote:
2015-11-23 16:32 GMT+04:00
Hi.
I have a question about how Conduit is properly used and configured?
I've prepared JMeter performance test with simultaneous requests and
enabled the JVM debug.
1. I've noticed that there are only two Conduit objects for processing 20
requests.
Is it good?
2. Could I configure the "One conduit
Hi,
Just a short question: we are currently using CXF & cxf-codegen-plugin version
3.0.6 to execute the wsdl2java goal with maven 2.2.1.
Now we wanted to upgrade to CXF 3.1.4 and experience problems when building our
project:
[ERROR] BUILD ERROR
[INFO] ---
When a Destination receives a message at processStreamIo method
ex:
protected void processStreamIo(IoSession session, InputStream in,
OutputStream out) {
final MessageImpl m = new MessageImpl();
final Exchange exchange = new ExchangeImpl();
exch
When a Destination receives a message at processStreamIo method
ex:
protected void processStreamIo(IoSession session, InputStream in,
OutputStream out) {
final MessageImpl m = new MessageImpl();
final Exchange exchange = new ExchangeImpl();
exch
If you want to receive a message and route it to somewhere else based
on the content, one typical approach is to Apache Camel
(http://camel.apache.org) which supports all kinds of endpoints
including CXF and also various processing steps. In this case, your
application is a simple Camel route with
Hi
I suspect it can be tricky to do, the tool parser manages to group
multiple -xjc args together and we can manage it later on, while passing
something like "-tMap aaa" to the parser will probably fail the parser
validation check (similar to the way passing an episode arg with the
file prope
Hi,
I'm trying to upgrade from CXF 2.7.x to 3.1.x. for my spring application
running on WebSphere 8.5 that uses SOAP over JMS for long running operations.
On 2.7.x I'm using the spring/websphere taskExecutor to correctly integrate
with WebSphere to avoid creating unmanaged threads. I also use t
13 matches
Mail list logo
