Thanks for the reply Ken. I know what was happening now with regard to
the design time jars. I had included all the jars for Woodstock's lib
directory in my app including webui-jsf-dt.jar. So when the Page class
was loaded I saw:
javax.servlet.ServletException: Cant instantiate class: com.sun.webui.jsf.component.Page.
javax.faces.webapp.FacesServlet.service(FacesServlet.java:277)
and the telling root cause:
java.lang.NoClassDefFoundError: com/sun/rave/designtime/faces/FacetDescriptor
com.sun.webui.jsf.component.PageBeanInfoBase.getFacetDescriptors(PageBeanInfoBase.java:108)
com.sun.webui.jsf.component.PageBeanInfoBase.getBeanDescriptor(PageBeanInfoBase.java:45)
com.sun.webui.jsf.component.PageBeanInfo.getBeanDescriptor(PageBeanInfo.java:31)
java.beans.Introspector.getTargetBeanDescriptor(Introspector.java:1228)
java.beans.Introspector.getBeanInfo(Introspector.java:386)
java.beans.Introspector.getBeanInfo(Introspector.java:159)
javax.faces.component.UIComponentBase.getPropertyDescriptors(UIComponentBase.java:174)
javax.faces.component.UIComponentBase.populateDescriptorsMapIfNecessary(UIComponentBase.java:139)
javax.faces.component.UIComponentBase.<init>(UIComponentBase.java:128)
com.sun.webui.jsf.component.Page.<init>(Page.java:44)
...
The PageBeanInfo class was being loaded from webui-jsf-dt.jar by the
Introspector which introduced the dependency. Removing webui-jsf-dt.jar
from my app solved the problem.
-Kenneth
Ken Paulsen wrote:
> FWIW, we do not use any of the design-time files w/ Woodstock in our
> GlassFish admin console application. We haven't upgraded to the
> latest Woodstock release, but unless something has changed, these
> files are for design-time only and have never been required.
>
> Good luck!
>
> Ken
>
> Kenneth Suter wrote:
>> Hello,
>>
>> I have not been able to find Woodstock version specific dependency
>> information. I have seen the document DeployingWoodstock on the Wiki
>> which seems like it would be useful but the dependency table is not
>> version specific, contains lots of question marks, and seems to
>> differ from my own experience (see next paragraph). I am currently
>> using the components outside of NetBeans and have had some trouble
>> with external library version incompatibility. For instance I was
>> attempting to use Woodstock 4.1 with the JSF Extensions RC5 which did
>> not work because the path the the .js files had changed. It would be
>> really nice to have this sort of information in the release notes or
>> at least on the wiki or java.net site.
>>
>> Also I am curious about the note on the note on the 'Build the
>> Source' page which states that "Netbeans is not required to use the
>> components...". In my simple application running in Tomcat 6, basic
>> components like page, body and button do not render unless I include
>> designtime.jar, editors.jar, and jsfcl.jar all of which I obtained
>> from the NetBeans visualweb plugin. Is this expected?
>>
>> Thanks,
>>
>> -Kenneth
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
>> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>