marcuspocus / play-camel Goto Github PK
View Code? Open in Web Editor NEWA EIP + Messaging module for the Play! Framework
Home Page: http://www.playframework.com/modules/camel
A EIP + Messaging module for the Play! Framework
Home Page: http://www.playframework.com/modules/camel
play run
Has Camel log output dumped into stdout.
It shouldn't be dumping to stdout and use Play logger.
And if it's dumping to stdout shouldn't it go to Play's system.out?
Is there a way to configure logging to use Play logger?
play run
~ _ _
~ _ __ | | __ _ _ _| |
~ | '_ \| |/ _' | || |_|
~ | __/|_|\____|\__ (_)
~ |_| |__/
~
~ play! 1.2.4, http://www.playframework.org
~ framework ID is developer
~
~ Ctrl+C to stop
~
Listening for transport dt_socket at address: 8000
May 3, 2012 12:26:34 AM net.sf.oval.internal.Log info
INFO: gnu.trove collection classes are available.
Can't load 'akka.conf'.
One of the three ways of locating the 'akka.conf' file needs to be defined:
1. Define the '-Dakka.config=...' system property option.
2. Put the 'akka.conf' file on the classpath.
3. Define 'AKKA_HOME' environment variable pointing to the root of the Akka distribution.
I have no way of finding the 'akka.conf' configuration file.
Using default values everywhere.
[INFO] [5/3/12 12:26 AM] [play-thread-1] [CamelContextManager$] Camel context initialized
[INFO] [5/3/12 12:26 AM] [play-thread-1] [CamelContextManager$] Camel context started
When I start up Play I get this message:
Can't load 'akka.conf'.
One of the three ways of locating the 'akka.conf' file needs to be defined:
1. Define the '-Dakka.config=...' system property option.
2. Put the 'akka.conf' file on the classpath.
3. Define 'AKKA_HOME' environment variable pointing to the root of the Akka distribution.
I have no way of finding the 'akka.conf' configuration file.
Using default values everywhere.
This is also discussed in play-camel thread few months ago https://groups.google.com/d/topic/play-framework/7fI74FUQg6M/discussion
Can we have this file, even with default values so it don't output this warning?
Activemq component can't be configured to connect to a remote broker without having an embedded broker.
if (broker != null) {
Logger.info("Starting ActiveMQComponent...");
Example of desired configuration:
# (missing broker.connector)
broker.url=tcp://somehosname:61616
This may not be strictly an issue, more of a question;
In Play development mode the Camel context is restarting every time Play is recompiling after modification of any source file in the project been made.
Logically since there was no changes to play-camel sources it shouldn't restart. Play itself did not restart. it only recompiles changed fiel not whole project?
Is this something that can be avoided or it's inherent issue coming from Play automatic recompilation?
Here's what happening:
Modify any source file in the project...
[INFO] [5/1/12 3:54 PM] [play-thread-1] [CamelContextManager$] Camel context stopped
[INFO] [5/1/12 3:55 PM] [play-thread-1] [CamelContextManager$] Camel context initialized
[INFO] [5/1/12 3:55 PM] [play-thread-1] [CamelContextManager$] Camel context started
Output of play deps
with camel-0.1.1 dependency configured:
module not found: se.scalablesolutions.akka#akka-camel;1.1.3
==== mavenCentral: tried
http://repo1.maven.org/maven2/se/scalablesolutions/akka/akka-camel/1.1.3/akka-camel-1.1.3.pom
-- artifact se.scalablesolutions.akka#akka-camel;1.1.3!akka-camel.jar:
http://repo1.maven.org/maven2/se/scalablesolutions/akka/akka-camel/1.1.3/akka-camel-1.1.3.jar
module not found: se.scalablesolutions.akka#akka-camel-typed;1.1.3
==== mavenCentral: tried
http://repo1.maven.org/maven2/se/scalablesolutions/akka/akka-camel-typed/1.1.3/akka-camel-typed-1.1.3.pom
-- artifact se.scalablesolutions.akka#akka-camel-typed;1.1.3!akka-camel-typed.jar:
http://repo1.maven.org/maven2/se/scalablesolutions/akka/akka-camel-typed/1.1.3/akka-camel-typed-1.1.3.jar
::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: groovy#groovy-all;1.0-jsr-03: java.text.ParseException: inconsistent module descriptor file found in 'http://repo1.maven.org/maven2/groovy/groovy-all/1.0-jsr-03/groovy-all-1.0-jsr-03.pom': bad module name: expected='groovy-all' found='groovy-all-1.0-jsr'; bad revision: expected='1.0-jsr-03' found='03';
:: se.scalablesolutions.akka#akka-camel;1.1.3: not found
:: se.scalablesolutions.akka#akka-camel-typed;1.1.3: not found
::::::::::::::::::::::::::::::::::::::::::::::
More of a question than an issue. I've tried several different approaches to use Play Model classes in a Processor in Camel.
I've got a bootstrap Job that runs on @OnApplicationStart.
Basically I've got a file-poller that parses a file and creates a Play Model object. I want to persist this by using the usual Model.save() but keep getting errors that the entity manager isn't available.
Is this something that is supposed to work?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.