Brendan,
Happy you've found your problem.
Using local with Inline modules is definitely tricky because there is
definitely a lot
going on behind the scenes.
Cheers,
Pat
----- Original Message -----
From: "Brendan W. McAdams" <[EMAIL PROTECTED]>
To: "Brendan W. McAdams" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, May 04, 2002 8:47 PM
Subject: Re: Mod_Perl + Inline::Java woes continue
> OK, I think I've nailed it down.
>
> I am localizing $/ in order to slurp a template file from Apache::File...
>
> It seems like if the inline code is placed AFTER this local $/ my issues
> begin.
>
> After some testing with moving the code up and down, it appears to be
this.
>
>
> ----- Original Message -----
> From: "Brendan W. McAdams" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, 04 May, 2002 19:16
> Subject: Mod_Perl + Inline::Java woes continue
>
>
> > Well, I'm digging through the code now; haven't heard back from Patrick
> yet
> > (last time i had a problem, he worked it out with me).
> >
> > It seems like mod_perl is missing the return message from Java that it
> > created the object.
> >
> > Code runs from command line and if the code I'm running is in same
> package,
> > etc as my handler - but it also seems to fail on abstraction.
> >
> > I haven't done alot of work with IO::Socket but if anyone has
suggestions
> on
> > getting more of a debug, or a way to do better insurance of getting
return
> > packets, i'd appreciate it.
> >
> > "Offending" piece of code, where the message is being lost, appears to
be:
> > if ($this->{socket}){
> > my $sock = $this->{socket} ;
> > print $sock $data . "\n" or
> > croak "Can't send packet to JVM: $!" ;
> >
> > $resp = <$sock> ;
> > if (! $resp){
> > croak "Can't receive packet from JVM: $!" ;
> > }
> >
> > # Release the reference since the object has been sent back
> > # to Java.
> > $Inline::Java::Callback::OBJECT_HOOK = undef ;
> > }
> >
> > .... somewhere in here a return message is going away.
> >
> > Any suggestions?
> >
> >
> >
>
>
