# Best way to arrange a large lib

**URL:** <https://www.ruby-forum.com/t/best-way-to-arrange-a-large-lib/109017>\
**Category:** Ruby\
**Created:** [July 10, 2007, 5:55pm UTC](https://www.ruby-forum.com/t/best-way-to-arrange-a-large-lib/109017 "2007-07-10T17:55:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![timperrett](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/c5a1d2/32.png) [@timperrett](https://www.ruby-forum.com/u/timperrett)\
**Post date:** [July 10, 2007, 5:55pm UTC](https://www.ruby-forum.com/t/best-way-to-arrange-a-large-lib/109017/1 "2007-07-10T17:55:01Z")

</div>

Hey guys

I have a large(ish) web service that im talking to in several  
applications and thought it would be best to then organise it into a  
re-usable library. I am using wsdl2ruby to generate my class stubs, but  
that means that I have 3 rb files for each service (of which there are  
quite a number)

So my plan of action was to then put everything into neatly ordered  
structure, so I could then just call a nice require ‘path/to/service’ to  
use it? As they will all be grouped into the appropriate modules

Is that a sensible thing to do? If not what would be a good plan of  
action?

Cheers

Tim