Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
WS-BPEL 2.0 for SOA Composite Applications with Oracle SOA Suite 11g

You're reading from   WS-BPEL 2.0 for SOA Composite Applications with Oracle SOA Suite 11g Define, model, implement, and monitor real-world BPEL business processes with SOA powered BPM.

Arrow left icon
Product type Paperback
Published in Sep 2010
Publisher Packt
ISBN-13 9781847197948
Length 616 pages
Edition 1st Edition
Languages
Arrow right icon
Toc

Table of Contents (17) Chapters Close

WS-BPEL 2.0 for SOA Composite Applications with Oracle SOA Suite 11g
Credits
1. Foreword
About the Authors
About the Reviewers
2. Preface
1. Introduction to BPEL and SOA FREE CHAPTER 2. Service Composition with BPEL 3. Advanced BPEL 4. Using BPEL with Oracle SOA Suite 11g 5. BPEL Extensions, Dynamic Parallel Flow, Dynamic Partner Links, Notification Service, Java Embedding, and Fault Management Framework 6. Entity Variables, Master and Detail Processes, Security, and Business Events in BPEL 7. Human Interactions in BPEL 8. Monitoring BPEL Processes with BAM 9. BPEL with Oracle Service Bus and Service Registry 10. BPMN to BPEL Round-tripping with BPA Suite and SOA Suite 11. Integrating BPEL with BPMN using BPM Suite

Java code embedding


Java code embedding is a method for integrating Java code and resources into BPEL processes. It allows us to embed Java code snippets directly into BPEL process code. This provides the opportunity to use Java for certain aspects where BPEL does not provide an appropriate activity. It also provides a possibility to use Java code to call other Java resources (EJBs, JCA, JMS, and so on).

To embed Java code snippets into BPEL, Oracle provides a custom BPEL activity called<exec>, defined in the http://schemas.oracle.com/bpel/extension namespace. This namespace is usually declared with the bpelx prefix, so we write the activity as<bpelx:exec>.

The BPEL server will execute the Java code, embedded in the<exec> activity, within its JTA (Java Transaction API) transaction context. If the embedded Java code calls EJBs (session or entity beans), the transactional context will be automatically propagated. If an exception occurs during the execution of the embedded...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image