I just checked the code of camel-cxf, it doesn't support to take the
schemaLocation, so I create a JIRA[1] for it and will work on quick fix
for it shortly.
[1]https://issues.apache.org/activemq/browse/CAMEL-3319
On 11/7/10 12:53 AM, Marco Zapletal wrote:
http://camel.apache.org/schema/cxf i
I'm not sure what you mean by creating a sample project. I'm not really a
developer. I'm a product manager.
I think that the specification of replyTo on an endpoint should always
ensure that there is a replyTo specified in messages sent by the
JMSProducer, because if the route creator specifies
Ahh..
I moved to a RouteBuilder because of this ;)
Thanks!
--
View this message in context:
http://camel.465427.n5.nabble.com/Delayer-and-asyncDelayed-how-to-delay-asynchronously-tp3252456p3253391.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi
Ah in Spring XML you gotta inline the nodes to be delayed.
Notice how to to is inside the delay tag.
There is a ticket in JIRA to improve this in Camel 3.0, as we got 3
DSL which acts like this, but its not intuitive
- delay
- throttle
- threads
Which requires the "stuff" to be inside its tag
http://camel.apache.org/schema/cxf is the namespace, which has
http://camel.apache.org/schema/cxf/camel-cxf.xsd defined as its
schemaLocation.
I've checked the schema, the element is defined there.
regards,
marco
Am 06.11.2010 17:52, schrieb Christian Müller:
Which namespace do you use for
Which namespace do you use for the "cxf" prefix?
Christian
Am 06.11.2010 17:40 schrieb "Marco Zapletal" :
Hello,
I am defining my CXF services in camel config (using 2.5.0) as follows:
classpath:wsdl/Message.xsd
When starting my Camel application an exception as show
Hello,
I am defining my CXF services in camel config (using 2.5.0) as follows:
classpath:wsdl/Message.xsd
When starting my Camel application an exception as shown below is
thrown. It seems that the CXF bean parser does not know what to do with
the cxf:sc
Nah, it works quite well.
Here's my bean:
import org.apache.camel.Header
class DelayerBean {
private static final long DELAY = 1000
public DelayerBean() {}
public long sendAtTime(@Header("JMSTimestamp") long messageTimestamp,
@Header("JMSMessageId") String msgId, @Header("msgNo")
Hi
I think the delayer in Camel 2.x is a bit different than 1.x which
kinda magically could use the timestuff from the JMS message. (eg it
was tied a bit into the JMS world).
So you may have to "compute" the delay a bit differently in 2.x than 1.x.
On Sat, Nov 6, 2010 at 11:45 AM, Krystian wro
Hi
I haven't had time to look into this.
There may be an issue on the producer side to send a message as InOnly
to a JMS destination and preserving the JMSReplyTo header.
Fell free to create a little sample project with a couple of routes
which highlights your intention.
Then we can use that for
Hi,
Thanks for the answer, however I got there without using concurrent
consumers.
2 years ago I was doing something ... well ... similar in a way.
Anyway... I am using a method call during delay [1] and in my bean I check
the difference between current time and timestamp on the message and delay
You need to use the concurrent consumers option on the JMS endpoint to
process message concurrently which is what you want
http://camel.apache.org/jms
On Sat, Nov 6, 2010 at 12:59 AM, Krystian wrote:
>
> I've tried doing something I did with 1.x version of camel, calling a method
> to figure ou
12 matches
Mail list logo
