ha! <listener> that's how it works :) That explains the issue w/ Jetty. Sean and me were wondering about that Tiger thing :)
thx craig! On 10/23/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
On 10/23/06, Sean Schofield <[EMAIL PROTECTED]> wrote: > > Craig, > > In the docs you mention you just need the shale-tiger.jar in your > webapp for things to work properly. I discovered that annotations are > not available when using the Jetty plugin and I'm trying to figure out > why. Can you clue me in as to the mechanism that is responsible for > discovering your annotations? I know there is a parser in the tiger > package but i can't figure out where that's being called from. Hmm ... there are at least the following prerequisites for this to work: * The shale-view-xxx.jar file contains a tag library that, among other things, includes a <listener> declaration that sets up the basics and (if the Tiger extensions are also in the webapp) does the Tiger-specific stuff. Do you have this JAR in your webapp? If not, and you try adding it, does that make things work? (If this does the trick, then the problem is a result of the recent split-out of the view functionality ... we'll have to come up with an alternative approach that doesn't require shale-view). * Does your JSF implementation (either MyFaces or the RI) initialize correctly without needing an explicit declaration in web.xml? This matters, because both implementations presume that the servlet container will do the spec-compliant thing of recognizing listeners declared in tag libraries. IIRC, this was a problem for older versions of Jetty, but I thought it had been addressed in later versions. TIA, > > Sean > Craig
-- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
