|
Hi there,
I'm exploring the feasibility of using Tapestry to
develop WAP applications (as well as possibly other non-HTML browser-based
applications).
As I understand it one of the major benefits of
Tapestry is the way it cleanly seperates the Java development and web design
specialties by using standard HTML pages, with some augmented by
transparent HTML elements and attributes, as its templating
mechanism. This allows web designers to work with standard HTML
development tools and to be able to preview and browse a static web of template
files (with sample content). Correct?
I was wondering how this can be extended to WML, or
other XML-based markup languages for that matter (like VoiceXML, XHTML, etc.),
which must be well-formed, and even valid (depending on the tools/viewers
used).
Would it be possible to develop (or better yet has
anyone written and contributed) "filter" components which strip out the Tapestry
special tags and make the links active so that the templates could be made
previewable/browsable? I guess this filters could also be developed
outside Tapestry itself (if appropriate), possibly as Servlet 2.3
filters.
Also, under the quotes section of the Tapestry
site, I notice that someone (by the name of David Solis) is using it to develop
WAP applications. He mentions that he "extended it [Tapestry] for WAP
support". I was wondering what specifically was involved. He seemed
to also be able to preserve "clean separation of content and developer
code". I was wondering how that was acheived with WML.
Any info and insights on these specific questions
and on WML (or XML-based markup) development with Tapestry in general would be
greatly appreciated.
Regards,
Sasha Haghani,
Toronto, Canada
|
