Actually I got it working once I removed tiles from the mix but it works well enough for what I need. I may be missing something with tiles but for now it's not that important.
I think I gave it a fair effort to convert to JSF, mainly to get a decent understanding of it to see how it could be useful. If it turned out I converted the entire app in the time I had that would of been fine. While it didn't turn out that way I learned enough about JSF to take my project in the proper direction it needs to go with certainty. Embedding a JSF component <f:view></f:view> in the middle of a jsp page for a specific purpose like I am for the tree component is actually a better solution for my project. I can use bookmarks for looking at specifics objects in my app and for predefined searches and offer browsing with the tree component which gives a more intuitive view to the user. If I find other places where a component offers useful functionality I can add it in as needed. I like the concepts behind JSF. But I think trying to sell it as an all or nothing option is not the way to go. JSF needs to play nice with JSP. Until it does, hopefully, in 1.2 (quite a ways off actually), using a component here and there embedded in a JSP page is going to be the most useful both for the applications and to give components a chance to mature in a variety of live environments. Rob @objectsource.org ----- Original Message ----- From: "Sean Schofield" <[EMAIL PROTECTED]> To: "MyFaces Discussion" <[email protected]> Sent: Monday, May 02, 2005 12:32 PM Subject: Re: struts-faces mailing list > I've actually got the tree showing up correctly on the page, even with call it with > the .do struts naming. I just need to figure out how to get it realize it needs to > deal with the tree when .faces is the extension and struts actions when .do is. I experienced the same significant problem trying to use Tiles, Struts and JSF together. Ultimately I think you can use struts-faces to achieve this but I'd rather spend my time porting the Struts stuff to JSF. Our solution (at my day job) is going to be to convert all of our dialogs over to JSF first. They run in their own modal window and have their own layout. So everything involved in our dialogs will be JSF. The rest will stay as Tiles + Struts. Then the next release we will migrate the rest. This gives us a chance to get familiar with JSF and only have to convert 20% of our pages. Once we finish that phase we will have that learning experience under our belts and can tackle the remainder. I agree its slow going but think about how it took a long time to convert from regular JSP to Struts when Struts first came out. JSF is still improving and more importantly, you and I are still learning JSF. sean > Rob
