Because the Java integration is one of the most important parts of JRuby, this chapter
detailed quite a bit of information about this subject. You can turn back to this text when
something is unclear in the example code in the rest of the book. This chapter didn??™t cover all
there is to know about Java integration, but it did cover much of it. You can find more updated
information on the Internet.
Now it??™s time to get started with the next project application, called CoMpoSe.
CHAPTER 6 ?– JAVA INTEGRATION 115
A Rails CMS
In the last chapter we explored the mechanics involved in crossing the border between Java
and Ruby. As you no doubt have learned, there are several tricky things to keep in mind. In this
chapter we??™ll start looking at the first application in the book that uses Java libraries actively,
instead of just relying on JDBC and otherwise doing things the Ruby way.
We??™ll take a look at the basic parts of a content management system, called CoMpoSe.
This system isn??™t a full-fledged Content Management System (CMS). First of all, most help
texts are missing. A few other areas also should be improved before deploying it in production.
However, CoMpoSe will still serve to illustrate how a Rails application that uses Java can work.
Further, it could absolutely form the skeleton for a real CMS application.
The project is divided into two different areas. The one we??™ll mostly explore in this chapter is
the administrative part, where a user can edit the content and metacontent of the system.
Pages:
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206