Endless Ebook, One Click Away – Start Downloading at ebookname.

com

Enterprise Integration with Ruby 1st Edition Maik

Schmidt

https://ebookname.com/product/enterprise-integration-with-
ruby-1st-edition-maik-schmidt/

OR CLICK HERE

DOWLOAD EBOOK

Browse and Get More Ebook Downloads Instantly at https://ebookname.com

Click here to visit ebookname.com and download ebook now
Instant digital products (PDF, ePub, MOBI) available
Download now and explore formats that suit you...

Service Oriented Java Business Integration Enterprise

Service Bus integration solutions for Java developers
1st Ed Edition Binildas

https://ebookname.com/product/service-oriented-java-business-
integration-enterprise-service-bus-integration-solutions-for-
java-developers-1st-ed-edition-binildas/

Cloning Internet Applications with Ruby 1st Edition

Sheong

https://ebookname.com/product/cloning-internet-applications-with-
ruby-1st-edition-sheong/

Enterprise Integration Patterns Designing Building and

Deploying Messaging Solutions 1st Edition Hohpe

https://ebookname.com/product/enterprise-integration-patterns-
designing-building-and-deploying-messaging-solutions-1st-edition-
hohpe/

Chinese Women Writers and The Feminist Imagination 1905

1948 Asia s Transformations 1st Edition Yan Haiping

https://ebookname.com/product/chinese-women-writers-and-the-
feminist-imagination-1905-1948-asia-s-transformations-1st-
edition-yan-haiping/
Décompression Zeh

https://ebookname.com/product/decompression-zeh/

Crime and Culpability A Theory of Criminal Law 1st

Edition Larry Alexander

https://ebookname.com/product/crime-and-culpability-a-theory-of-
criminal-law-1st-edition-larry-alexander/

Handbook of Cognition 1st Edition Dr Koen Lamberts

https://ebookname.com/product/handbook-of-cognition-1st-edition-
dr-koen-lamberts/

Biology of Northern Krill 1st Edition Geraint A.

Tarling (Eds.)

https://ebookname.com/product/biology-of-northern-krill-1st-
edition-geraint-a-tarling-eds/

The Nonprofit Manager s Resource Directory Second

Edition Landskroner R.A.

https://ebookname.com/product/the-nonprofit-manager-s-resource-
directory-second-edition-landskroner-r-a/
Interacting with Objects Language Materiality and
Social Activity 1st Edition Maurice Nevile (Ed.)

https://ebookname.com/product/interacting-with-objects-language-
materiality-and-social-activity-1st-edition-maurice-nevile-ed/
Enterprise Integration with Ruby
A Pragmatic Guide

Maik Schmidt

The Pragmatic Bookshelf

Raleigh, North Carolina Dallas, Texas
 P r a g m a t i c

B o o k s h e l f

Many of the designations used by manufacturers and sellers to distinguish their products
are claimed as trademarks. Where those designations appear in this book, and The
Pragmatic Programmers, LLC was aware of a trademark claim, the designations have
been printed in initial capital letters or in all capitals. The Pragmatic Starter Kit, The
Pragmatic Programmer, Pragmatic Programming, Pragmatic Bookshelf and the linking g
device are trademarks of The Pragmatic Programmers, LLC.

Every precaution was taken in the preparation of this book. However, the publisher
assumes no responsibility for errors or omissions, or for damages that may result from
the use of information (including program listings) contained herein.

Our Pragmatic courses, workshops, and other products can help you and your team
create better software and have more fun. For more information, as well as the latest
Pragmatic titles, please visit us at

http://www.pragmaticprogrammer.com

Copyright © 2006 The Pragmatic Programmers LLC.

All rights reserved.

No part of this publication may be reproduced, stored in a retrieval system, or transmit-

ted, in any form, or by any means, electronic, mechanical, photocopying, recording, or
otherwise, without the prior consent of the publisher.

Printed in the United States of America.

ISBN 0-9766940-6-9
Printed on acid-free paper with 85% recycled, 30% post-consumer content.
First printing, March 2006
Version: 2006-5-4
 Für meine Eltern.
Ihr seid die Giganten, auf deren Schultern ich stehe!

For my parents.
You are the giants on whose shoulders I stand!
 Contents
Foreword viii

1 Introduction 1
1.1 What Is Enterprise Software? . . . . . . . . . . . . . . . . 2
1.2 What Is Enterprise Integration? . . . . . . . . . . . . . . 3
1.3 Why Ruby? . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4 Who Should Read This Book? . . . . . . . . . . . . . . . 5
1.5 PragBouquet . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.6 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 6

2 Databases 8
2.1 The Coupon Application . . . . . . . . . . . . . . . . . . . 9
2.2 Database Interface (DBI) . . . . . . . . . . . . . . . . . . 25
2.3 Object-Relational Mappers . . . . . . . . . . . . . . . . . 28
2.4 Lightweight Directory Access Protocol (LDAP) . . . . . . 51

3 Processing XML 79
3.1 A Short XML Reminder . . . . . . . . . . . . . . . . . . . 81
3.2 Generating XML Documents . . . . . . . . . . . . . . . . 83
3.3 Processing XML Documents . . . . . . . . . . . . . . . . 95
3.4 Validating XML Documents . . . . . . . . . . . . . . . . . 127
3.5 Are There Alternatives to XML? . . . . . . . . . . . . . . 132

4 Low-Ceremony Distributed Applications 145

4.1 “I’d Rather Use a Socket” . . . . . . . . . . . . . . . . . . 146
4.2 Remote Procedure Calls Using HTTP . . . . . . . . . . . 159

5 Distributed Applications with RPC 179

5.1 Another Day, Another Protocol . . . . . . . . . . . . . . . 179
5.2 We Will Take No REST, Will We? . . . . . . . . . . . . . . 189
5.3 SOAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
5.4 CORBA, RMI, and Friends . . . . . . . . . . . . . . . . . 221
 CONTENTS vii

6 Tools and Techniques 240

6.1 Internationalization and Localization . . . . . . . . . . . 240
6.2 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
6.3 Creating Daemons and Services . . . . . . . . . . . . . . 279
6.4 Build and Deployment Process . . . . . . . . . . . . . . . 286
6.5 Project Automation with Rake . . . . . . . . . . . . . . . 303
6.6 Testing Legacy Applications . . . . . . . . . . . . . . . . . 314

A Resources 321
A.1 Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . 321
 Foreword
A few years ago, I came across the Ruby programming language, and I fell in
love. Somehow, it just seemed to work the way my brain works—I can express
myself in Ruby more naturally and with less intervening fluff than in any other
language I know. I liked it so much I persuaded Andy Hunt to coauthor a book
about it.

That was back in 1999. Since then, a lot has happened in the Ruby world.
The language went from release 1.6 to 1.8, and the standard library matured
into something world class. It gained a standardized documentation system, a
standard library distribution mechanism, and a fine build tool. I produced a
second edition of Programming Ruby to celebrate.

And now, for the first time, I can seriously say that Ruby is ready for the
enterprise. The language is stable, the libraries are great, and there is a growing
pool of talented and enthusiastic Ruby developers, all rising to the challenge.
We see companies such as Amazon and EarthLink using Ruby for both internal-
and external-facing projects.

The problem is that—until now—there wasn’t much documentation on using

Ruby in the enterprise. Sure, you can always find the API documentation for a
library, but that doesn’t really explain the how and the why.

Now the situation has changed. With Enterprise Integration with Ruby, Maik
has done something I would have thought impossible. Not only has he doc-
umented just how to use Ruby to create new enterprise solutions and to knit
together existing applications, but he has also documented the backgrounds to
all the technologies, along with how and when to use each.

I consider this book a worthy partner to Programming Ruby. With it, you’ll
exploit the power and flexibility of Ruby to create new solutions for your com-
pany in record time.

And, just as importantly, you’ll have fun.

Dave Thomas
The Pragmatic Programmers
 There are two types of complex systems: those that have
grown out of simpler systems and those that do not work.
Unknown

Chapter 1

Introduction
Have you ever worked for a big enterprise? Do you remember your
expectations as you walked into work on that first day? Whistling as
the sun shone brightly, you might have been thinking, “It will be great
to work for <company name here>. They will have a professional envi-
ronment where coffee is free and where every system has been specified
accurately, implemented carefully, and tested thoroughly. Hmmmm...
I wonder which database and programming language they use.”
After your fifth cup of free coffee (around 9:07) you came to realize that
the real world looks completely different from your expectations. Typi-
cal enterprises use dozens, hundreds, and sometimes even thousands
of applications, components, services, and databases. Many of them
were custom-built in-house or by third parties, some were bought, oth-
ers are based on open source projects, and the origin of a few—usually
the most critical ones—is completely unknown. A lot of applications
are very old, some are fairly new, and seemingly no two of them were
written using the same tools. They run on heterogeneous operating sys-
tems and hardware, they use databases and messaging systems from
various vendors, and they were written in completely different program-
ming languages.
The reasons for this are manifold. You can find countless books that
explain why the situation is so bad. You can even find books claim-
ing that they help you prevent such chaos. This book uses another
approach. We will not help you clean up this mess, but we will help
you deal with the problems pragmatically. Instead of complaining that
valuable data is spread across different database schemas or across
databases from several vendors, we will write code that integrates it. We
will take it even a step further and write new applications that aggregate
 W HAT I S E NTERPRISE S OFTWARE ? 2

all your existing resources. It doesn’t matter if we have to use relational

databases, LDAP repositories, XML files, or web services based on dif-
ferent protocol standards. We will blend data from multiple, disparate
databases to create new business knowledge.
Along the way we’ll show you how to solve all the small day-to-day
problems. These are the issues that occur over and over again, espe-
cially when developing enterprise software. We will access relational
databases such as Oracle and MySQL, and we will work with LDAP
repositories. We’ll show you how to do application logging, how to
deploy your software, how to automate tedious and error-prone tasks,
and how to survive in an international environment. Oh, and as you
might have guessed already from the book’s title, we will use Ruby to
accomplish all these feats.

1.1 What Is Enterprise Software?

In Patterns of Enterprise Application Architecture [Fow03], Martin Fowler
writes, “Enterprise applications are about the display, manipulation,
and storage of large amounts of often complex data and the support or
automation of business processes with that data.”
That’s a concise but nevertheless abstract definition, because every
nontrivial piece of software has to store, manipulate, and display data.
Video games do nothing else (and modern video games also need huge
amounts of data that often can get complex). The key point in the pre-
vious definition is the second part: the data in enterprise applications
is used for business processes and not for rendering alien spaceships.
Unsurprisingly, there are more differences between enterprise applica-
tions and other types of software. For example, enterprise applications
are often created only for a small user group that is in close contact
with the development team, implying the developers know their cus-
tomers very well. In extreme cases programs are written for only a
single person (special report generators for the CEO, for example).
Enterprise software demands a certain set of tools. Large amounts
of data—complex or not—have to be stored somehow and somewhere.
Often it is stored in relational databases, but it can also be in plain-text
files or LDAP repositories. In addition, modern enterprise software is
often based on distributed architectures consisting of many small to
midsize components that perform specialized tasks and that are con-
 W HAT I S E NTERPRISE I NTEGRATION ? 3

nected by some kind of middleware such as CORBA, RMI, SOAP, and

XML-RPC.
Obviously, as an enterprise software developer, you’re better off if you
know how to deal with such technologies. You shouldn’t be troubled by
the details of reading from a relational database or accessing an LDAP
repository. Mastering skills such as these help you concentrate on the
fun stuff—the application itself.

1.2 What Is Enterprise Integration?

Enterprise integration is a rather vague term and cannot be defined in
a strict mathematical sense. Simply put, it happens whenever you use
an existing enterprise resource to achieve some results. If you use an
existing database or web service in your application, you’re perform-
ing enterprise integration. If you build a new component that is used
by other pieces of your existing architecture, you’re doing enterprise
integration, too.
Integration needn’t just happen inside a single enterprise. It’s quite
possible—and not too unusual—that the software or data of two differ-
ent enterprises has to be integrated. If you’re using a payment gateway
to bill your customers, for example, you’re effectively integrating enter-
prise software.
You might ask yourself whether every development activity in an enter-
prise environment is some kind of enterprise integration. There are a
few exceptions. Enterprise integration does not happen when you build
a completely new piece of software from scratch, for example. In reality
this case is rare, but from a theoretical point of view this is the only
clear exception.
Enterprise integration often means integration with standard software
such as databases, LDAP repositories, message queues, ERM systems,
and so on. If you’re using one of these technologies, chances are good
that you’re doing some enterprise integration.

1.3 Why Ruby?

Most enterprise software running today was written in languages such
as COBOL, C/C++, and Java. Because of its distributed nature, enter-
prise software often makes it easy to use new tools and programming
 W HY R UBY ? 4

languages. When you have to create a small stand-alone application—

one that relies only upon an existing database, SOAP service, or LDAP
repository—it almost doesn’t seem to matter whether you were to write
it in C++, Java, or Ruby. But if you look into it more deeply, dynamic
languages such as Perl, Python, and Ruby have many advantages,
especially in enterprise environments:
• They are interpreted and do not need a compile phase, which
increases development speed tremendously. After editing your
program, you can see the results of your changes immediately.
• Enterprise software is about munging data. Dynamic languages
are designed to handle data and include high-level data types such
as hashes.
• Memory management is dealt with by the language. This is a great
advantage over languages such as C++ where you have to specify
the length of each string you read from a database. Dynamic lan-
guages prevent waste and result in more concise, more robust,
and more secure software.
• Software written in dynamic languages is installed as source code,
so you always know exactly which version is currently running on
your production system. Gone are the days when you had to guess
whether a certain binary executable is the right one.
We will show you Ruby’s strengths and how Ruby helps you accom-
plish many tasks much faster, more elegantly, and with more fun than
with any other programming language available today. But, even more
important, we will also tell you about Ruby’s weaknesses. Ruby is com-
paratively young, and although the core of the language is mature and
lots of excellent libraries are available, many features are still missing
or incomplete.
Although there is no industry standard for enterprise programming
with Ruby (as there is with J2EE or .NET), everything you need is
readily available. The most important libraries come with every Ruby
distribution, and the standard distribution has grown rapidly over the
last years. All the other stuff can be found in public places such as
RubyForge1 or the Ruby Application Archive.2

1 http://www.rubyforge.org
2 http://raa.ruby-lang.org
 W HO S HOULD R EAD T HIS B OOK ? 5

1.4 Who Should Read This Book?

This book was written for experienced enterprise developers who know
Java, C#, or C++ but don’t know much Ruby (although you should
probably have read Programming Ruby [TFH05]). We assume you are
familiar with relational databases and have at least an idea of what
LDAP is. Maybe you do not know RELAX NG, but you understand the
concepts of XML and what well-formed, SAX2, and DOM mean.
You’ve probably used tools such as object-relational mappers. Maybe
you’re familiar with Enterprise Java Beans (EJB), Java Data Objects
(JDO), and so on. Maybe you’re fed up with editing configuration files
instead of coding. You are looking for better ways to integrate the exist-
ing resources in your company, and you are looking for better ways to
quickly create new and fancy applications based on all the wonderful
stuff you already have.
Depending on the tools you’ve used to build your architecture, differ-
ent choices are available for the integration process. If you’re using
message queues, you have a lot of freedom and flexibility for integrat-
ing your services and software with others. The same holds true for
all kinds of web service protocols. It’s slightly different with databases,
because they usually do not offer interfaces as clean as message-based
systems do. Sometimes you have to access tables directly, and some-
times you have to use a set of stored procedures written in a proprietary
database programming language.
In this book we do not talk about sophisticated messaging patterns.
Instead, we cover the basics. We show you how to use databases, web
services, XML files, and all the other legacy stuff you want to combine
for building new applications.

1.5 PragBouquet
To make things more interesting and tangible, we’ve founded an imag-
inary company called PragBouquet. It sells flowers from a web shop.
Customers from all over the world can order flowers and send them to
people living in the United States.
PragBouquet’s business demands a lot of components and services. It
depends on several partners, too. Their current infrastructure is shown
in Figure 1.1, on the following page. Customers place orders in the web
shop. The shop communicates with the central order system. Because
 A CKNOWLEDGMENTS 6

Figure 1.1: PragBouquet Infrastructure

PragBouquet has no billing system, the order system uses an external

payment gateway to charge orders. In parallel, the production system
is informed of new orders, and busy florists create wonderful bunches
of flowers. Eventually, the floral goods are picked up by a parcel service
and are delivered to the happy recipient.
This is only a rough overview. We’ll show single components in more
detail when necessary.

1.6 Acknowledgments
First, I’d like to thank Dave Thomas and Andy Hunt for giving me the
opportunity to write this book for the Pragmatic Bookshelf. Working
with them has been both an honor and a pleasure. I couldn’t imagine
better or more professional working conditions.
It would be impossible to write a book about software for enterprise
integration without the software itself. The following gentlemen kindly
made their ingenious work public for free and have always responded
quickly and accurately to all my questions: Yukihiro “Matz” Matsumoto,
Will Drewry, arton (the author of Rjb), Sean Russel, Ian Macdonald,
Takaaki Tateishi, Thomas Uehlinger, Jim Weirich, Nikolai Lugovoi, Matt
Mower, Daniel Berger, why the lucky stiff, Minero Aoki, Michael Neu-
 A CKNOWLEDGMENTS 7

mann, Kubo Takehiro, Tomita Masahiro, David Heinemeier Hansson,

Hiroshi Nakamura, John W. Small, Takahashi Masayoshi, Gotou Yuu-
zou, Yoshida Masato, and Grant McLean.
Please join me in thanking my reviewers: Frank Tewissen, Matthias
“Matze” Klame, Uwe Simon, and Kaan Karaca did an awesome job!
Without their corrections and suggestions this book wouldn’t be half
as good.
A loud “Thank you very much!!!” goes to all the people who sent
errata and suggestions during the beta book process: Lee Grey, Hoang
Uong, Ola Bini, Ron Lusk, John Athayde, Blair Zajac, Jim Weirich, Pat
Podenski, Gregory Brown, Lachlan Dowding, Sean, Eldon, Henry Chiu,
Stuart Halloway, Raymond Brigleb, Ken Barker, Peter Morelli, Eric-
Olivier Lamey, Jim Kimball, Wilson Bilkovich, John Douthat, Remco
van ’t Veer, Mark Mayo, Joe Duhamel, Carl Graf, Adam Keys, Manirith
Nuth, Andres Paglayan, Dána Watanabe, Mike Stok, Eric Kramer, and
Urban Hafner.
Perhaps there are authors who write books in isolation under a rock
or on a lonesome island. Fortunately, I didn’t, and I got invaluable
support from a lot of wonderful people. I am deeply grateful to my
parents (this one is for you); my sister, Yvonne Janka (yet another
book you won’t read?); my brother, André Schmidt (for relaxing shop-
ping/running tours and even more relaxing evenings with “the boys”);
Christian and Agnieszka Rattat (for being true friends when I needed
them most); Frank Tewissen (for listening patiently and for advising
carefully); Manu (for being “die Manu”! Heja BVB!); AleX Reinartz (I’m
looking forward to the next decades); Bettina Hamidian and Corinna
Lorscheid (for insightful talks and lots of fun); Katja Wevelsiep (let’s
have a coffee tomorrow, OK?); Frank Möcke (for giving me the opportu-
nity to publish texts in my mother tongue); Dr. Andreas Kötz (for your
appreciation); and the “gleis drei” staff (for providing a perfect proof-
reading environment).
Mia: I promise to write until I finally learn to clearly express how excit-
ing and wonderful the last months have been.
 Another Random Document on
Scribd Without Any Related Topics
 When the judge announced the sentence, and they realized that
Custer Pennington was to pay the death penalty, although it had been
almost a foregone conclusion, the shock left them numb and cold.
Neither the condemned man nor his father gave any outward
indication of the effect of the blow. They were Penningtons, and the
Pennington pride permitted them no show of weakness before the eyes
of strangers. Nor yet was there any bravado in their demeanor. The
younger Pennington did not look at his father or Shannon as he was led
away toward his cell, between two bailiffs.
As Shannon Burke walked from the court room with the colonel,
she could think of nothing but the fact that in two months the man she
loved was to be hanged. She tried to formulate plans for his release—
wild, quixotic plans; but she could not concentrate her mind upon
anything but the bewildering thought that in two months they would
hang him by the neck until he was dead.
She knew that he was innocent. Who, then, had committed the
crime? Who had murdered Wilson Crumb?
Outside the Hall of Justice she was accosted by Allen, whom she
attempted to pass without noticing. The colonel turned angrily on the
man. He was in the mood to commit murder himself; but Allen
forestalled any outbreak on the old man’s part by a pacific gesture of
his hands and a quick appeal to Shannon.
“Just a moment, please,” he said. “I know you think I had a lot to
do with Pennington’s conviction. I want to help you now. I can’t tell you
why. I don’t believe he was guilty. I changed my mind recently. If I can
see you alone, Miss Burke, I can tell you something that might give you
a line on the guilty party.”
“Under no conceivable circumstances can you see Miss Burke
alone,” snapped the colonel.
“I’m not going to hurt her,” said Allen. “Just let her talk to me here
alone on the sidewalk, where no one can overhear.”
“Yes,” said the girl, who could see no opportunity pass which held
the slightest ray of hope for Custer.
 The colonel walked away, but turned and kept his eyes on the man
when he was out of earshot. Allen spoke hurriedly to the girl for ten or
fifteen minutes, and then turned and left her. When she returned to the
colonel, the latter did not question her. When she did not offer to
confide in him, he knew that she must have good reasons for her
reticence, since he realized that her sole interest lay in aiding Custer.

* * * * *
For the next two months the colonel divided his time between
Ganado and San Francisco, that he might be near San Quentin, where
Custer was held pending the day of execution. Mrs. Pennington, broken
in health by the succession of blows that she had sustained, was sorely
in need of his companionship and help. Eva was rapidly regaining her
strength and some measure of her spirit. She had begun to realize how
useless and foolish her attempt at self-destruction had been, and to see
that the braver and nobler course would have been to give Guy the
benefit of her moral support in his time of need.
The colonel, who had wormed from Custer the full story of his
conviction upon the liquor charge, was able to convince her that Guy
had not played a dishonorable part, and that of the two he had
suffered more than Custer. Her father did not condone or excuse Guy’s
wrong-doing, but he tried to make her understand that it was no
indication of a criminal inclination, but rather the thoughtless act of an
undeveloped boy.
During the two months they saw little or nothing of Shannon. She
remained in Los Angeles, and when she made the long trip to San
Quentin to see Custer, or when they chanced to see her, they could not
but note how thin and drawn she was becoming. The roses had left her
cheeks, and there were deep lines beneath her eyes, in which there
was constantly an expression of haunting fear.
As the day of the execution drew nearer, the gloom that had
hovered over Ganado for months settled like a dense pall upon them
all. On the day before the execution the colonel left for San Francisco,
to say good-by to his son for the last time. Custer had insisted that his
mother and Eva must not come, and they had acceded to his wish.
 On the afternoon when the colonel arrived at San Quentin, he was
permitted to see his son for the last time. The two conversed in low
tones, Custer asking questions about his mother and sister, and about
the little everyday activities of the ranch. Neither of them referred to
the event of the following morning.
“Has Shannon been here to-day?” the colonel asked.
Custer shook his head.
“I haven’t seen her this week,” he said. “I suppose she dreaded
coming. I don’t blame her. I should like to have seen her once more,
though!”
Presently they stood in silence for several moments.
“You’d better go, dad,” said the boy. “Go back to mother and Eva.
Don’t take it too hard. It isn’t so bad, after all. I have led a bully life,
and I have never forgotten once that I am a Pennington. I shall not
forget it to-morrow.”
The father could not speak. They clasped hands once, the older
man turned away, and the guards led Custer back to the death cell for
the last time.
 CHAPTER XXXVII
It was morning when the colonel reached the ranch. He found
his wife and Eva sitting in Custer’s room. They knew the hour, and
they were waiting there to be as near him as they could. They were
weeping quietly. In the kitchen across the patio they could hear
Hannah sobbing.
They sat there for a long time in silence. Suddenly they heard a
door slam in the patio, and the sound of some one running.
“Colonel Pennington! Colonel Pennington!” a voice cried.
The colonel stepped to the door of Custer’s room. It was the
bookkeeper calling him.
“What is it?” he asked. “Here I am.”
“The Governor has granted a stay of execution. There is new
evidence. Miss Burke is on her way here now. She has found the
man who killed Crumb!”
What more he said the colonel did not hear, for he had turned
back into the room, and, collapsing on his son’s bed, had broken into
tears—he who had gone through those long weeks like a man of
iron.
It was nearly noon before Shannon arrived. She had been driven
from Los Angeles by an attaché of the district attorney’s office. The
Penningtons had been standing on the east porch, watching the
road with binoculars, so anxious were they for confirmation of their
hopes.
She was out of the car before it had stopped and was running
toward them. The man who had accompanied her followed, and
joined them on the porch. Shannon threw her arms around Mrs.
Pennington’s neck.
“He is safe!” she cried. “Another has confessed, and has satisfied
the district attorney of his guilt.”
“Who was it?” they asked.
Shannon turned toward Eva.
“It is going to be another blow to you all,” she said; “but wait
until I’m through, and you will understand that it could not have
been otherwise. It was Guy who killed Wilson Crumb.”
“Guy? Why should he have done it?”
“That was it. That was why suspicion was never directed toward
him. Only he knew the facts that prompted him to commit the deed.
It was Allen who suggested to me the possibility that it might have
been Guy. I have spent nearly two months at the sanatorium with
this gentleman from the district attorney’s office, in an effort to
awaken Guy’s sleeping intellect to a realization of the past, and of
the present necessity for recalling it. He has been improving steadily,
but it was only yesterday that memory returned to him. We worked
on the theory that if he could be made to realize that Eva lived, the
cause of his mental sickness would be removed. We tried everything,
and we had almost given up hope when, almost like a miracle, his
memory returned, while he was looking at a kodak picture of Eva
that I had shown him. The rest was easy, especially after he knew
that she had recovered. Instead of the necessity for confession
resulting in a further shock, it seemed to inspirit him. His one
thought was of Custer, his one hope that we would be in time to
save him.”
“Why did he kill Crumb?” asked Eva.
“Because Crumb killed Grace. He told me the whole story
yesterday.”
Very carefully Shannon related all that Guy had told of Crumb’s
relations with his sister, up to the moment of Grace’s death.
 “I am glad he killed him!” said Eva. “I would have had no respect
for him if he hadn’t done it.”
“Guy told me that the evening before he killed Crumb he had
been looking over a motion picture magazine, and he had seen there
a picture of Crumb which tallied with the photograph he had taken
from Grace’s dressing table—a portrait of the man who, as she told
him, was responsible for her trouble. Guy had never been able to
learn this man’s identity, but the picture in the magazine, with his
name below it, was a reproduction of the same photograph. There
was no question as to the man’s identity. The scarfpin, and a lock of
hair falling in a peculiar way over the forehead, marked the pictures
as identical. Though Guy had never seen Crumb, he knew from
conversations that he had heard here that it was Wilson Crumb who
was directing the picture that was to be taken on Ganado. He
immediately got his pistol, saddled his horse, and rode up to the
camp in search of Crumb. It was he whom one of the witnesses
mistook for Custer. He then did what the district attorney attributed
to Custer. He rode to the mouth of Jackknife, and saw the lights of
Crumb’s car up near El Camino Largo. While he was in Jackknife, Eva
must have ridden down Sycamore from her meeting with Crumb,
passing Jackknife before Guy rode back into Sycamore. He rode up
to where Crumb was attempting to crank his engine. Evidently the
starter had failed to work, for Crumb was standing in front of the
car, in the glare of the headlights, attempting to crank it. Guy
accosted him, charged him with the murder of Grace, and shot him.
He then started for home by way of El Camino Largo. Half a mile up
the trail he dismounted and hid his pistol and belt in a hollow tree.
Then he rode home.
“He told me that while he never for an instant regretted his act,
he did not sleep all that night, and was in a highly nervous condition
when the shock of Eva’s supposed death unbalanced his mind;
otherwise he would gladly have assumed the guilt of Crumb’s death
at the time when Custer and I were accused.
 “After we had obtained Guy’s confession, Allen gave us further
information tending to prove Custer innocent. He said he could not
give it before without incriminating himself; and as he had no love
for Custer, he did not intend to hang for a crime he had not
committed. He knew that he would surely hang if he confessed the
part that he had played in formulating the evidence against Custer.
“Crumb had been the means of sending Allen to the county jail,
after robbing him of several thousand dollars. The day before Crumb
was killed, Allen’s sentence expired. The first thing he did was to
search for Crumb, with the intention of killing the man. He learned
at the studio where Crumb was, and he followed him immediately.
He was hanging around the camp out of sight, waiting for Crumb,
when he heard the shot that killed him. His investigation led him to
Crumb’s body. He was instantly overcome by the fear, induced by his
guilty conscience, that the crime would be laid at his door. In casting
about for some plan by which he might divert suspicion from himself,
he discovered an opportunity to turn it against a man whom he
hated. The fact that he had been a stableman on Ganado, and was
familiar with the customs of the ranch, made it an easy thing for him
to go to the stables, saddle the Apache, and ride him up Sycamore
to Crumb’s body. Here he deliberately pulled off the fore shoe from
the horse and hid it under Crumb’s body. Then he rode back to the
stable, unsaddled the Apache, and made his way to the village.
“The district attorney said that we need have no fear but that
Custer will be exonerated and freed. And, Eva”—she turned to the
girl with a happy smile—“I have it very confidentially that there is
small likelihood that any jury in southern California will convict Guy,
if he bases his defense upon a plea of insanity.”
Eva smiled bravely and said:
“One thing I don’t understand, Shannon, is what you were doing
brushing the road with a bough from a tree, on the morning after
the killing of Crumb, if you weren’t trying to obliterate some one’s
tracks.”
 “That’s just what I was trying to do,” said Shannon. “Ever since
Custer taught me something about tracking, it has held a certain
fascination for me, so that I often try to interpret the tracks I see
along the trails in the hills. It was because of this, I suppose, that I
immediately recognized the Apache’s tracks around the body of
Crumb. I immediately jumped to the conclusion that Custer had
killed him, and I did what I could to remove this evidence. As it
turned out, my efforts did more harm than good, until Allen’s
explanation cleared up the matter.”
“And why,” asked the colonel, “did Allen undergo this sudden
change of heart?”
Shannon turned toward him, her face slightly flushed, though
she looked him straight in the eyes as she spoke.
“It is a hard thing for me to tell you,” she said. “Allen is a bad
man—a very bad man; yet in the worst of man there is a spark of
good. Allen told me this morning, in the district attorney’s office,
what it was that had kindled to life the spark of good in him. He is
my father.”

THE END
 Transcriber’s Notes
Punctuation, hyphenation, and spelling were made
consistent when a predominant preference was found in
the original book; otherwise they were not changed.
Simple typographical errors were corrected;
unbalanced quotation marks were remedied when the
change was obvious, and otherwise left unbalanced.
Transcriber removed redundant half-title page.
Page 60: “some one’s else happiness” was printed
that way.
Page 78: “an unkind face” was printed that way; may
be a typographical error for “fate”.
Page 79: “the possessor a quiet humor” was printed
that way, likely omitting an “of”.
Page 87: “Half an hour later he emerged” originally
was printed as “merged”.
Page 189: “which had arisen in his mind and would
not down.” was printed that way; probably should be “go
down.”
Page 200: “she cared about just then” originally was
printed as “just them”.
Page 248: “There’s be a whole regiment” was printed
that way.
 Page 263: “she was purposely avoiding her” was
printed that way, but “she” perhaps should be “he”.
Page 310: “leap of the murderer’s horse” originally
was printed as “murder’s”.
Page 319: “pulled off the fore shoe” originally was
printed as “the off”.
*** END OF THE PROJECT GUTENBERG EBOOK THE GIRL FROM
HOLLYWOOD ***

Updated editions will replace the previous one—the old editions

will be renamed.

Creating the works from print editions not protected by U.S.

copyright law means that no one owns a United States
copyright in these works, so the Foundation (and you!) can copy
and distribute it in the United States without permission and
without paying copyright royalties. Special rules, set forth in the
General Terms of Use part of this license, apply to copying and
distributing Project Gutenberg™ electronic works to protect the
PROJECT GUTENBERG™ concept and trademark. Project
Gutenberg is a registered trademark, and may not be used if
you charge for an eBook, except by following the terms of the
trademark license, including paying royalties for use of the
Project Gutenberg trademark. If you do not charge anything for
copies of this eBook, complying with the trademark license is
very easy. You may use this eBook for nearly any purpose such
as creation of derivative works, reports, performances and
research. Project Gutenberg eBooks may be modified and
printed and given away—you may do practically ANYTHING in
the United States with eBooks not protected by U.S. copyright
law. Redistribution is subject to the trademark license, especially
commercial redistribution.

START: FULL LICENSE

THE FULL PROJECT GUTENBERG LICENSE
 PLEASE READ THIS BEFORE YOU DISTRIBUTE OR USE THIS WORK

To protect the Project Gutenberg™ mission of promoting the

free distribution of electronic works, by using or distributing this
work (or any other work associated in any way with the phrase
“Project Gutenberg”), you agree to comply with all the terms of
the Full Project Gutenberg™ License available with this file or
online at www.gutenberg.org/license.

Section 1. General Terms of Use and

Redistributing Project Gutenberg™
electronic works
1.A. By reading or using any part of this Project Gutenberg™
electronic work, you indicate that you have read, understand,
agree to and accept all the terms of this license and intellectual
property (trademark/copyright) agreement. If you do not agree
to abide by all the terms of this agreement, you must cease
using and return or destroy all copies of Project Gutenberg™
electronic works in your possession. If you paid a fee for
obtaining a copy of or access to a Project Gutenberg™
electronic work and you do not agree to be bound by the terms
of this agreement, you may obtain a refund from the person or
entity to whom you paid the fee as set forth in paragraph 1.E.8.

1.B. “Project Gutenberg” is a registered trademark. It may only

be used on or associated in any way with an electronic work by
people who agree to be bound by the terms of this agreement.
There are a few things that you can do with most Project
Gutenberg™ electronic works even without complying with the
full terms of this agreement. See paragraph 1.C below. There
are a lot of things you can do with Project Gutenberg™
electronic works if you follow the terms of this agreement and
help preserve free future access to Project Gutenberg™
electronic works. See paragraph 1.E below.
1.C. The Project Gutenberg Literary Archive Foundation (“the
Foundation” or PGLAF), owns a compilation copyright in the
collection of Project Gutenberg™ electronic works. Nearly all the
individual works in the collection are in the public domain in the
United States. If an individual work is unprotected by copyright
law in the United States and you are located in the United
States, we do not claim a right to prevent you from copying,
distributing, performing, displaying or creating derivative works
based on the work as long as all references to Project
Gutenberg are removed. Of course, we hope that you will
support the Project Gutenberg™ mission of promoting free
access to electronic works by freely sharing Project Gutenberg™
works in compliance with the terms of this agreement for
keeping the Project Gutenberg™ name associated with the
work. You can easily comply with the terms of this agreement
by keeping this work in the same format with its attached full
Project Gutenberg™ License when you share it without charge
with others.

1.D. The copyright laws of the place where you are located also
govern what you can do with this work. Copyright laws in most
countries are in a constant state of change. If you are outside
the United States, check the laws of your country in addition to
the terms of this agreement before downloading, copying,
displaying, performing, distributing or creating derivative works
based on this work or any other Project Gutenberg™ work. The
Foundation makes no representations concerning the copyright
status of any work in any country other than the United States.

1.E. Unless you have removed all references to Project

Gutenberg:

1.E.1. The following sentence, with active links to, or other

immediate access to, the full Project Gutenberg™ License must
appear prominently whenever any copy of a Project
Gutenberg™ work (any work on which the phrase “Project
Gutenberg” appears, or with which the phrase “Project
Gutenberg” is associated) is accessed, displayed, performed,
viewed, copied or distributed:

This eBook is for the use of anyone anywhere in the United

States and most other parts of the world at no cost and
with almost no restrictions whatsoever. You may copy it,
give it away or re-use it under the terms of the Project
Gutenberg License included with this eBook or online at
www.gutenberg.org. If you are not located in the United
States, you will have to check the laws of the country
where you are located before using this eBook.

1.E.2. If an individual Project Gutenberg™ electronic work is

derived from texts not protected by U.S. copyright law (does not
contain a notice indicating that it is posted with permission of
the copyright holder), the work can be copied and distributed to
anyone in the United States without paying any fees or charges.
If you are redistributing or providing access to a work with the
phrase “Project Gutenberg” associated with or appearing on the
work, you must comply either with the requirements of
paragraphs 1.E.1 through 1.E.7 or obtain permission for the use
of the work and the Project Gutenberg™ trademark as set forth
in paragraphs 1.E.8 or 1.E.9.

1.E.3. If an individual Project Gutenberg™ electronic work is

posted with the permission of the copyright holder, your use and
distribution must comply with both paragraphs 1.E.1 through
1.E.7 and any additional terms imposed by the copyright holder.
Additional terms will be linked to the Project Gutenberg™
License for all works posted with the permission of the copyright
holder found at the beginning of this work.

1.E.4. Do not unlink or detach or remove the full Project

Gutenberg™ License terms from this work, or any files
 containing a part of this work or any other work associated with
Project Gutenberg™.

1.E.5. Do not copy, display, perform, distribute or redistribute

this electronic work, or any part of this electronic work, without
prominently displaying the sentence set forth in paragraph 1.E.1
with active links or immediate access to the full terms of the
Project Gutenberg™ License.

1.E.6. You may convert to and distribute this work in any binary,
compressed, marked up, nonproprietary or proprietary form,
including any word processing or hypertext form. However, if
you provide access to or distribute copies of a Project
Gutenberg™ work in a format other than “Plain Vanilla ASCII” or
other format used in the official version posted on the official
Project Gutenberg™ website (www.gutenberg.org), you must,
at no additional cost, fee or expense to the user, provide a copy,
a means of exporting a copy, or a means of obtaining a copy
upon request, of the work in its original “Plain Vanilla ASCII” or
other form. Any alternate format must include the full Project
Gutenberg™ License as specified in paragraph 1.E.1.

1.E.7. Do not charge a fee for access to, viewing, displaying,

performing, copying or distributing any Project Gutenberg™
works unless you comply with paragraph 1.E.8 or 1.E.9.

1.E.8. You may charge a reasonable fee for copies of or

providing access to or distributing Project Gutenberg™
electronic works provided that:

• You pay a royalty fee of 20% of the gross profits you derive
from the use of Project Gutenberg™ works calculated using the
method you already use to calculate your applicable taxes. The
fee is owed to the owner of the Project Gutenberg™ trademark,
but he has agreed to donate royalties under this paragraph to
the Project Gutenberg Literary Archive Foundation. Royalty
 payments must be paid within 60 days following each date on
which you prepare (or are legally required to prepare) your
periodic tax returns. Royalty payments should be clearly marked
as such and sent to the Project Gutenberg Literary Archive
Foundation at the address specified in Section 4, “Information
about donations to the Project Gutenberg Literary Archive
Foundation.”

• You provide a full refund of any money paid by a user who

notifies you in writing (or by e-mail) within 30 days of receipt
that s/he does not agree to the terms of the full Project
Gutenberg™ License. You must require such a user to return or
destroy all copies of the works possessed in a physical medium
and discontinue all use of and all access to other copies of
Project Gutenberg™ works.

• You provide, in accordance with paragraph 1.F.3, a full refund of

any money paid for a work or a replacement copy, if a defect in
the electronic work is discovered and reported to you within 90
days of receipt of the work.

• You comply with all other terms of this agreement for free
distribution of Project Gutenberg™ works.

1.E.9. If you wish to charge a fee or distribute a Project

Gutenberg™ electronic work or group of works on different
terms than are set forth in this agreement, you must obtain
permission in writing from the Project Gutenberg Literary
Archive Foundation, the manager of the Project Gutenberg™
trademark. Contact the Foundation as set forth in Section 3
below.

1.F.

1.F.1. Project Gutenberg volunteers and employees expend

considerable effort to identify, do copyright research on,
transcribe and proofread works not protected by U.S. copyright
law in creating the Project Gutenberg™ collection. Despite these
efforts, Project Gutenberg™ electronic works, and the medium
on which they may be stored, may contain “Defects,” such as,
but not limited to, incomplete, inaccurate or corrupt data,
transcription errors, a copyright or other intellectual property
infringement, a defective or damaged disk or other medium, a
computer virus, or computer codes that damage or cannot be
read by your equipment.

1.F.2. LIMITED WARRANTY, DISCLAIMER OF DAMAGES - Except

for the “Right of Replacement or Refund” described in
paragraph 1.F.3, the Project Gutenberg Literary Archive
Foundation, the owner of the Project Gutenberg™ trademark,
and any other party distributing a Project Gutenberg™ electronic
work under this agreement, disclaim all liability to you for
damages, costs and expenses, including legal fees. YOU AGREE
THAT YOU HAVE NO REMEDIES FOR NEGLIGENCE, STRICT
LIABILITY, BREACH OF WARRANTY OR BREACH OF CONTRACT
EXCEPT THOSE PROVIDED IN PARAGRAPH 1.F.3. YOU AGREE
THAT THE FOUNDATION, THE TRADEMARK OWNER, AND ANY
DISTRIBUTOR UNDER THIS AGREEMENT WILL NOT BE LIABLE
TO YOU FOR ACTUAL, DIRECT, INDIRECT, CONSEQUENTIAL,
PUNITIVE OR INCIDENTAL DAMAGES EVEN IF YOU GIVE
NOTICE OF THE POSSIBILITY OF SUCH DAMAGE.

1.F.3. LIMITED RIGHT OF REPLACEMENT OR REFUND - If you

discover a defect in this electronic work within 90 days of
receiving it, you can receive a refund of the money (if any) you
paid for it by sending a written explanation to the person you
received the work from. If you received the work on a physical
medium, you must return the medium with your written
explanation. The person or entity that provided you with the
defective work may elect to provide a replacement copy in lieu
of a refund. If you received the work electronically, the person
or entity providing it to you may choose to give you a second
opportunity to receive the work electronically in lieu of a refund.
If the second copy is also defective, you may demand a refund
in writing without further opportunities to fix the problem.

1.F.4. Except for the limited right of replacement or refund set

forth in paragraph 1.F.3, this work is provided to you ‘AS-IS’,
WITH NO OTHER WARRANTIES OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR ANY PURPOSE.

1.F.5. Some states do not allow disclaimers of certain implied

warranties or the exclusion or limitation of certain types of
damages. If any disclaimer or limitation set forth in this
agreement violates the law of the state applicable to this
agreement, the agreement shall be interpreted to make the
maximum disclaimer or limitation permitted by the applicable
state law. The invalidity or unenforceability of any provision of
this agreement shall not void the remaining provisions.

1.F.6. INDEMNITY - You agree to indemnify and hold the

Foundation, the trademark owner, any agent or employee of the
Foundation, anyone providing copies of Project Gutenberg™
electronic works in accordance with this agreement, and any
volunteers associated with the production, promotion and
distribution of Project Gutenberg™ electronic works, harmless
from all liability, costs and expenses, including legal fees, that
arise directly or indirectly from any of the following which you
do or cause to occur: (a) distribution of this or any Project
Gutenberg™ work, (b) alteration, modification, or additions or
deletions to any Project Gutenberg™ work, and (c) any Defect
you cause.

Section 2. Information about the Mission

of Project Gutenberg™
Project Gutenberg™ is synonymous with the free distribution of
electronic works in formats readable by the widest variety of
computers including obsolete, old, middle-aged and new
computers. It exists because of the efforts of hundreds of
volunteers and donations from people in all walks of life.

Volunteers and financial support to provide volunteers with the

assistance they need are critical to reaching Project
Gutenberg™’s goals and ensuring that the Project Gutenberg™
collection will remain freely available for generations to come. In
2001, the Project Gutenberg Literary Archive Foundation was
created to provide a secure and permanent future for Project
Gutenberg™ and future generations. To learn more about the
Project Gutenberg Literary Archive Foundation and how your
efforts and donations can help, see Sections 3 and 4 and the
Foundation information page at www.gutenberg.org.

Section 3. Information about the Project

Gutenberg Literary Archive Foundation
The Project Gutenberg Literary Archive Foundation is a non-
profit 501(c)(3) educational corporation organized under the
laws of the state of Mississippi and granted tax exempt status
by the Internal Revenue Service. The Foundation’s EIN or
federal tax identification number is 64-6221541. Contributions
to the Project Gutenberg Literary Archive Foundation are tax
deductible to the full extent permitted by U.S. federal laws and
your state’s laws.

The Foundation’s business office is located at 809 North 1500

West, Salt Lake City, UT 84116, (801) 596-1887. Email contact
links and up to date contact information can be found at the
Foundation’s website and official page at
www.gutenberg.org/contact
 Section 4. Information about Donations to
the Project Gutenberg Literary Archive
Foundation
Project Gutenberg™ depends upon and cannot survive without
widespread public support and donations to carry out its mission
of increasing the number of public domain and licensed works
that can be freely distributed in machine-readable form
accessible by the widest array of equipment including outdated
equipment. Many small donations ($1 to $5,000) are particularly
important to maintaining tax exempt status with the IRS.

The Foundation is committed to complying with the laws

regulating charities and charitable donations in all 50 states of
the United States. Compliance requirements are not uniform
and it takes a considerable effort, much paperwork and many
fees to meet and keep up with these requirements. We do not
solicit donations in locations where we have not received written
confirmation of compliance. To SEND DONATIONS or determine
the status of compliance for any particular state visit
www.gutenberg.org/donate.

While we cannot and do not solicit contributions from states

where we have not met the solicitation requirements, we know
of no prohibition against accepting unsolicited donations from
donors in such states who approach us with offers to donate.

International donations are gratefully accepted, but we cannot

make any statements concerning tax treatment of donations
received from outside the United States. U.S. laws alone swamp
our small staff.

Please check the Project Gutenberg web pages for current

donation methods and addresses. Donations are accepted in a
number of other ways including checks, online payments and
credit card donations. To donate, please visit:
www.gutenberg.org/donate.

Section 5. General Information About

Project Gutenberg™ electronic works
Professor Michael S. Hart was the originator of the Project
Gutenberg™ concept of a library of electronic works that could
be freely shared with anyone. For forty years, he produced and
distributed Project Gutenberg™ eBooks with only a loose
network of volunteer support.

Project Gutenberg™ eBooks are often created from several

printed editions, all of which are confirmed as not protected by
copyright in the U.S. unless a copyright notice is included. Thus,
we do not necessarily keep eBooks in compliance with any
particular paper edition.

Most people start at our website which has the main PG search
facility: www.gutenberg.org.

This website includes information about Project Gutenberg™,

including how to make donations to the Project Gutenberg
Literary Archive Foundation, how to help produce our new
eBooks, and how to subscribe to our email newsletter to hear
about new eBooks.
Welcome to our website – the ideal destination for book lovers and
knowledge seekers. With a mission to inspire endlessly, we offer a
vast collection of books, ranging from classic literary works to
specialized publications, self-development books, and children's
literature. Each book is a new journey of discovery, expanding
knowledge and enriching the soul of the reade

Our website is not just a platform for buying books, but a bridge
connecting readers to the timeless values of culture and wisdom. With
an elegant, user-friendly interface and an intelligent search system,
we are committed to providing a quick and convenient shopping
experience. Additionally, our special promotions and home delivery
services ensure that you save time and fully enjoy the joy of reading.

Let us accompany you on the journey of exploring knowledge and

personal growth!

ebookname.com