A guy named Dan Jacobs, who runs the local ACM charter and organizes monthly meetings (basically, a hard-driven, bright guy, and a local leader type) was asked, at a session about Struts + Tiles (a month after I gave my Tapestry presentation), "what criteria would you use to decide whether to use Struts+Tiles or to use Tapestry". His response: "no criteria, I'd just use Tapestry.".
Dan was the guy who pointed out (obvious in retrospect) one of the benefits of Tapestry; that each Tapestry file is just one language (HTML, XML or Java ... not mixed together). Just an example to support my opinion of him; that he's on the ball. But, as you can see, I got the juices flowing and I have a skeleton of a Tapestry/JSP bridge in my head. ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 03, 2002 2:02 PM Subject: Re: [Tapestry-developer] struts > > Where did you see the JSF spec? I couldn't find one last time I looked. > > This is conveniently what I was thinking about anyway....the "advanced" > components go in between a custom tag that hooks in the engine and > component tree. > > I think if we could "fake" the request cycle within those tags we'd be > there. I am OK with having to manually map/deal with names of objects to > some extent to get the attributes back out of the request (similar to how > struts form bean works). > > As for the debate, there really wasn't one. To be honest, the more I > thought about it, the more it made sense to go the JSP route. It is so much > more readily accepted and understood. Now, what I want is to tell the JSP > folks, "just drop these tags on the page and play be these rules and you > get components on your pages"...we'll probably also use Tiles to get some > "inheritence" of pages...still need to do some research. > > I have a lot more to think about than the presentation layer, so I may not > get all my ideas down for a bit. > > -C > > > > > hlship@attbi. > com To: Christian Hall/Technology/Equifax@Equifax > cc: > 09/03/2002 Subject: Re: [Tapestry-developer] struts > 11:52 AM > > > > > > What was the debate like, internally? Did you have > Tapestry results to show on one hand, vs. Struts on the > other? > > Perhaps we should set you up a new branch to start > playing with JSP/Tapestry interop. > > Some brainstorming ... > > If you notice, on a JSF page, you have to put your faces > components inside a <faces:usefaces> tag. > > I suspect that JSF does a "fake render" that is used to > figure out which components are present on a page, and > how they wrap around each other ... in the same way that > Tapestry parses an HTML template. > > Perhaps we could change Tapestry to parse JSP files as > well as HTML templates? If we forbid Java code, and > create a Tapestry component that can delegate to a JSP > taglib ... > > I think the right thing is to still have a page > specification for the JSP, just not have a template. > Trying to do all the configuration of a component from > the JSP is so limited. > > -- > [EMAIL PROTECTED] > > http://tapestry.sf.net > > Recently, our company decided to standardize on using Struts. I think > this > > is a reality in many companies. The hard fact is that the best technology > > does not always survive. > > > > As I have time over the next month or so, I am going to try to figure out > > what parts of the Tapestry framework could be "hooked in" to Struts/JSP. > I > > think there are many essentials of Tapestry that could be decoupled from > > the guts to allow for: > > > > - a way to embed Tapestry components in JSP pages > > - a way to reuse some of the guts of Tapestry in a JSP (e.g. Struts) > > application > > > > I understand the internals of Tapestry well having built a production > > application with it. Some hard work needs to go into making JSP (and > > eventually JSF) play well with Tapestry. Otherwise, I can see that it > will > > become like many other great technologies and be a niche player. > > > > As soon as I have any concrete thoughts as to how to move forward, I'll > > share them. I just thought I'd remind everyone that this issue is going > to > > be a driver. Get familiar with Struts. Most enterprise tools deal with > JSPs > > (and even generate them) and everyone's API/toolkit includes custom tags > > for integration. It's fundamental to Java Web GUIs whether we like it or > > not. I tried to go the strict Tapestry route and now I can see that it is > > not a long-term option for leveraging other technologies or developers. > > > > I had unsubscribed to this list as soon as I was told that Struts was my > > future here : )...but I think there is some middle ground to be found. My > > goal is component development in the JSP environment (as much as is > > feasible), and hopefully some opportunity to reuse a subset of "JSP > > compatible" Tapestry components in the future. > > > > -Christian > > > > > > > > Protect yourself against identity theft with Equifax Credit Watch. Visit > > http://www.creditalert.equifax.com. > > > > This message contains information from Equifax Inc. which may be > > confidential and privileged. If you are not an intended recipient, > please > > refrain from any disclosure, copying, distribution or use of this > > information and note that such actions are prohibited. If you have > > received this transmission in error, please notify by e-mail > > [EMAIL PROTECTED] > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by: OSDN - Tired of that same old > > cell phone? Get a new here for FREE! > > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > > _______________________________________________ > > Tapestry-developer mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/tapestry-developer > > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
