That makes sense.  I did a test.

tml of:
<?xml version="1.0" encoding="UTF-8" ?>
<xml>
</xml>

java of:

public class TestXML {

}

produces:

The root element of the rendered document was <xml>, not <html>. A root element of <html> is needed when linking JavaScript and stylesheet resources.


I'll add that to the issue.

Thanks!

Mark

On Nov 19, 2008, at 11:02 AM, Howard Lewis Ship wrote:

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 that if the root tag is the <html> tag.

The discussion concerned how to override Tapestry to add the
JS-related markup to a different tag.

On Wed, Nov 19, 2008 at 8:37 AM, Mark W. Shead <[EMAIL PROTECTED]> wrote:
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:
PageWithForm submits to itself and then returns PageWithoutForm so the
Javascript stuff should only be present on the first page.

I searched for the following terms on Mark Mail, but couldn't find anything
that seemed to address this:

xml form
javascript xml
xml form javascript
root element html needed

I did find some suggestions to just create the xml and stream it back to the client. My goal here is to use the template capabilities of T5 unless this
isn't possible.

If anyone has any other suggestions or can point me toward a previous
discussion regarding this I'd appreciate it.

Mark



On Nov 18, 2008, at 5:05 PM, Howard Lewis Ship wrote:

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 and got:
The root element of the rendered document was <smbxml>, not <html>. A
root
element of <html> 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.response-content-type=text/xml")
public class EventXML {

To try to tell it to use xml instead of html for the content type.

Is there a setting I'm missing somewhere?

Thanks for your help.

Mark

On Nov 18, 2008, at 11:07 AM, Howard Lewis Ship wrote:

<t:container> is intended for components that need to render more than
one "root" element.  Try:
-
<?xml version="1.0" encoding="UTF-8" ?>

<!DOCTYPE smbxml SYSTEM "http://www.netledger.com/xml/dtd/smb_4_11.dtd ">

<smbxml xmlns:t="http://tapestry.apache.org/schema/tapestry_5_0_0.xsd ">

<t:loop source="sequenceList" value="aSequence">

...snip...

</t:loop>

</smbxml>

On Tue, Nov 18, 2008 at 7:59 AM, Mark W. Shead <[EMAIL PROTECTED]>
wrote:

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-1600 being fixed seems to indicate that this should be possible, but I'm not seeing exactly
how to implement it.

Mark

More info:
Here is my xml template file:

<?xml version="1.0" encoding="UTF-8" ?>

<!DOCTYPE smbxml SYSTEM
"http://www.netledger.com/xml/dtd/smb_4_11.dtd";>

<t:container
xmlns:t="http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>

<smbxml>

<t:loop source="sequenceList" value="aSequence">

...snip...

</t:loop>

</smbxml>

</t:container>

This doesn't work because it expects an html tag. I'm guessing that might be something that is coming from the t:container tag. I've tried a bunch of other ways of getting the tapestry namespace in, but they either don't work or it complains about not having an HTML element.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






--
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to