backtozero/camelinaction

Automatically exported from code.google.com/p/camelinaction

camelinaction's Issues

verbose flag is not exposed via jmx

What steps will reproduce the problem?
1. at chapter12/custom, run mvn compile exec:java -Pcustom
2. connect via jmx remotely (e.g. 
service:jmx:rmi:///jndi/rmi://myPC:1099/jmxrmi/camel)
3.

What is the expected output? What do you see instead?

at the endpoints section no Operation are exposed under the erp component. But 
it should.

What version of the product are you using? On what operating system?

camel 2.10.2
Windows 7
java 1.6.0_25


Please provide any additional information below.

I changed imports from:

import org.springframework.jmx.export.annotation.ManagedAttribute;
import org.springframework.jmx.export.annotation.ManagedResource;

to:

import org.apache.camel.api.management.ManagedAttribute;
import org.apache.camel.api.management.ManagedResource;

and works fine.

Original issue reported on code.google.com by [email protected] on 27 Dec 2012 at 12:55

Update chapter9-xa

Hi all,

I think chapter9-xa example should be updated.

Starting from 3.7.0, Atomikos jar file are available on central maven repo. The 
latest releas is 3.7.1.

To make the test works I had to customize the jdbc resource in 
AtomikosXACommitTest.createRouteBuilder()

You can find my patch as attached file.


Thx.

Original issue reported on code.google.com by pascal.leclercq on 11 May 2012 at 9:11

Attachments:

• chapter9-xa.patch

Spring Example

What steps will reproduce the problem?
1. Download 2120 version of source and extract the files
2. Navigate to the chapter 2\spring folder
3. run mvn compile:exec:java -Dexec.mainClasss=camelinaction.GreetMeBean

What is the expected output? What do you see instead?

The expected output should be a successful install followed by Hello 
<Username>. That's what is specified in the book and that is what happens in 
previous versions

In this case it would download a lot of the necessary things before we see 
something along the lines of
[ERROR] BUILD ERROR
[INFO] Failed to resolve artifact.

Missing:
----------
1) org.apache.qpid:proton-jms:jar0.3.0-fuse-2
...


What version of the product are you using? On what operating system?

Windows 7 Professional, just using cmd.exe
Please provide any additional information below.

It worked perfectly in the 2103 version, so I suspect either something is 
different between the chapter 2/spring versions

Original issue reported on code.google.com by [email protected] on 27 Sep 2013 at 7:37

Logging for Dead Letter Queue is not as described in the Book

When executing the JUnit test 
/chapter5-errorhandler/src/test/java/camelinaction/RouteScopeTest.java for the 
error handling using a dead letter channel (chapter 5, p. 136 in the book), I 
do not get the error message stating that the delivery attempts have been 
exhausted.

More explicitly: I do not see the following message mentioned in the book: 

Exhausted after delivery attempt: 6 caught:
camelinaction.OrderException: ActiveMQ in Action is out of stock.
Processed by failure processor: sendTo(Endpoint[log://DLC])

The project is referencing camel-core-2.7.0.jar

Since I think that this logging is pretty useful, I am wondering how to enable 
it.

Thanks for any help!

Kind regards,

Ingmar

Original issue reported on code.google.com by [email protected] on 15 Jun 2011 at 4:49

Add instructions to source code how to use hawtio ui

So you can run some of the examples / unit tests with hawtio embedded and see 
from the UI what happended

Original issue reported on code.google.com by [email protected] on 20 Jan 2014 at 4:01

Move code to github

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

Original issue reported on code.google.com by [email protected] on 23 Jan 2014 at 9:01

Incorrect pom.xml for chapter5/usecase module

What steps will reproduce the problem?
1. run "mvn compile exec:java -PServer" as said in README.txt
2.
3.

What is the expected output? What do you see instead?
Output:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail
s.

What version of the product are you using? On what operating system?
pom.xml revision 320

Is solved by removing test scope parameter from log4j, org.slf4j, junit 
dependency declarations.

Corrected pom.xml in attachment.

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 13 Jun 2011 at 1:38

Attachments:

• pom.xml

Chapter13/war seems to be broken

What steps will reproduce the problem?
1. From chapter13/war run 'mvn package'
2. Put the resulting war into a tomcat container (I used Tomcat 7.0.27)
3. Look at the log and see that the War was not deployed

I'm working on understanding the War that is generated by mvn package and am 
having trouble as it appears to be broken currently.

Original issue reported on code.google.com by [email protected] on 21 May 2012 at 4:22

ActiveMQ embedded without persistent datastore

As AMQ 5.9 onwards WARNs about when < 50gb free disk space.

We should embed AMQ as non persistent queues when possible.

Original issue reported on code.google.com by [email protected] on 20 Jan 2014 at 3:57