Hi Pranav, Thank you for your interests for AP4R.
On 8/18/08 3:50 PM Pranav Railkar wrote: > > I am facing the following error when I run my application with AP4R > > /usr/lib64/ruby/gems/1.8/gems/uuidtools-1.0.1/lib/uuidtools.rb:105: UUID > is not a class (TypeError) > from > /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in > `gem_original_require' > from > /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in `require' > from > /usr/lib64/ruby/gems/1.8/gems/activesupport-1.4.4/lib/active_support/dependencies.rb:495:in > > `require' > from > /usr/lib64/ruby/gems/1.8/gems/activesupport-1.4.4/lib/active_support/dependencies.rb:342:in > > `new_constants_in' > from > /usr/lib64/ruby/gems/1.8/gems/activesupport-1.4.4/lib/active_support/dependencies.rb:495:in > > `require' > from > /usr/lib64/ruby/gems/1.8/gems/activerdf_rdflite-1.4/lib/activerdf_rdflite/rdflite.rb:8 > I just read some files in rdflite and uuidtools. I found the cause but I don't have workaround yet. Cause: the source of rdflite, so it requires "uuidtools" and "uuidtools" declare the UUID class. On the other hand, AP4R requires "uuid" (through reliable-msg), which declare UUID as a module. Workaround (somewhat RISKY): Declare UUID as a class in uuid.rb. But there are some risks i.e. name collision. I will mail you when I hit on a better workaround. Regards, shino _______________________________________________ ap4r-user mailing list [email protected] http://rubyforge.org/mailman/listinfo/ap4r-user
