没有合适的资源？快使用搜索试试~ 我知道了~

首页Java框架Camel实战教程：企业集成模式与应用开发

Java框架Camel实战教程：企业集成模式与应用开发

Camel

5星 · 超过95%的资源需积分: 10 14 下载量 104 浏览量更新于2023-06-16 收藏 3.89MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

试读

550页

《Camel实战》(原名：Camel in Action)是一本由Claus Ibsen和Jonathan Anstey合著的专业级Apache Camel教程，由Manning出版社于2010年12月发行。该书是英文版，适合对Java企业集成框架有一定了解的读者，尤其是那些希望深入学习和实践Camel技术的开发者。Camel是一个强大的Java框架，通过简洁的DSL（领域特定语言）实现企业集成模式，支持超过80种常见的数据传输方式，如HTTP、REST、JMS和Web Services。书中分为四个部分，循序渐进地引导读者： 1. 第一部分 - "First steps"：从入门开始，介绍了Camel的基本概念，包括发送、接收、路由和数据转换。这部分让读者快速上手，理解框架的核心功能。 2. 第二部分 - "Core Camel"：深入探讨了数据转换、与Java bean的交互、错误处理、单元测试、组件理解和企业集成模式等核心概念，帮助读者掌握如何构建高效且健壮的集成逻辑。 3. 第三部分 - "Out in the wild"：涉及更高级的主题，如事务处理、并发与可扩展性、项目开发、管理和监控，以及如何部署和利用Camel进行远程调用。 4. 附录 - 提供了Simple表达式语言、表达式和谓词、生产者和消费者模板、Camel社区信息以及Akka与Camel的整合等内容，以补充主章节的学习。这本书不仅包含了丰富的实战示例，还凝聚了作者作为Camel开发者的经验和实用洞察，旨在使读者能够像专业人员一样应对集成任务。此外，Manning出版社提供的折扣信息以及版权信息也包含在内，提醒读者合法获取并尊重版权。对于想要提升企业应用集成能力的开发人员来说，《Camel实战》是一本不可或缺的参考资料，无论是初次接触Camel还是希望深入研究的开发者，都能从中获益良多。

资源详情

资源推荐

CONTENTS

Developing Camel projects 359

11.1 Managing projects with Maven 360

Using Camel Maven archetypes 360

■

Camel Maven

dependencies 364

■

Using Camel in Eclipse 366

■

Using the

Maven Eclipse plugin 366

■

Using the m2eclipse plugin 368

11.2 Developing custom components 371

Setting up a new Camel component 371

■

Diving into the

implementation 373

11.3 Developing interceptors 377

Creating an InterceptStrategy 377

11.4 Using alternative languages 380

The Scala DSL 380

■

Adding Scala routes to the CamelContext 382

Mixing Java and Scala 382

11.5 Summary and best practices 384

Management and monitoring 385

12.1 Monitoring Camel 386

Checking health at the network level 386

■

Checking health at the

JVM level 388

■

Checking health at the application level 388

12.2 Using JMX with Camel 389

Using JConsole to manage Camel 390

■

Using JConsole to remotely

manage Camel 391

12.3 Tracking application activity 393

Using log files 393

■

Using core logs 394

■

Using custom

logging 394

■

Using Tracer 398

■

Using notifications 402

12.4 Managing Camel applications 405

Managing Camel application lifecycles 405

■

Managing custom

Camel components 406

12.5 Summary and best practices 409

Running and deploying Camel 410

13.1 Starting Camel 411

How Camel starts 411

■

Camel startup options 413

■

Ordering

routes 416

■

Disabling autostartup 418

13.2 Starting and stopping routes at runtime 419

Using CamelContext to start and stop routes at runtime 420

Using RoutePolicy to start and stop routes at runtime 422

CONTENTS

xvi

13.3 Shutting down Camel 424

Graceful shutdown 425

13.4 Deploying Camel 428

Embedded in a Java application 428

■

Embedded in a web

application 430

■

Embedded in JBoss Application Server 436

13.5 Camel and OSGi 437

Setting up Maven to generate an OSGi bundle 438

■

Installing

and running Apache Karaf 439

■

Deploying the example 440

13.6 Summary and best practices 441

Bean routing and remoting 443

14.1 Using beans for routing 444

Inventory update at Rider Auto Parts 444

■

Receiving messages

with @Consume 445

■

Sending messages with @Produce 448

When to use beans for routing 450

14.2 Hiding middleware 451

Introducing the starter kit 453

■

Using Spring remoting and

Camel proxies 456

14.3 Summary and best practices 460

appendix A Simple, the expression language 461

appendix B Expressions and predicates 471

appendix C The producer and consumer templates 477

appendix D The Camel community 483

appendix E Akka and Camel 487

index 501

xvii

foreword

Languages are a critical aspect of software development. They give us the vocabulary

to express what a program should do. They force us to encode our requirements in

precise and non-ambiguous terms. Lastly, they enable the sharing of knowledge

between developers. No, I’m not talking about Java, Haskell, or PL/1. I’m talking

about the languages we use to communicate from human to human, from developer

to developer, or from end user to product manager. For a long time, the world of

enterprise integration (or EAI, as it was commonly known in the “dark ages of integra-

tion”) lacked such a vocabulary. Each vendor offered a proprietary solution, which

not only failed to integrate at a technical level with other vendors’ offerings, but also

used a different language to describe the main components and their functions. This

not only caused confusion, but was also a key inhibitor to creating a community of

developers that could span the vast space of enterprise integration. Each “tribe” was

essentially held hostage by the language bestowed upon them. Ironically, integration

developers were faced with the same “tower of Babel” problem that their software was

designed to solve!

Establishing a common vocabulary that enables knowledge sharing and collabora-

tion was the key motivator for us to write Enterprise Integration Patterns (EIPs). Each

of the 65 patterns has a descriptive name, which represents the solution to a design

challenge in the integration space. Besides supporting effective communication, this

vocabulary also raises the level of abstraction at which we can describe integration

problems and solutions.

A shared vocabulary is a big step forward, but a giant step we could not imagine at

the time was that our language would spur the development of a whole family of open

FOREWORD

xviii

source messaging and enterprise service bus (ESB) products. These tools embrace the

EIP vocabulary by implementing many patterns directly in the platform. With Apache

Camel, a Splitter pattern translates directly into a “split” element in the Camel DSL.

We couldn’t have wished for a more direct translation of the pattern language into an

implementation platform.

Claus and Jon bring the saga to a grand finale by showing us how to use the Camel

pattern language to compose real-life messaging solutions. In doing so, they not only

cover fundamental concepts like routing and transformation, but also dig into often-

neglected parts of the development process, including testing, monitoring, and deploy-

ing. They find the right balance of the pattern language, Camel core concepts, and run-

ning code to help you build easy-to-understand and robust messaging solutions.

REGOR HOHPE

COAUTHOR OF ENTERPRISE INTEGRATION PATTERNS

WWW.EAIPATTERNS.COM

xix

foreword

I was one of the original founders of both Apache ActiveMQ (an open source high-

performance message broker) and ServiceMix (an open source ESB based on JBI and

OSGi). I found that Enterprise Integration Patterns were becoming increasingly cen-

tral to what we were doing on these projects and how we were using them; the only dif-

ference was the context and technologies with which we were using the patterns.

There have been many libraries and frameworks over the years to help with inte-

gration. But frequently the concepts behind the Enterprise Integration Patterns get

transformed into some complex class hierarchies or objects that need to be wired

together just so, and the original intentions and patterns are often lost. The developer

is forced from then on to focus on the low-level detail and some complex class library

API, losing the bigger picture and patterns.

Integration is hard and once you start down the path of integrating things together

the code can very easily mushroom; being able to easily comprehend, communicate,

adapt, and maintain integration solutions is vital to be able to solve integration prob-

lems efficiently in an agile way.

So we decided it was time for a new integration framework that put the EIPs at its

core and tried to raise the abstraction level so that developers could describe declara-

tively in very concise terms what Enterprise Integration Patterns they wanted to use in

a simple domain-specific language. Using a convention over configuration approach,

developers would declaratively describe what they wanted to do, using the Enterprise

Integration Pattern language; it would be both quick and easy to get things done and

剩余549页未读，继续阅读

报错错误: 找不到或无法加载主类 org.apache.camel.main.Main 原因: java.lang.ClassNotFoundException: org.apache.camel.main.Main

根据你提供的错误信息，仍然是找不到 `org.apache.camel.main.Main` 类。这个错误通常发生在缺少了Apache Camel主要模块的依赖时。请确保在你的pom.xml文件中添加了正确的Apache Camel依赖项。在 `...

我使用java -jar 还是报错Exception in thread "main" java.lang.NoClassDefFoundError: org.apache.camel.main.Main at org.apache.camel.example.MyApplication.main(MyApplication.java:9) Caused by: java.lang.ClassNotFoundException: org.apache.camel.main.Main at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:827) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:1094) ... 1 more

Exception in thread "main" org.apache.camel.RuntimeCamelException: java.lang.NoSuchMethodException: org.apache.camel.example.InfluxDBConnectBean.<init>()什么原因

根据您提供的错误信息，`NoSuchMethodException: org.apache.camel.example.InfluxDBConnectBean.()`，它指示在实例化 `InfluxDBConnectBean` 时找不到相应的构造函数。这通常发生在以下情况下： 1. 缺少无参数的...

Camel in Action, Second Edition

Camel in Action, Second Edition is a comprehensive guide to the Apache Camel integration framework. It provides a thorough introduction to Camel and then goes on to cover topics such as routing, ...

我的influxDBConfig类的名字就是influxDBConfig，内部配置如下package org.apache.camel.example; import org.apache.camel.BindToRegistry; import org.apache.camel.CamelConfiguration; import org.apache.camel.PropertyInject; import com.influxdb.client.InfluxDBClient; import com.influxdb.client.InfluxDBClientFactory; public class InfluxDBConfig implements CamelConfiguration{ @BindToRegistry public InfluxDBClient influxDBConfig(@PropertyInject("url") String url, @PropertyInject("token") String token) { // this will create an instance of this bean with the name of the method (eg myBean) return InfluxDBClientFactory.create(url, token.toCharArray()); }

根据您提供的代码，您的 `InfluxDBConfig` 类的名字确实是 `InfluxDBConfig`，而不是 `org.apache.camel.example.InfluxDBConfig`。在您使用 jbang 命令运行程序时，应该运行的是 Java 文件而不是 YAML 文件。您...

我项目的目录和yaml配置如下，启动项目还是报错 java.lang.ClassNotFoundException: org.apache.camel.example.InfluxDBConfig ├─src │ └─main │ ├─java │ │ └─org │ │ └─apache │ │ └─camel │ │ └─example │ │ Application.java │ │ InfluxDBConfig.java │ │ │ └─resources │ │ application.properties │ │ log4j2.properties │ │ │ └─routes │ create_bean.camel.yaml yarml中我做了如下配置 - beans: - name: influxDBConfig type: org.apache.camel.example.InfluxDBConfig properties: url: "http://localhost:8086" token: "token"

但是，根据您提供的错误信息 `java.lang.ClassNotFoundException: org.apache.camel.example.InfluxDBConfig`，这意味着编译或运行时找不到 `InfluxDBConfig` 类。请确保您的项目已正确编译，并且在运行时可以访问...

我运行的时候报错 java.lang.RuntimeException: java.lang.ClassNotFoundException: org.apache.camel.example.InfluxDBConfig，事实上我已经将yaml中的bean的type替换成立我项目中创建的bean了

根据报错信息，看起来是找不到 `org.apache.camel.example.InfluxDBConfig` 类导致的错误。请确保在您的项目中存在名为 `org.apache.camel.example.InfluxDBConfig` 的类，并且该类已经正确配置为 bean。另外，...

Error binding property (token=token) with name: token on bean: org.apache.camel.example.InfluxDBConnectBean@af5e9cd4 with value: token 什么原因，yaml配置如下：- beans: - name: influxDBConnectBean type: org.apache.camel.example.InfluxDBConnectBean properties: url: http://localhost:8086 token: token

根据您提供的错误信息 `Error binding property (token=token) with name: token on bean: org.apache.camel.example.InfluxDBConnectBean@af5e9cd4 with value: token`，这意味着在绑定 `token` 属性值时发生了错误...

activemq-camel-5.5.1.jar

activemq-camel-5.5.1.jar是一个Java类库，来自于Apache ActiveMQ和Apache Camel项目的结合体。Apache ActiveMQ是一个开源的异步消息传递（Messaging）中间件，而Apache Camel是一个开源的企业集成模式框架，可以...

我想通过apach camel的 yaml dsl 的方式连接到influxdb2 component，yaml中配置了路由，和influxDBConnectBean的bean to: uri: influxdb2:influxDBConnectBean id: to-3799 parameters: bridgeEndpoint: true connectionBean: connectionBean bucket: my-bucket org: my-org operation: shelf1,factory=F1,building=B2,area=A3,item=Part4 testField=10 beans: name: influxDBConnectBean type: org.apache.camel.example.InfluxDBConnectBean java中InfluxDBConnectBean.java创建好了influxDBConnectBean package org.apache.camel.example; import org.apache.camel.Configuration; import org.apache.camel.language.bean.Bean; import com.influxdb.client.InfluxDBClient; import com.influxdb.client.InfluxDBClientFactory; public class InfluxDBConnectBean { private String url; private String token; private InfluxDBClient influxDBClient; public InfluxDBConnectBean() { createConnect(); } @Bean(ref = "influxDBConnectBean") public InfluxDBClient createConnect() { System.out.println("createConnect(): token:" + token); return InfluxDBClientFactory.create("http://localhost:8086", "r51thkAg7Z7RUynP7Tkq6bJj1bbNCXIwRm4oXxJRmr0G6pQ_Mu2oE8orYxnAXy2RWzbNM4DBX53wy_inY2HR2A==".toCharArray()); } } 但是运行报错No bean could be found in the registry for: influxDBConnectBean of type: com.influxdb.client.InfluxDBClient

根据您提供的信息，报错"No bean could be found in the registry for: influxDBConnectBean of type: com.influxdb.client.InfluxDBClient"意味着Camel无法在注册表中找到正确的Bean。在您的YAML配置中，确保在...

依旧报错org.apache.camel.NoSuchBeanException: No bean could be found in the registry for: influxDBConnectBean of type: com.influxdb.client.InfluxDBClient

根据您提供的错误信息 `org.apache.camel.NoSuchBeanException: No bean could be found in the registry for: influxDBConnectBean of type: com.influxdb.client.InfluxDBClient`，这意味着在 Camel 的注册表中找...

or (Field fieldsAndParentsField : fieldsAndParentsFields) { if (StringUtils.equals(fieldsAndParentsField.getName(), camel)) { Field f = object.getClass().getDeclaredField(camel); f.setAccessible(true); Object value = f.get(object); if (StringUtils.equals(key, value.toString()) && schemaRowRuleEo.getRowEditPermission()) { System.out.println("修改成功"); } else { throw new CustomException("大马猴来了", code); } } }代码优化

.filter(f -> StringUtils.equals(f.getName(), camel)) .findFirst() .orElseThrow(() -> new CustomException("大马猴来了", code)); Field f = object.getClass().getDeclaredField(camel); f.setAccessible...

我想通过apache camel 的yaml方式想influxdb2插入数据，我在yaml 里定义了连接influxdb2的component，配置如下：- set-body: constant: "shelf1,factory=F1,building=B2,area=A3,item=Part4 temperature=35.2,bank=88.0" - to: uri: influxdb2:influxDBConnectBean id: to-3799 parameters: org: my-org bucket: my-bucket operation: insert 但是，在插入数据的时候，无法正常插入数据，因为set-body中的"shelf1,factory=F1,building=B2,area=A3,item=Part4 temperature=35.2,bank=88.0" 无法转换为org.apache.camel.component.influxdb2.data.Record类型，你能告诉我怎么办吗

根据你提供的配置，问题出现在无法将字符串转换为 `org.apache.camel.component.influxdb2.data.Record` 类型。为了解决这个问题，你可以通过以下步骤进行尝试： 1. 创建一个 Java Bean 类，用于将字符串转换为 `...

huzhouhzy

粉丝: 83
资源: 1961

上传资源快速赚钱

我的内容管理收起

我的资源快来上传第一个资源

我的收益

登录查看自己的收益

我的积分登录查看自己的积分

我的C币登录后查看C币余额

我的收藏

我的下载

下载帮助

会员权益专享

Java框架Camel实战教程：企业集成模式与应用开发

针对Java开发者的ApacheCamel入门指南

camel 手册

Camel in action(camel实战)

报错错误: 找不到或无法加载主类 org.apache.camel.main.Main 原因: java.lang.ClassNotFoundException: org.apache.camel.main.Main

Exception in thread "main" org.apache.camel.RuntimeCamelException: java.lang.NoSuchMethodException: org.apache.camel.example.InfluxDBConnectBean.<init>()什么原因

Camel in Action, Second Edition

我想通过 jbang命令的方式启动 比如 jbang -Dcamel.jbang.version=3.20.3 camel@apache/camel run ....yaml，我想知道在你上述的情况下我要run的是java还是yaml

报错Caused by: java.lang.ClassNotFoundException: org.apache.camel.main.Main

camel实战第二版

apache camel 如何配置 application.properties

我运行的时候报错 java.lang.RuntimeException: java.lang.ClassNotFoundException: org.apache.camel.example.InfluxDBConfig，事实上我已经将yaml中的bean的type替换成立我项目中创建的bean了

activemq-camel-5.5.1.jar

依旧报错org.apache.camel.NoSuchBeanException: No bean could be found in the registry for: influxDBConnectBean of type: com.influxdb.client.InfluxDBClient

会员权益专享

最新资源

我想通过 jbang命令的方式启动比如 jbang -Dcamel.jbang.version=3.20.3 camel@apache/camel run ....yaml，我想知道在你上述的情况下我要run的是java还是yaml