I haven't run tree2 on the RI and from what you are describing it sounds like there may be a problem.
My gut instinct tells me that there is a problem with the RI because AFAIK there is no spec requirement that a commandLink be inside of a form. Of course I haven't read the spec that carefully ;-) Can you help me to investigate this? Check the spec to see if this is a requirement. Also check sun's JSF forum and see if there have been posts already regarding this and if there is a consensus that this is a bug or not. That would help out big time. I can look into it but I am a bit swamped at the moment. Just came back from 2 weeks out of country and now I'm dealing with reorganizing the entire SVN repository for MyFaces. sean On 6/21/05, CONNER, BRENDAN (SBCSI) <[EMAIL PROTECTED]> wrote: > Hmm. That's what I thought also, although I've tried to get it to work > with just myfaces-extensions.jar and the Sun RI, with no luck. I've > only gotten it to work if I use the entire myfaces.jar (and not the Sun > implementation). > > I modified the example jsp somewhat, because it uses a non-standard > borders="0" argument in the <h:graphicImage> tag, and I put an <h:form> > tag to be able to test the page by itself, but, even though all the code > is now surrounded by <h:form>...</h:form>, the main problem seems to be > that I get the following message: > > [6/21/05 15:21:30:543 CDT] 79d4fe94 CommandLinkRe E > com.sun.faces.renderkit.html_basic.CommandLinkRenderer component _id107 > must be enclosed inside a form > > - Brendan > > -----Original Message----- > From: Sean Schofield [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 21, 2005 3:12 PM > To: MyFaces Discussion > Subject: Re: Using Tree2 with WebSphere 5.1 > > > Use myfaces-extensions.jar (see the binary release and/or nightly > build.) Its designed to run with RI or any other implementation. > Whichever impl you use it should be JSF 1.1 - nobody has tested tree2 > with JSF 1.0 so who knows if that works or not. > > sean > > On 6/21/05, CONNER, BRENDAN (SBCSI) <[EMAIL PROTECTED]> wrote: > > Thanks, Sean. > > > > Given that, is there an easy way to obtain the minimal set of classes > > needed from the MyFaces distribution to get just the Tree2 component's > > capability (without laboriously loading one class after another to see > > which dependencies are still broken)? Ideally, I'd like to crisply > take > > just the Tree2 component (and any of the other MyFaces classes on > which > > it depends) and plop it into my server environment. At this point, I > > would like to avoid using the MyFaces JSF implementation, if possible, > > but I would be interested in using the Tree2 component. > > > > Thanks, > > > > - Brendan > > > > -----Original Message----- > > From: Sean Schofield [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, June 21, 2005 2:49 PM > > To: MyFaces Discussion > > Subject: Re: Using Tree2 with WebSphere 5.1 > > > > > > You should be able to use whatever version of JSF you want. I don't > > use WS but you can probably tinker with the server libraries and > > replace them with whatever version you want. > > > > sean > > > > On 6/7/05, CONNER, BRENDAN (SBCSI) <[EMAIL PROTECTED]> wrote: > > > Has anyone gotten Tree2 to work with WebSphere 5.1? I realize that > > > WebSphere is only JSF 1.0 compatible, but I didn't see anything in > the > > > code that required JSF 1.1. However, when trying to run the > example, > > I > > > got an Error 500: Assertion Failed at the following location in > > > HtmlTreeRenderer: > > > > > > private void encodeRecursive(FacesContext context, UIComponent > > > component) throws IOException > > > { > > > /[EMAIL PROTECTED] consider moving this common functionality to a > > > base > > > class or utility class */ > > > if (!component.isRendered()) return; > > > > > > component.encodeBegin(context); > > > > > > - Brendan > > > > > >
