categories/JBang/index.xml

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>JBang on Apache Camel</title>
    <link>https://camel.apache.org/categories/JBang/</link>
    <description>Recent content in JBang on Apache Camel</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 24 Nov 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://camel.apache.org/categories/JBang/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to test an Integration for Camel K</title>
      <link>https://camel.apache.org/blog/2022/11/camel-k-jbang/</link>
      <pubDate>Thu, 24 Nov 2022 00:00:00 +0000</pubDate>
      
      <guid>https://camel.apache.org/blog/2022/11/camel-k-jbang/</guid>
      <description>Testing is probably one of those operations we use to repeat most of the time while building any application. Applications in Camel world are no difference. With the advent of Camel JBang, we have a unified place that can be used to perform our testing/fine tuning locally before moving to a higher environment.
During the last years of development, we have noticed that testing or fine tuning an integration directly connected to a Cloud Native environment can result a bit cumbersome.</description>
    </item>
    
  </channel>
</rss>