[OT] Doctypes

Hola a todos, ¿¿ alguien sabe las diferencias entre
los siguientes doc types
y en que afectan a la pagina web dependiendo lo que se ponga
?? ó en su
defecto donde encontrar información acerca de esto ??
Tipo de documento :
Ninguna
HTML 4.01 transición
HTML 4.01 estricto
XHTML 1.0 transición
XHTML 1.0 estricto
XHTML 1.1
XHTML Mobile
Gracias,
Lui7

Depende, si quieres mas accesibilidad el estricto sino el
otro.
"Luisete" <[email protected]> escribió en el mensaje
news:fgaf9v$53r$[email protected]..
> Cual me recomiendas usar Lucas???? Es mejor transitional
no??? para
> mayores temas visuales y todo eso...
>
>
> "Lucas Sevilla" <[email protected]>
escribió en el mensaje
> news:fgaeil$421$[email protected]..
>> Los transicionales incluyen todos los elementos y
cualidades de HTML 4
>> Strict pero agrega cualidades presentational,
elementos desaprobados o
>> elementos obsoletos. Se llaman Transitional porque
está pensado como
>> transición hacia HTML 4 estricto, el que cumple
todos los estándares.
>>
>> --
>> Saludos
>> www.lucassevilla.info
>> www.gestproyect.info
>>
>> "Luisete" <[email protected]> escribió en
el mensaje
>> news:fga7o1$obe$[email protected]..
>>>
>>> Hola a todos, ¿¿ alguien sabe las
diferencias entre los siguientes doc
>>> types y en que afectan a la pagina web
dependiendo lo que se ponga ?? ó
>>> en su defecto donde encontrar información
acerca de esto ??
>>>
>>> Tipo de documento :
>>> Ninguna
>>> HTML 4.01 transición
>>> HTML 4.01 estricto
>>> XHTML 1.0 transición
>>> XHTML 1.0 estricto
>>> XHTML 1.1
>>> XHTML Mobile
>>>
>>> Gracias,
>>> Lui7
>>>
>>>
>>
>>
>
>

Similar Messages

How to set up 2 agreements for the same From,To,DocType,Version in B2B11g

Hi
I am having an issue in configuring more than one agreement for the same DocType, Version, From and To partner in Oracle B2B11g.
When I click "Valid" button on the second agreement it errors out saying duplicate agreement is found for the same DocType, Version, From and TO partners.
Is there any mechanism to over ride this?
We need to have multiple agreements created for the same To Partner, From Partner, Doc Type and Version. Otherwise we will end up creating multiple partners which is a real pain.
Multiple agreements are required because we have to set up different Interchange and Group IDs for each transaction.
-Sriharish.
Edited by: 840696 on Mar 1, 2011 7:30 AM

You can not have two agreements for same From TP,To TP,DocType & DocType revision combination in B2B 11g.
Multiple agreements are required because we have to set up different Interchange and Group IDs for each transactionIs this requirement for outbound or inbound? You may send Internal Properties from back-end to override envelope parameters in Oracle B2B in case of outbound -
B2B 11G Outbound EDI Envelope Override
http://www.b2bgurus.com/2008/09/internal-properties-in-oracle-b2b.html (this blog is for 10g, so read concept only, not settings)
In case of Inbound, TP identification can be done on the basis of exchange, interchage, group. So if any of this can be same then you may have single agreement. Make sure to enable property "Functional Ack Internal Properties" on B2B console (Administration --> Configuration)-
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10229/bb_config.htm#CEGEADFJ
Regards,
Anuj

Invalid logging line: !DOCTYPE html PUBLIC "-//W3C//DTD XHTM error

Hi..
I am getting the following error while deploying a bpel process cantaining java embedding on weblogic server 11g.
[04:31:54 PM] Received HTTP response from the server, response code=200
[04:31:54 PM] Invalid logging line: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
[04:31:54 PM] Invalid logging line: <html xmlns="http://www.w3.org/1999/xhtml">
[04:31:54 PM] Invalid logging line: <head>
[04:31:54 PM] Invalid logging line: <title>GE | Web Site Verification</title>
[04:31:54 PM] Invalid logging line: <style type="text/css">
[04:31:54 PM] Invalid logging line: 
[04:31:54 PM] Invalid logging line: </style>
[04:31:54 PM] Invalid logging line: <script>
[04:31:54 PM] Invalid logging line: function show_lang(section) {
[04:31:54 PM] Invalid logging line:      document.getElementById('excerpt_EN').style.display = "none";
[04:31:54 PM] Invalid logging line:
[04:31:54 PM] Invalid logging line: document.getElementById('excerpt_SCN').style.display = "none";
[04:31:54 PM] Invalid logging line:      document.getElementById('excerpt_FR').style.display = "none";
[04:31:54 PM] Invalid logging line:
[04:31:54 PM] Invalid logging line: document.getElementById('excerpt_ES').style.display = "none";
[04:31:54 PM] Invalid logging line:      document.getElementById('excerpt_DE').style.display = "none";
[04:31:54 PM] Invalid logging line:
[04:31:54 PM] Invalid logging line: document.getElementById('excerpt_IT').style.display = "none";
[04:31:54 PM] Invalid logging line:      document.getElementById('excerpt_JP').style.display = "none";
[04:31:54 PM] Invalid logging line:
[04:31:54 PM] Invalid logging line: document.getElementById('footer_EN').style.display = "none";
[04:31:54 PM] Invalid logging line:      document.getElementById('footer_SCN').style.display = "none";
[04:31:54 PM] Invalid logging line:
[04:31:54 PM] Invalid logging line: document.getElementById('footer_FR').style.display = "none";
[04:31:54 PM] Invalid logging line:      document.getElementById('footer_ES').style.display = "none";
[04:31:54 PM] Invalid logging line:
[04:31:54 PM] Invalid logging line: document.getElementById('footer_DE').style.display = "none";
[04:31:54 PM] Invalid logging line:      document.getElementById('footer_IT').style.display = "none";
[04:31:54 PM] Invalid logging line:
[04:31:54 PM] Invalid logging line: document.getElementById('footer_JP').style.display = "none";
[04:31:54 PM] Invalid logging line:      var excerpt = "excerpt_" + section;
[04:31:54 PM] Invalid logging line:      var footer="footer_"+
[04:31:54 PM] Invalid logging line: section;
[04:31:54 PM] Invalid logging line:      document.getElementById(excerpt).style.display = "block";
[04:31:54 PM] Invalid logging line:      document.getElementById(footer).style.display
[04:31:54 PM] Invalid logging line: = "block";
[04:31:54 PM] Invalid logging line: }
[04:31:54 PM] Invalid logging line: function show(section) {
[04:31:54 PM] Invalid logging line:      var excerpt = "excerpt_" + section;
[04:31:54 PM] Invalid logging line:      var full_text = "full_" + section;
[04:31:54 PM] Invalid logging line:
[04:31:54 PM] Invalid logging line: document.getElementById(excerpt).style.display = "none";
[04:31:54 PM] Invalid logging line:      document.getElementById(full_text).style.display = "block";
[04:31:54 PM] Invalid logging line: }
[04:31:54 PM] Invalid logging line:
[04:31:54 PM] Invalid logging line: function hide(section) {
[04:31:54 PM] Invalid logging line:      var excerpt = "excerpt_" + section;
[04:31:54 PM] Invalid logging line:      var full_text = "full_" + section;
[04:31:54 PM] Invalid logging line:
[04:31:54 PM] Invalid logging line: document.getElementById(full_text).style.display = "none";
[04:31:54 PM] Invalid logging line:      document.getElementById(excerpt).style.display = "block";
[04:31:54 PM] Invalid logging line: }
[04:31:54 PM] Invalid logging line:
[04:31:54 PM] Invalid logging line:
[04:31:54 PM] Invalid logging line: /** BEGIN SCRIPS FOR REMEMBER SSO IMPLEMENTATION **/
[04:31:54 PM] Invalid logging line: function rememberSSOID(){
[04:31:54 PM] Invalid logging line:
[04:31:54 PM] Invalid logging line:      if (document.SSOForm.saveID.checked){
[04:31:54 PM] Invalid logging line:           saveSSOID();
[04:31:54 PM] Invalid logging line:      } else {
[04:31:54 PM] Invalid logging line:           clearSSOID();
[souhaitez continuer sur ce site.
[04:31:54 PM] Invalid logging line:
[04:31:54 PM] Invalid logging line: Pour en savoir plus
[04:31:54 PM] Invalid logging line: sur le processus de protection de l'accès Internet GE, consultez les informations ci-dessous.</p>
[04:31:54 PM] Invalid logging line:      <p id="excerpt_ES"
[04:31:54 PM] Invalid logging line: style="display:none">La página a la que intenta acceder no es un sitio web de confianza de GE. Para protegerlo a usted y
[04:31:54 PM] Invalid logging line: a la Compañía, por favor, seguidamente inicie sesión para confirmar que desea continuar en este sitio. Para
[04:31:54 PM] Invalid logging line: obtener más datos respecto de la protección al acceso a Internet de GE, consulte la información que aparece
[04:31:54 PM] Invalid logging line: debajo.</p>
[04:31:54 PM] Invalid logging line:      <p id="excerpt_JP"
[04:31:54 PM] Invalid logging line: style="display:none">アクセスしようとして
[04:31:54 PM] Invalid logging line: いるサイトはGEが信賴していな
[04:31:54 PM] Invalid logging line: いウェブサイトです。自身と
[04:31:54 PM] Invalid logging line: 会社を守るため、下記にログ
[04:31:54 PM] Invalid logging line: インしてこのサイトを続けて
[04:31:54 PM] Invalid logging line: 閲覧することを確認してくだ
[04:31:54 PM] Invalid logging line: さい。 GE のインターネットアクセス保
[04:31:54 PM] Invalid logging line: 護プロセスについての詳細は
[04:31:54 PM] Invalid logging line: 、下記を参照してください。
[04:31:54 PM] Invalid logging line: </p>
[04:31:54 PM] Invalid logging line:      <p id="excerpt_DE" style="display:none">Die Website,
[04:31:54 PM] Invalid logging line:           <li>
[04:31:54 PM] Invalid logging line:
[04:31:54 PM] Invalid logging line:      </ul>
[04:31:54 PM] Invalid logging line: </div>
[04:31:54 PM] Invalid logging line: <div id="footer_JP" style="display:none">
[04:31:54 PM] Invalid logging line: <p><img
[04:31:54 PM] Invalid logging line: src="https://www.ge.com/security_proxy_sign_on/more-information.png"></p>
[04:31:54 PM] Invalid logging line:      <ul>
[04:31:54 PM] Invalid logging line:           <li>
[04:31:54 PM] Invalid logging line:
[04:31:54 PM] Invalid logging line: <div id="excerpt_one_JP"><a href="javascript:show('one_JP')
[04:31:54 PM] Invalid logging line: name="why_title">このページにアクセスする理由</a></div>
[04:31:54 PM] Invalid logging line:                     <div id="full_one_JP" style="display:none;">
[04:31:54 PM] Invalid logging line:                          <p><a
[04:31:54 PM] Invalid logging line: href="javascript:hide('one_JP')"
[04:31:54 PM] Invalid logging line: name="why_title">このページにアクセスする理由</a></p>
[04:31:54 PM] Invalid logging line:                          <p
[04:31:54 PM] Invalid logging line: class="why_desc">GE の企業情報を保護することは
[04:31:54 PM] Invalid logging line: 最優先事項です。
[04:31:54 PM] Invalid logging line: この情報は、物理的、電子的、手
[04:31:54 PM] Invalid logging line: 続き上のセーフガード（この認証
[04:31:54 PM] Invalid logging line: ページ等）により保護されます。
[04:31:54 PM] Invalid logging line: このページは、アクセスしている
[[04:31:54 PM] ---- Deployment finished. ----

Hi:
R u behind a Proxy?
If it so, u can configure it at JDEveloper in the Tools->Preferences->Web Browser and Proxy section.
Or u can deploy ur composite, directly in Enterprise Manager - Fusion Middleware Control.
thx
best

Creation of XML !DOCTYPE DTD Validation line

Hello all!
I've been working in the creation of an XML File via Abap Objects.
<b>if_ixml</b> For Document Header
<b>if_ixml_document</b> For Document Header
<b>if_ixml_element</b> For Nodes and their Child Nodes
I have already developed the code for creating the XML File.
I think I have it completed, but I don't know how to insert the line that starts with <!DOCTYPE>.
This line validates all the DOM tree structure against a DTD File.
I've been searching for an example of how to do it, but I dind't find anything
Wich is the proper Class, object or method that I have to implement for this topic?
The Line I have to post on the XML file is one like this:
<!DOCTYPE e-billing-payable PUBLIC "-//BxxxxFxxxxx.com//DTD Ebilling Enterprise to Bank 1.0//EN" "https://hb.xxx.com.ar/cobranzasonline/ebillingE2B.dtd">
Thanks in advance,
Claudio.

Thanks Sandra, I was succesfull in getting the doc type but here is the format that I need
<!DOCTYPE gsafeed PUBLIC "-//Google//DTD GSA Feeds//EN" "gsafeed.dtd">
If I try to use entity declaration , it dosen't let me without passing the SYSTEM paramater. Is there any method within if_ixml_document_type or outside, that would help me pass the attributes to get in the below format.
<!DOCTYPE rootElement PUBLIC "PublicIdentifier" "URIreference">
Thanks
Ganesh.S

Archivelink - Document Class * - All docs stored with text/x-docType mime

Hi,
I have configured an archivelink document type (OAC2) to use document class *, ie it can accept any file and not restricted to a particular type. Document is being stored on archive server with a mime type of text/x-docType and therefore when you try retrieve it, SAP GUI isnt able to determine the mime type and only offers the 'Save As' dialog box, ie doesnt open in the SAP Viewer.
I have previously used this * configuration on another clients system and it works correctly, the file is stored with the correct mime type and therefore is retrieved correctly.
Any ideas why using the * config is forcing the mime type to text/x-docType?
Thanks,
Mark

Hi Mark
Transaction SPRO - SAP Reference IMG - SAP Netweaver - Application Server - Basis Services - ArchiveLink - Basic Customizing - Edit Document Classes
The very first entry will be * and the MIME type is by default text/x-docType.

Add Doctype to the XML File

Experts,
My Scenario is JDBC to File
For the resultant xml file i have to include a <DOCTYPE> after
<?xml version="1.0" encoding="UTF-8" ?> while passing it to legacy system ?
I had written an XSLT Code to acheive this, i checked in XML spy and it is working.
but in moni iam getting an error in message mapping
my XSLT Code is
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:output method="xml" indent="no" doctype-system="http://integratex.quality.techdata.de:8080/ix/dtd/ixOrder.dtd"/>

<xsl:template match="node() | @*">
            <ns0:MT_ASNDATAOUT xmlns:ns0="http://aaaaa/sd/SD152.25">
            <xsl:copy>
                                                <xsl:apply-templates select="node() | @*"/>
            </xsl:copy>
            </ns0:MT_ASNDATAOUT>
</xsl:template>
</xsl:stylesheet>
and the error in moni is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">GENERIC</SAP:Code>
<SAP:P1>Parsing error after multi mapping.</SAP:P1>
<SAP:P2>Expected Message<i> instead of Messages</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Parsing error after multi mapping.Expected Message<i> instead of Messages</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Iam doing multi mapping between source and target, is m ulti mapping causing the issue?
and also check my xslt code,it is working in xml spy as desired.
Please help me on this
Appreciate your help.
Thanks
Srinivas

Hi,
Yes you have to chnage the DTD structure to add DOCTYPE Value,one morething when you executing XSLT mapping Multi Mapping scenario it shouls also supports multi mapping feature.Fisrt execute XSLT Mapping program without multi mapping,let me know how its behaving.
Regards,
Raj

Removing HTTP header field DOCTYPE in inbound HTTP

Hello,
For an inbound HTTP message we need to remove the !DOCTYPE tag from the message since XI message mapping cannot handle it.
We had a similar issue with outbound http where we used an xslt mapping to include the DOCTYPE.
I think it should be possible to also remove the doctype with xslt, in fact I have an xslt that works in xmlspy on the inbound http message, but after deploying in XI the mapping step fails.
The xslt is small but working:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
<xsl:template match="/">
<xsl:copy-of select="." />
</xsl:template>
</xsl:stylesheet>
When I test the interface mapping it gives a transformer exception.
When i test the finished product I see the following in the monitor:
com/sap/xi/tf/_IF021_Ordrsp_TD_to_Ordrsp_CCS_com.sap.aii.utilxi.misc.api.BaseRuntimeExceptionFailed to load resource from the context classloa~
Since mapping works in external tools I'm not sure what the problem is for XI and how to solve it.
Another solution for this would seem to be a java mapping although i have no clue as to how to do this.
How to proceed?
Thanks
Tom

update:
The solution lies in note 812966 which describes the problem above, and also gives an example java mapping program as example to get rid the DOCTYPE.
Regards
Tom

DOCTYPE and xslt mapping

Hi All,
I have an XSLT mapping. I have only now found out that I need to include a
<i><!DOCTYPE Order SYSTEM "XCBL3.0.dtd"></i> tag on the second line of the xml I am sending via HTTP. This causes the XSLT mapping to fail in XI. From reading other threads, I understand there is a limitation on the XI xslt parser with "DOCTYPE" tags.
I have tried a workaround by invoking a custom java program in my xslt mapping to insert the doctype but this gets sent out via HTTP as:
<!DOCTYPE Order SYSTEM "XCBL3.0.dtd">
Is there any other workaround I could do without having to completely rewrite my mapping into a Java mapping as mentioned in another thread?
Please Help!!

In your xslt mapping place the following line before the top level element is written
<xsl:text disable-output-escaping="yes"><!DOCTYPE Order SYSTEM "XCBL3.0.dtd"></xsl:text>
Regds Doug.

Add and Remove DOCTYPE from cXML

Hi,
I'm currently using Message mapping from cXML to idoc and vice versa. I need a remove the DOCTYPE declaration on the inbound cXML and add DOCTYPE for outbound. I understand, it is possible to have a JAVA mapping or XSLT to resolve this problem, since i'm not expert in Java. Can someone send me a Java code which could help me resolve this issue. Any ideas or help is greatly appreciated.
Thanks!.

Hi Ganesh,
i think most easy would be ABAP:
Do not parse the message, just call a fm to convert to string:
DATA:
* xml message
    l_message TYPE string.
*create a string to search (and replace) in it
CALL FUNCTION 'ECATT_CONV_XSTRING_TO_STRING'
    EXPORTING
      im_xstring = source
      im_encoding = 'UTF-8'
    IMPORTING
      ex_string   = l_message.
Then use the right string operation for example REPLACE:
REPLACE FIRST OCCURRENCES OF
    '<!DOCTYPE...'
IN
    l_message
WITH
Finally switch back to XString:
* create a XString: Ready, no use of DOM!
CALL FUNCTION 'ECATT_CONV_STRING_TO_XSTRING'
    EXPORTING
      im_string   = l_message
      im_encoding = 'UTF-8'
    IMPORTING
      ex_xstring = result.
Regards,
Udo

Named file entity do not load in from xml files(eg., !DOCTYPE PURANA SYSTEM "purana.dtd" [ !ENTITY CHAPTER_1 SYSTEM "./chapter_1.xml" ] ?xml-stylesheet type="text/xsl" href="purana.xsl"? PURANA TITLE /TITLE &CHAPTER_1; /PURANA )

I create several file name entities in an external DTD.
It used to work sometimes back but I don't remember now when it begun to fail.
typical document for eg., is given below:
<!DOCTYPE PURANA SYSTEM "purana.dtd" [ <!ENTITY CHAPTER_1 SYSTEM "./chapter_1.xml"> ]>
<?xml-stylesheet type="text/xsl" href="purana.xsl"?> <PURANA>
<TITLE>
</TITLE>
&CHAPTER_1;
</PURANA>)
the abbreviation used to work by loading the file using XSL script,
but now it does not even work when the entity is defined within the XML document itself.

Too difficult???
Please helped me.
Thank you, Theo

How to add DOCTYPE in XML using jaxp-1.2 ????

Hi all,
I know this question has been asked at least 2000 times. But I couldn't find the answer from the previously posted messages.
I would like to create a new Document (actually a XML document) and to write it out into a file. Of course, to be useful, that document needs a DTD... But I can't find a way to create that DOCTYPE tag.
In fact, I get this error: org.apache.crimson.tree.DomEx: HIERARCHY_REQUEST_ERR: This node isn't allowed there.
       at org.apache.crimson.tree.XmlDocument.appendChild(XmlDocument.java:661)
       at ServiceManager.PlaylistDOM.createDoc(PlaylistDOM.java:99)
       at ServiceManager.PlaylistDOM.load(PlaylistDOM.java:52)
       at java.lang.Thread.run(Thread.java:536)The code I have is the following:
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
try {
    //create a factory and configure it
    DocumentBuilder builder = factory.newDocumentBuilder();
    playlistDoc = builder.newDocument();
    DOMImplementation impl = builder.getDOMImplementation();
    DocumentType doctype = impl.createDocumentType(ROOT_EL, null, "playlist.dtd");
    playlistDoc = impl.createDocument(null, ROOT_EL, doctype);
catch (ParserConfigurationException pce) {}
//create the root of the XML file
Element root = (Element) playlistDoc.createElement(ROOT_EL);
root.setAttribute(FRAME_ATTR, fNb);
playlistDoc.appendChild(root);
//now print it out into XML file
TransformerFactory tfactory = TransformerFactory.newInstance();
try {
    Transformer transformer = tfactory.newTransformer();
    DOMSource source = new DOMSource(playlistDoc.getDocumentElement());
    StreamResult res = new StreamResult(new File(filename));
    transformer.transform(source, res);
catch (TransformerConfigurationException tce) {}
catch (TransformerException te) {}Thank you for your help

add both SYSTEM and PUBLIC, then you will find PUBLIC :P
================
If the doctype-public or doctype-system attributes are specified, then the html output method should output a document type declaration immediately before the first element. The name following <!DOCTYPE should be HTML or html. If the doctype-public attribute is specified, then the output method should output PUBLIC followed by the specified public identifier; if the doctype-system attribute is also specified, it should also output the specified system identifier following the public identifier. If the doctype-system attribute is specified but the doctype-public attribute is not specified, then the output method should output SYSTEM followed by the specified system identifier.
reference: http://java.sun.com/j2se/1.4.1/docs/api/javax/xml/transform/OutputKeys.html

Java mapping for Remove and Add of DOCTYPE Tag

HI All,
i have one issue while the Java mapping for Remove and Add of DOCTYPE Tag in Operation Mapping .
it says that , while am testing in Configuration Test " Problem while determining receivers using interface mapping: Error while determining root tag of XML"
Receiver Determination...
error in SXMB MOni
" SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem while determining receivers using interface mapping: Error while determining root tag of XML: '<!--' or '<![CDATA[' expected</SAP:P1>
plz provide solutions
Thanks in advance.

Hi Mahesh,
I understand, you are using extended Receiver Determination using Operational Mapping (which has Java Mapping). And, there is an error message u201CError while determining root tag of XMLu201D, when you are doing configuration test.
Can you please test, the Operational Mapping (which has Java Mapping) separately in ESR, with payload which is coming now. It should produce a XML something like this [Link1|http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce53aea0d7154ee10000000a421937/frameset.htm]
<Receivers>
<Receiver>
<Party agency="016" scheme="DUNS">123456789</Party>
<Service>MyService</Service>
</Receiver>
<Receiver>
<Party agency="http://sap.com/xi/XI" scheme="XIParty"></Party>
<Service>ABC_200</Service>
</Receiver>
</Receivers>
If it is not (I Think it will not), then there is some problem in Java Mapping coding. Please correct it. Last option, if your Java code is small in length; you may paste it here, so that we can have a look at the cause of issue.
Regards,
Raghu_Vamsee

RH 7 project upgraded to RH 9 does not show the doctype as XHTML

I’m using Robohelp version 9.0.2.271 and I successfully upgraded a project in Robohelp 9 from Robohelp 7. However, in the source at the top of the files, the doctype shows as HTML instead of XHTML as follows:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
My co-worker who is using the same version of RH 9 upgraded this same project and her doctype shows as XHTML as follows:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
Shouldn’t the source show XHTML when using RH 9? And, if so, shouldn’t this have automatically converted when I upgraded the project from RH 7? Is there a setting or something I need to change to show this?
I’ve tried uninstalling and reinstalling RH 9 several times and reconverted the project, as well, in case there was some problem with the install or the conversion, and have not had any success. I have also applied the 9.0.2 update after running the installation. Thanks for your help.

William,
Yes, that solved the problem. Thank you so much. I had no idea about that option. I kept thinking something was wrong with the install or my conversion. Thanks again.
Cathy

Adding !Doctype at top of page in login page of portal

Hi Experts,
I need guidance on how we can put <!doctype> tag on top of page ie before <HTML> tag.
I have a requirement to build custom logon screens which i have build but when i put it in sap , it opens in Quirks mode in IE9 .
I have seen that when i changed its mode to standard mode 9 then it looks perfect, also it works properly in Chrome and mozilla browsers,
I have refer some SCN links which says to create java api to add <!doctype> , if we can follow the same then let me know it step by step as i am not that good in java.
Kindly guide me ASAP .

Hi Amit,
This is not supported currently. See my answer in Re: doctype tag for external facing portal logon application (NWP 7.3) and also the referred SAP-Note.
@Andrew: The question was about the login page, and this has not yet a portal desktop!
Anyhow, even if Dani Cohens explanation made sense at that point in time, meanwhile http://service.sap.com/sap/support/notes/1713259 could be a good reason to change this. I would suggest to open an OSS message and ask for clarification, as with note 1713259 there is the possibility that also a HTML5 login page could be rendered successfully within a HTML5 portal.
It should be the responsibility of the customer (and this can be stretched in the note about the HTML5 support for the login page) that if he uses an HTML5 login page for the portal that in this case the portal itself should be completely HTML5, too, as otherwise a login page within the portal might lead to issues.
Hope it helps
Detlev

How do you make Xerces parser generate doctype to XML-file?

When I use javacode (with xerces parser) to update an XML-file the doctype-line disappears!!!!
Anyone how knows how to solve this problem????
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE test SYSTEM "StatisticStandard.dtd"> <---- This is the line I want to keep!!!
<test>
<totalanswered>5</totalanswered>
<set>
<alt>1</alt>
</set>
</test>

Hi!
I found a sort of solution to my problem. I don't think it is the best, but it works!
Where you write to file you add this line (look for the arrow).
(I use the javax.xml.transform package)
Source xmlSource = new DOMSource(document);
Result result = new StreamResult(
new FileOutputStream(path+file));
TransformerFactory transformerFactory = TransformerFactory.newInstance();
Transformer transformer = transformerFactory.newTransformer();
transformer.setOutputProperty(javax.xml.transform.OutputKeys.DOCTYPE_SYSTEM, "dtdfilename.dtd"); <-- This one does the trick!!!
transformer.transform(xmlSource, result);
Anette :)

XSLT/JAVA Mapping for cXML DOCTYPE

Hello -
Was anyone successful in adding the header
<!DOCTYPE cXML SYSTEM "http://xml.cXML.org/schemas/cXML/1.2.014/cXML.dtd">
after the
<?xml version="1.0" encoding="UTF-8"?> when converting
using either XSL or JAVA?
If there's way let me know what kind of mapping was used and how?
Thanks,
Tirumal

Hi Tirumal,
you can solve that with xsl:output
one example:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
     <xsl:output method="xml" doctype-system="http://xml.cXML.org/schemas/cXML/1.2.014/cXML.dtd"/>
     <xsl:template match="/">
          <xsl:copy-of select="*"/>
     </xsl:template>
</xsl:stylesheet>
Regards,
Udo

[OT] Doctypes

Similar Messages

Maybe you are looking for