Gavin,
Yes a good advert for "don't drink and drive" ;) Apology accepted.
As stated in my post, it was only speculation and I was clearly wrong. While my
assumption now appears rather naive (and, yes, I feel suitably embarrassed) please
appreciate that many us on the forum are not yet well versed in the subtleties of AOP and
classloading. In my class cast example I was able to bind to a regular managed bean but
not via a Seam binding "because Seam used a different classloading mechanism to get
the underlying class". Surely this IS quite subtle from a regular Seam programmers
pov? Is this something that could be cleared up in the Seam reference, say introduce a
section from a "Seam and the JEE environment" interaction perspective?
I would have taken the time to acquaint myself with the subtleties of JEE classloading but
having read that documentation you'll know that stuff is not exactly 'light'
reading hence my polite request for direction to the required material. RTFM is often a
fair response but when the 'M' is something as big and vague as the JEE spec then
some direction would be appreciated.
I agree with you that preprender does not work under Seam. I personally DO NOT want to be
dealing with the raw JSF component instances. But let's face it, there will be a lot
of people migrating to Seam from JSC who are used to having exactly that sort of
experience of JSF programming. I only got onto to this because of the way in which the
Trinidad built-in table selections work. Again, maybe something in the Seam reference
could 'educate' people who may be used to other JSF programming models?
Anyway please accept my apologies if I upset you. I really appreciate the help you are
giving myself and others on this forum. I will refrain from speculation from now on and I
will now go away to read up on classloading and try to understand what's going on.
Best Regards,
Chris.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990940#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...