> Hello Kevin,
>
> Kevin Duffey wrote:
>
> > Hi,
> >
> > >your problem is the setProperty * part .. Orion has yet to support
> > >this. I and a few others have already complained about this. For a quick
> > >fix just put the exact properties that may be called, but it seems to me
> >
Hello Kevin,
Kevin Duffey wrote:
> Hi,
>
> >your problem is the setProperty * part .. Orion has yet to support
> >this. I and a few others have already complained about this. For a quick
> >fix just put the exact properties that may be called, but it seems to me
> >Orion is putting all
Hi,
>your problem is the setProperty * part .. Orion has yet to support
>this. I and a few others have already complained about this. For a quick
>fix just put the exact properties that may be called, but it seems to me
>Orion is putting all their effort into the EJB compatibility, not
your problem is the setProperty * part .. Orion has yet to support
this. I and a few others have already complained about this. For a quick
fix just put the exact properties that may be called, but it seems to me
Orion is putting all their effort into the EJB compatibility, not JSP
prob
Hey all,
I get this weird effect occuring on a JSP page with Orion .9.4. I know it
didn't happen with an earlier version, and it doesn't happen on two other
app servers and IIS/JRUN, so I am hoping that I have found a bug for the
Orion team.
Here is the offending code in my JSP page:
<% if( Log
