I'm having a difficult time understanding why using DBI is causing a SOAP module to not work. When I use DBI in a module and restart the SOAP server, function calls return nothing but undef results (I'm assuming what's happening is the soap server couldn't dispatch the module). When I comment out the use DBI and all my DBI code in my module and restart the server it works fine. Here's a stripped down example that shows the problem.

Client:

#!/usr/bin/perl
use strict;
use warnings;

use SOAP::Lite;
my $soap = SOAP::Lite->uri('http://localhost/Test')->proxy('http://loc
+alhost:8089/');

print 'Returned: ', $soap->return1()->result(), "\n";
[download]

Soap Server:

#!/usr/bin/perl
use strict;
use warnings;
use SOAP::Transport::HTTP;

SOAP::Transport::HTTP::Daemon
        -> new (LocalPort => 8089, Reuse => 1)
        -> dispatch_to('/opt/scripts/SOAP/lib')
        -> handle;
[download]

Module:

package Test;
use DBI;
sub return1 { return 1; }
1;
[download]

This code works fine when "use DBI;" is commented, returning 1. When uncommented it returns undef.
Any thoughts? I've googled around for SOAP::Transport and DBI issues and have seen some folks with not-so-similar problems but nothing matching my own. I'm new to using SOAP but have successfully implemented scripts that don't use DBI.

EDIT: I should also add that DBI works fine on this box in a non-soap environment. This script works fine with use DBI commented or not in the module.

#!/usr/bin/perl
use strict;
use warnings;
use lib '/opt/scripts/SOAP/lib';
use Test;
print Test::return1(), "\n";
[download]