You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Bernard Sirius <be...@yahoo.com> on 2005/02/24 19:12:28 UTC
Re: xml generation someone?... (making more progress)
I've put the property in the page specification. That
works. And the XML stuff I've added works too.
Only it's a pitty that I have to put this property all
over the place in each one of my page definitions.
Now, there remains that idiotic thing about putting
the templates inside a folder hierarchy. All the
examples given throw everything under the WEB-INF in
one huge bunch of files.
Has tapestry lost the concept of a folder? ;-)
about that template-extension problem, citing the
documentation:
org.apache.tapestry.template-extension
Overrides the default extension used to locate
templates for pages or components. The default
extension is "html", this configuration property
allows overrides where appropriate. For example, an
application that produces WML may want to override
this to "wml".
This configuration property does not follow the
normal search path rules. The <property> must be
provided in the <page-specification> or
<component-specification>. If no value is found there,
the immediate containing <application> or
<library-specification> is checked. If still not
found, the default is used.
-------------------------------
I've tried putting it in the application spec. When I
first tried it, it threw me an exception, saying it
didn't find the template. When I put the html template
in place, it worked.
Then I've tried validating the app spec (using it's
dtd)... here's what I have obtained:
Referenced entity at
"http://tapestry.sf.net/dtd/Tapestry_1_3.dtd".
Attribute "value" must be declared for element type
"property". [16]
XML validation finished.
-------------------------------
...strange, or is it?
bernard
__________________________________
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: xml generation someone?... (making more progress)
Posted by "matthew c. mead" <m-...@goof.com>.
I'm not sure about the namespacing with respect to URLs and requests - I
don't think you can use a / there, but if you want to organize templates
and page specifications by folder, it's doable. I'm doing the following:
<page name="Catalog.Page1" specification-path="Catalog/Page1.page"/>
<page name="Catalog.Page2" specification-path="Catalog/Page2.page"/>
<page name="Catalog.Page3" specification-path="Catalog/Page3.page"/>
<page name="Catalog.Page4" specification-path="Catalog/Page4.page"/>
<page name="Catalog.Page5" specification-path="Catalog/Page5.page"/>
Thus, my .page and template files for the catalog are in
WEB-INF/Catalog. However, when I want to refer to these pages and
activate them with code, I use a period for the "file separator" like
so: getPage("Catalog.Page1");
-matt
Bernard Sirius wrote:
>I've put the property in the page specification. That
>works. And the XML stuff I've added works too.
>
>Only it's a pitty that I have to put this property all
>over the place in each one of my page definitions.
>
>Now, there remains that idiotic thing about putting
>the templates inside a folder hierarchy. All the
>examples given throw everything under the WEB-INF in
>one huge bunch of files.
>
>Has tapestry lost the concept of a folder? ;-)
>
>about that template-extension problem, citing the
>documentation:
>
>org.apache.tapestry.template-extension
>
> Overrides the default extension used to locate
>templates for pages or components. The default
>extension is "html", this configuration property
>allows overrides where appropriate. For example, an
>application that produces WML may want to override
>this to "wml".
>
> This configuration property does not follow the
>normal search path rules. The <property> must be
>provided in the <page-specification> or
><component-specification>. If no value is found there,
>the immediate containing <application> or
><library-specification> is checked. If still not
>found, the default is used.
>
>-------------------------------
>
>I've tried putting it in the application spec. When I
>first tried it, it threw me an exception, saying it
>didn't find the template. When I put the html template
>in place, it worked.
>
>Then I've tried validating the app spec (using it's
>dtd)... here's what I have obtained:
>
>Referenced entity at
>"http://tapestry.sf.net/dtd/Tapestry_1_3.dtd".
>Attribute "value" must be declared for element type
>"property". [16]
>XML validation finished.
>-------------------------------
>
>...strange, or is it?
>
>bernard
>
>
>
>__________________________________
>Do you Yahoo!?
>Yahoo! Mail - Find what you need with new enhanced search.
>http://info.mail.yahoo.com/mail_250
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
--
matthew c. mead
http://www.goof.com/