Re: Render Template as XML instead of HTML

2008-11-20 Thread Howard Lewis Ship
This should now work with the 5.0.17-SNAPSHOT. Unfortunately, we aren't building nightly snapshots for 5.0 anymore, just for 5.1 (and this fix is not in 5.1 yet). You may have to download Tapestry and build from source. On Wed, Nov 19, 2008 at 11:58 AM, Mark W. Shead <[EMAIL PROTECTED]> wrote: >

Re: Render Template as XML instead of HTML

2008-11-19 Thread Mark W. Shead
That makes sense. I did a test. tml of: java of: public class TestXML { } produces: The root element of the rendered document was , not . A root element of is needed when linking JavaScript and stylesheet resources. I'll add that to the issue. Thanks! Mark On Nov 19, 2008, at

Re: Render Template as XML instead of HTML

2008-11-19 Thread Howard Lewis Ship
https://issues.apache.org/jira/browse/TAP5-370 Will be fixed in 5.0.17. Looks like we'll need a new release shortly. On Wed, Nov 19, 2008 at 9:02 AM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > There must be something on the new page that generates some > JavaScript. Some component with an

Re: Render Template as XML instead of HTML

2008-11-19 Thread Howard Lewis Ship
There must be something on the new page that generates some JavaScript. Some component with an @InlcudeJavaScriptLibrary annotation, or similar. Hm. Thinking about this, it may be a bug. I think Tapestry is trying to inject the default stylesheet into your document. It should only try to do tha

Re: Render Template as XML instead of HTML

2008-11-19 Thread Mark W. Shead
The page that I want to render as XML doesn't have a form, but the preceding page does. So PageWithFrom gathers information and then when it is submitted, returns PageWithoutForm (the page that is trying to generate xml). I thought the cycle would be something along the lines of: PageWith

Re: Render Template as XML instead of HTML

2008-11-18 Thread Howard Lewis Ship
You likely have a Form component in your page, and it's generating JavaScript to handle client-side validation. Please search the list archive (at markmail.org), we were just discussing this issue. On Tue, Nov 18, 2008 at 2:40 PM, Mark W. Shead <[EMAIL PROTECTED]> wrote: > I tried that as well an

Re: Render Template as XML instead of HTML

2008-11-18 Thread Mark W. Shead
I tried that as well and got: The root element of the rendered document was , not . A root element of is needed when linking JavaScript and stylesheet resources. I'm not trying to render any javascript or stylesheets--at least not on purpose. In my .java file I have: @Meta("tapestry.re

Re: Render Template as XML instead of HTML

2008-11-18 Thread Howard Lewis Ship
is intended for components that need to render more than one "root" element. Try: - http://www.netledger.com/xml/dtd/smb_4_11.dtd";> http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";> ...snip... On Tue, Nov 18, 2008 at 7:59 AM, Mark W. Shead <[EMAIL PROTECTED]> wrote: > I have a

Render Template as XML instead of HTML

2008-11-18 Thread Mark W. Shead
I have a page that needs to render as xml. I see that there was a patch applied to do this, but I can't seem to bring in the tapestry name space in order to get loop components, etc. to work. Does anyone have an example showing how this should work? https://issues.apache.org/jira/browse/TAPESTRY