Hello,
I'm meeting this problem exactly in the same conditions : jboss, facelets
1.1.11.
Jacob answered Lewie on 2006-02-14 that it would be fixed. Is it and if so, in
which version of facelets ?
Regards,
Dom
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C6319E.6A2013DE"
Date: Tue, 14 Feb 2006 13:39:46 -0600
From: Lewie Gass <Lewi...@virtualmoneyinc.com>
Subject: object is not an instance of declaring class
Jacob,
Thanks for the reply, that would be a great help.
Lewie
________________________________
From: jac...@hookom.net [mailto:jac...@hookom.net]
Sent: Tuesday, February 14, 2006 1:36 PM
To: use...@facelets.dev.java.net; use...@facelets.dev.java.net
Subject: RE: RE: Re: object is not an instance of declaring class
I can actually probably correct this. The first time a MetaTagHandler
gets hit, it captures reflective information to basically build a
'compiled' Tag for future use. I can do a check specifically for that
not-instance-of whatever exception and re-call the MetaRules builder to
with a newly-allocated class instance from the classloader. This should
cause changes to classes to quietly resolve/update within Facelets.
Adam-
I am using Jboss (obviously with Tomcat) ... I understand how Jboss does
class loading but it just seems weird to me
that on the JSP+Faces presentation layer this is not a problem, but due
to the fact that Facelets does reflection on UIComponents
in order to support the arbitrary setting of attributes/properties and
value bindings I think it may be manifesting the problem
that is just not obvious with Faces since it uses Tag classes for
attribute setting.
If I re-deploy the whole app that is where I run into the problem....
once my component library is stable its not a problem since
I deploy it as a separate global jar, and then I can deploy my web app
as many times as I want and have no problems, but as soon
as I redeploy the jar containing the UIComponents I get that error... so
I guess for now developing UIComponent's with Jboss/Facelets
will require a full app restart everytime I fix a bug.... guess its good
that 4.0.4 starts up a lot faster now... hehe
Thanks
Lewie