+1
All routes (blueprint) work in Karaf 2.2.2.
Regards
JB
On 07/19/2011 04:13 AM, Zbarcea Hadrian wrote:
A new minor release apache-camel-2.8.0 is out with approximately 420 issues
resolved: improvements and bug fixes [1]. This is a release with a record
number of fixes and reflects the incr
+1
My Scala project can now compile and run its unit tests.
--
Tommy Chheng
On Monday, July 18, 2011 at 7:13 PM, Zbarcea Hadrian wrote:
> A new minor release apache-camel-2.8.0 is out with approximately 420 issues
> resolved: improvements and bug fixes [1]. This is a release with a record
>
We had to redo the release due to an issue we discovered with the
previous builds. This vote is for the second attempt. I changed the
subject line to reflect that and avoid confusions.
Hadrian
On Mon, Jul 18, 2011 at 10:13 PM, Zbarcea Hadrian wrote:
> A new minor release apache-camel-2.8.0 is ou
A new minor release apache-camel-2.8.0 is out with approximately 420 issues
resolved: improvements and bug fixes [1]. This is a release with a record
number of fixes and reflects the increased popularity of Apache Camel and our
growing community.
Please find the staging repo here:
https://repos
Enterprise Integration Patterns Web Page Documentation Incomplete
-
Key: CAMEL-4243
URL: https://issues.apache.org/jira/browse/CAMEL-4243
Project: Camel
Issue Type: Task
It's just a step reaming for my goal .
Now it logs into karaf everything even when it goes to that processor that I
specified that to be logged into "new.log" .
@ "new.log" , it successfully logs but the log doesn't have the stack trace
like what it's been already logged into karaf.log
That's w
On Mon, Jul 18, 2011 at 8:27 PM, Echo wrote:
> Hello ,
> Actually I have modified my code as I misunderstood u :
>
> log4j.rootLogger=INFO, out,sylk,osgi:VmLogAppender
>
> Now it logs everything on BOTH files .
> I just need when I log like the follwong from camel :
>
> process(doSmth).log(Logging
Hello ,
Actually I have modified my code as I misunderstood u :
log4j.rootLogger=INFO, out,sylk,osgi:VmLogAppender
Now it logs everything on BOTH files .
I just need when I log like the follwong from camel :
process(doSmth).log(LoggingLevel.INFO,"new","Hello New Logger")
JUST in that case to
That's the final org.ops4j.pax.logging.cfg after updating ur comments .
Now erverything logs into new.log .
I just need erverything to be logged into karaf.log .
Except for specific process that will only log into new.log
###
You don need second appender - osgi:VmLogAppender if you wish store messages
only in one place. Second appender is unecessary to use first.
> I have already made the first step :
>
> log4j.appender.new=org.apache.log4j.RollingFileAppender
> log4j.appender.new.layout=org.apache.log4j.PatternLay
I have already made the first step :
log4j.appender.new=org.apache.log4j.RollingFileAppender
log4j.appender.new.layout=org.apache.log4j.PatternLayout
log4j.appender.new.layout.ConversionPattern=%d{ABSOLUTE} | %-5.5p | %-16.16t
| %-32.32c{1} | %-32.32C %4L | %X{bundle.id} - %X{bundle.name} -
%X{
You need specific category settings. Karaf uses log4j as logging framework
wrapped by pax-logging service. To store log messages from any category follow
these steeps:
1. Create new appender (eg. file)
log4j.appender.file=org.apache.log4j.RollingFileAppender
log4j.appender.file.layout=org.apach
I have a system that uses both Apache Camel and Karaf.
I need some specific processor to log into a new log instead of the default
one ,karaf.log.
I have reached that there is a file called "org.ops4j.pax.logging.cfg" that
is responsible for logging configuration .
Here it's the file before I
[
https://issues.apache.org/jira/browse/CAMEL-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4242.
Resolution: Fixed
> When bridging http endpoints and end users do not enable the bridgeEndpoint
>
There's only 2404 warnings left See the first 100 here:
http://camel.465427.n5.nabble.com/file/n4600069/warnings.jpeg warnings.jpeg
.
Just wonder if IDEA doesn't warn about these stuff, for example the raw type
declaration of a given generic type
Regards, Babak
--
View this message in context
When bridging http endpoints and end users do not enable the bridgeEndpoint
option they may get a NPE exception
---
Key: CAMEL-4242
URL: https://issues.apa
[
https://issues.apache.org/jira/browse/CAMEL-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067062#comment-13067062
]
Chad Beaulac commented on CAMEL-3471:
-
The UDP endpoint works when you have a codec co
On Mon, Jul 18, 2011 at 5:31 AM, Zbarcea Hadrian wrote:
> I could start the builds tomorrow morning (around 11am EDT) if nobody shouts
> and asks for more time.
>
On this glorious day, monday, it would be nice if a new build could be started.
The fix for the SMX issue has been committed, and CI
[
https://issues.apache.org/jira/browse/CAMEL-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-4234:
---
Affects Version/s: (was: 2.8.0)
Fix Version/s: (was: 2.9.0)
2.8
[
https://issues.apache.org/jira/browse/CAMEL-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4234.
Resolution: Fixed
> ProducerTemplate/MockEndpoint does not seem to trigger context exception
> han
[
https://issues.apache.org/jira/browse/CAMEL-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Brouckaert updated CAMEL-4234:
Fix Version/s: 2.9.0
> ProducerTemplate/MockEndpoint does not seem to trigger context excep
[
https://issues.apache.org/jira/browse/CAMEL-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067023#comment-13067023
]
Bryan Brouckaert commented on CAMEL-4234:
-
I tested with 2.9-SNAPSHOT and it does
[
https://issues.apache.org/jira/browse/CAMEL-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067007#comment-13067007
]
Claus Ibsen commented on CAMEL-4234:
Can you make sure you use the latest source code.
[
https://issues.apache.org/jira/browse/CAMEL-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-4234:
--
Assignee: Claus Ibsen
> ProducerTemplate/MockEndpoint does not seem to trigger context exceptio
[
https://issues.apache.org/jira/browse/CAMEL-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Brouckaert updated CAMEL-4234:
Affects Version/s: 2.7.0
2.7.1
2.7.2
The same
[
https://issues.apache.org/jira/browse/CAMEL-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Brouckaert updated CAMEL-4234:
Attachment: CAMEL-4234.zip
Added a simple example that causes the error.
There are 2 route
-1
Hi,
Sorry, I did not see the previous messages. Just realized the issue with
camel-osgi... I just ran the unit tests.
Cheers,
Ashwin...
-
-
Ashwin Karpe
Apache Camel Committer & Sr Principal Consultant
FUSESource (a Progress Softw
+1
Release looks good...
Cheers,
Ashwin...
-
-
Ashwin Karpe
Apache Camel Committer & Sr Principal Consultant
FUSESource (a Progress Software Corporation subsidiary)
http://fusesource.com
Blog: http://opensourceknowledge.blogspot.com
[
https://issues.apache.org/jira/browse/CAMEL-4241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4241.
Resolution: Fixed
> Removed unused imports from examples
>
>
>
Removed unused imports from examples
Key: CAMEL-4241
URL: https://issues.apache.org/jira/browse/CAMEL-4241
Project: Camel
Issue Type: Task
Components: examples
Reporter: Claus Ibsen
Unable to use XA JMS trabsaction on WebLogic
Key: CAMEL-4240
URL: https://issues.apache.org/jira/browse/CAMEL-4240
Project: Camel
Issue Type: Bug
Components: camel-jms
Report
31 matches
Mail list logo
