I would love some patches..  If others have done it, then that would be
great as a learning experience..  I agree, the getRealPath is a bad way to
do things.  So patches plus unit tests would be good.  Part of moving to
Avalon components in 2.4 will be to remove a lot of those as well.

Eric

> -----Original Message-----
> From: Josh and Melody Fuller [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 13, 2003 7:49 PM
> To: [EMAIL PROTECTED]
> Subject: getRealPath Issues
>
>
> There are a few core classes in the Turbine code which use
> "getRealPath" and
> they cause a lot of problems - especialy on any version of
> WebLogic.  I
> noticed the problem first when running Jetspeed1.4 (which
> uses turbine 2.2).
>   I checked to see if Turbine 2.3 fixed the problem - the
> code is almost
> exactly the same - so no fix there.  I have not checked
> Turbine 3.0 yet, but
> the comments in 2.3 say it will be the same in 3.0.
>
> The problem is two parts.  First, when deploying in a war file the
> getRealPath does not work at all in WebLogic - it returns
> null.  Second,
> when deploying as an exploded war instead, other files will
> fail to load.
> The fix seems to be to use getResource instead.  Others have
> modified the
> turbine code to use this, and fixed the problem, but it is
> not part of the
> standard turbine development.
>
> What are the possibilities of having someone in turbine
> development make the
> appropriate changes (i.e. check for nulls, and valid path and use
> getResource instead)?
>
> Thank you,
> Josh Fuller
>
> _________________________________________________________________
> MSN Messenger with backgrounds, emoticons and more.
> http://www.msnmessenger-download.com/tracking/cdp_customize
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to