# Fully qualifying classes underneath the vendor directory

**URL:** <https://www.ruby-forum.com/t/fully-qualifying-classes-underneath-the-vendor-directory/94866>\
**Category:** Ruby\
**Created:** [May 16, 2006, 9:48pm UTC](https://www.ruby-forum.com/t/fully-qualifying-classes-underneath-the-vendor-directory/94866 "2006-05-16T21:48:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tbobker](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/73ab20/32.png) [@tbobker](https://www.ruby-forum.com/u/tbobker)\
**Post date:** [May 16, 2006, 9:48pm UTC](https://www.ruby-forum.com/t/fully-qualifying-classes-underneath-the-vendor-directory/94866/1 "2006-05-16T21:48:29Z")

</div>

Java background?

Ruby’s concept of namespaces is different from packages in Java. Also,  
there’s no need that your Node class is defined in a file called  
`node.rb`.

In your example above, you’d need to make sure that (…)/vendor is in  
your $LOAD\_PATH, for example by calling ruby like this:

ruby -I(…)

and then you require the file:

require “html-scanner/html/node”

Assuming that no conflichts exists and `Node` isn’t in fact packed  
into a namespace /module called `HTML-Scanner::HTML` you can now  
access `Node` like you would any other class.

n=Node.new

That what you meant?  
-tim