Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

There is nothing further to do. Any Apache Camel configuration defined in XML files in the application source code will be automatically detected. Follow the instructions below to run a new analysis/snapshot to generate new results:

What results can you expect?

Once the analysis/snapshot generation is completed, you can view the results in the normal manner (for example via CAST Enlighten):

Objects

IconDescription Icon DescriptionIconDescription

Image Modified

Apache Camel HTTP Get Operation

 Image Modified

Apache Camel JMS Queue Receive

Image Modified

Apache Camel Unknown ActiveMQ Queue Receive

Image Modified

Apache Camel HTTP Put Operation

 Image Modified

Apache Camel JMS QueueCall

Image Modified

Apache Camel Unknown ActiveMQ Queue Call

Image Modified

Apache Camel HTTP Post Operation

 Image Modified

 Apache Camel Unknown JMS Queue Receive

Image Modified

Apache Camel RabbitMQ
Queue
Topic Receive

Image Modified

Apache Camel HTTP Delete Operation 

 Image Modified

 Apache Camel Unknown JMS Queue Call

Image Modified

Apache Camel RabbitMQ
Queue
Topic Call

Image Modified

Apache Camel HTTP Any Operation 

 Image Modified

Apache Camel IBM Queue Receive

Image Modified

Apache Camel Unknown RabbitMQ
Queue
Topic Receive

Image Modified

Apache Camel Route Call

 Image Modified

Apache Camel IBM Queue Call

Image Modified

Apache Camel Unknown RabbitMQ
Queue
Topic Call

Image Modified

Apache Camel Route

 Image Modified

Apache Camel Unknown IBM_Queue Receive

Image Modified

Apache Camel File

Image Modified

Apache Camel Bean Call

 Image Modified

Apache Camel Unknown IBM Queue Call

Image Modified

Apache Camel File Call

Image Modified

Apache Camel Process Call

 Image Modified

Apache Camel ActiveMQ Queue Receive

Image Added

Apache Camel Kafka Topic Receive

Image Modified

Apache Camel Database Query

 Image Modified

Apache Camel ActiveMQ Queue Call

Image Added

Apache Camel Kafka Topic Call

Image Added

Apache Camel Unknown Kafka Topic Receive

Image Added

Apache Camel Unknown Kafka Topic Call

Only callLinks are created between various objects created by this extension.

...

Expand


Code Block
languagejava
public void configure () throws Exception {
	from("file://inputdir?fileName=order.xml")
                .routeId("readFilefromDir")
				.log(LoggingLevel.INFO, "com.toyota.tme.cws.transform.route.error", "Processing File - ${file:name}")
                .bean("FileBusiness", "moveToSedaQueue")
                .end();
}

Java DSL - callLink between Apache Camel Route and Kafka Topic Call

Expand


Code Block
languagejava
public void configure () throws Exception {
	from("direct:start")       
            .to("kafka:localhost:8080?topic=testkafkaprod3");
}

Image Added

Java DSL - callLink between Kafka Topic Receive and File Call

Expand


Code Block
public void configure () throws Exception {
	from("kafka:localhost:8080?topic=testkafkacon1&zookeeperHost=localhost&zookeeperPort=2181&groupId=group1").to("file:input");
}

Image Added

callLinks in the complete transaction

Expand

Image Added

Limitations

  • Unknown queue/process/bean/route/file/jms/kafka object is created in case where the exact name can't be retrieved
  • Routes defined using route templates result in unknown route objects 
  • All other route components are ignored. Any Route starting with a component not mentioned in the Object section , the whole of the Route with its components will be ignored.
  • Any component created with a customized name will not be handled or created
  • There may be missing/multiple links instead of one between process call and process method of the target class
  • There may be multiple links instead of one between bean call and target method of the bean
  • There may be incorrect bookmarks in few call links and objects
  • One of the signature for the overloaded method idempotentConsumer method of org.apache.camel.model.ProcessDefinition is not supported. This suspends the creation of the objects for the components in that route following this method.
  • Current version does not support Kafka topic using Kafka idempotent repository
  • Consuming messages from multiple Kafka topics is not supported
  • Kafka topic receive/call object is always created by the name whatever is present in Kafka component topic. There is a possibility that name mentioned of the topic is an alias and refers to something else. Due to some design constraints, it will not be evaluated to refer to the exact value. Hence, object will be created in the name present in Kafka component.

Future development

  •  More Components Support, Better Linking, Fixing Bookmark Issue, Custom Component Support.