You are completely true Simon. A problem in the release build made the faces-config.xml not to be included in the myfaces-all.jar. Another option if you want to use the myfaces-all.jar is to download a recent nightly, as those are not affected by this issue,
Regards, Bruno 2005/9/22, Simon Kitching <[EMAIL PROTECTED]>: > Christian wrote: > > Like you I just switched form 1.0.9 to 1.1.0. > > > > I deleted all myfaces-jars and replaced them with "myfaces-all.jar" of > > 1.1.0, updated the tld-references and cleaned my build-directory. > > > [snip] > > > > I got this error > > Undefined component type org.apache.myfaces.HtmlColumn > > It might be because the tld point to > > <tag-class>org.apache.myfaces.custom.column.HtmlColumnTag</tag-class> > > It is a different class. > > > > Then I put tomahawk.jar in my lib directory. Although this action seems > > to be redundant, as myfaces-all.jar seems to contain all required > > classes and the problem is solved. In fact, i cannot see where the > > org.apache.myfaces.HTMLColum comes from. > > The tomahawk.jar file contains a file META-INF/faces-config.xml which > declares all the tomahawk JSF components. > > The myfaces-all.jar file contains the tomahawk classes, but due to a > build problem doesn't contain the faces-config.xml file necessary to > tell the myfaces framework that the classes exist. Until this is fixed > it is necessary to use the standalone tomahawk jar (or possibly to add > the missing META-INF/faces-config.xml file into the classpath). > > Disclaimer: I'm pretty new to myfaces. This is just info I picked up > from watching this list. > > Regards, > > Simon >
