Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Creating a large ENTITY container???

From: "Chris Lovett" <chris@------.--->
To: NULL
Date: 1/1/2006 6:20:00 PM
Not sure what limitations you have on the client side, but if you are 
running inside a client that supports HTTP Forms, like a web browser, then 
you could post a Form to the server with the XML embedded in one hidden 
<input type="text"> object and the HTML hidden in another <input 
type="text"> object so you can then read them out separately on the server 
side.

"adude28" <adude28@y...> wrote in message 
news:DC96C97F-48D0-4FDC-B7FB-4192E0DE9EB8@m......
> Here is what I have learned from this post.
>
> 1. When you have an <!ENTITY and you are going to use a CDATA section then
> you must choose one type of quote mark internally and use the other to
> enclose the CDATA section.
>

> 2. Inside your CDATA section you can not use "%" or "&" marks otherwise
> things will bomb out.
>
> I followed these two rules and things worked. Unfortunately, now I realize
> that this approach will probably not work because I can forsee times that 
> I
> may need to use a "%" or "&" mark in my code.
>
> I am thinking of using the following format for my <!ENTITY reference
>
> <!ENTITY MessageBodyContent SYSTEM
> 'http://www.url.com/MessageBodyContent.xml'>
>
> that way I don't have to touch the content of my MessageBodyContent.xml 
> and
> I then I can still post just one file to my processing page.
>
> Thank you Chris and Peter. I have learned A LOT with your help. You guys 
> are
> true experts and professionals.
>
> Sincerely,
>
> Ed 




transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent