Ryan Wynn wrote:
On 8/16/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
On 8/16/06, Joe Shevland
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> [snip]
>
> Cheers
> Joe
The dependency that would be the hardest to try to work around is the
use of
a ServletRequestListener to fire init/destroy events for view
controllers
and related beans. This API did not exist in Servlet 2.3, although it
*might* theoretically be possible ot use a Filter to do some of this
stuff.
This change to servlet 2.4 might be the reason why I could not get
shale 1.0.3 to work inside WebSphere Portal 5.1. My application would
not even start anymore.
Yep, I'm on WAS 5.1 and it would be... WAS 5.1 seems to like swallowing
exceptions in context listeners if thats where you're initializing
things, so sometimes you need to dig down into arcane paths to get the
log files it dumps to (activity.log). I'm using test environments in RAD
(nasty, nasty tool), and it drops them deep in the RAD test env folder
hierarchy.
Is there any way that I can get my application to start up in the
container that supports only 2.3? I realize that I may need to
sacrifice some capabilities of shale.
Two other questions... Does the use of shale-clay require the use of
shale-core? Also could the ViewController functionality be relocated
as a Phase Listener - the reason that I am asking is that portals do
not have the ServletRequest or Filter entry points?
Not sure on these, I'm going to have a crack at the first issue and see
if we can work around the view/controller bit.
Cheers
Joe
