XHTML Generated by JBO tags does not validate

I was wondering if anyone has run into this issue, and if so, what they have done about it....
Our organisation standards state that our web pages must validate to the XHTML V1.0 STRICT standards.
But if I use the JBO tags, such as InputRender, etc, the fact that many of the fields are created in upper case means that the validation fails.
As an example, my JBO tag is
<td title="<jbo:ShowHint hintname='TOOLTIP'></jbo:ShowHint>"><jbo:InputRender datasource="dsource" formname="<%=formName%>" /></td>
and the output HTML is
<td title=""><TEXTAREA ROWS="5" MAXLENGTH="256" NAME="Description" CLASS="clsDescription" COLS="70"></TEXTAREA>
<INPUT VALUE TYPE="HIDDEN" NAME="_Description">
</td>
Note that the parameter names are all uppercase (and not found by the validator), and that the <INPUT> tag is not terminated (it requires a / before the closing >).
Is there a workaround for this? Where does JBO get the text it uses for the replacment tags?
thanks for any assistance with this....
Brigette

Could you show us an example of the cflayout code?

Similar Messages

ERROR: "info.plist does not validate against DTD"

Hi! I got this error if anyone has it solved Please HELP.
I am trying to package a WRT widget using Nokia WRT extension for Adobe Dreamweaver. This is the place for info on the extension: http://www.forum.nokia.com/Tools_Docs_and_Code/Tools/Runtimes/Web_Runtime/
I figure developer from here who use DW to develop mobile content might know the error.
When come to the step of 'Package Nokia WRT Widget' I got this error: info.plist does not validate against DTD
and a page of error info shown like this:
DTD validated at: Wed Jun 17 2009 19:03:00 GMT+0800 (Malay Peninsula Standard Time)
DTD used for validation: http://www.nokia.com/DTDs/plist-1.0.dtd
Line
Column
Message
Explanation
Source
2
95
DTD did not contain element declaration for document type name
3
16
Attribute "version" exists, but can not be used for this element.
3
21
element "plist" undefined. Did you mean "applet" or "strike"?
4
7
element "dict" undefined. Did you mean "strike" or "input"?
5
7
element "key" undefined. Did you mean "strike" or "blockquote"?
6
10
element "string" undefined. Did you mean "strong" or "strike"?
7
7
element "key" undefined. Did you mean "strike" or "blockquote"?
8
10
element "string" undefined. Did you mean "strong" or "strike"?
9
7
element "key" undefined. Did you mean "strike" or "blockquote"?
10
10
element "string" undefined. Did you mean "strong" or "strike"?
11
7
element "key" undefined. Did you mean "strike" or "blockquote"?
12
10
element "string" undefined. Did you mean "strong" or "strike"?
13
7
element "key" undefined. Did you mean "strike" or "blockquote"?
14
9
element "true" undefined. Did you mean "textarea" or "tr"?
Can anyone knows what this means and how i can solve it?
Please help. Thankyou.
note: I am new here and knows that keep asking quesion without giving back is not good but I have a deadline here and wanted to finish the job. I will read some other post and try to help in return when I am able to do so.

Hi pziecina,
Thanks for your reply,
I suspect my problem is the installation or setup of my system or software. as the result i tested is not by doing any scripting at all. All I did is following one of their example exactly (http://www.forum.nokia.com/Tools_Docs_and_Code/Tools/Runtimes/Web_Runtime/Dreamweaver_Exte nsion/QuickStart.xhtml) and package strightaway without modifying the code. because I want to make sure i got the extension install correctly. even so by packaging one of their ready make example already yield this error.

Encountering error End tag does not match start tag 'group'

Hi guys,
am a newbee to XML Publisher.
I am encountering the below error:
Creating XDO Report at: Wed May 25 16:38:14 GMT+05:30 2011
     sql = select 'TEST' from dual;
     description = Learning XML Reporting
     port = 1561
     user = apps
     host = e2dscorhrmdba01.cendant.com
     sid = ABGHRDEV
     ReportParameters = {}
     path = D:\lanosrep\XML\Output\FirstXMLReport
     data_source_name = ABGHRDEV
     name = FirstXMLReport
oracle.xml.parser.v2.XMLParseException: End tag does not match start tag 'group'.
     at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:205)
     at oracle.xml.parser.v2.XMLReader.popXMLReader(XMLReader.java:516)
     at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1242)
     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:227)
     at oracle.apps.xdo.dataengine.DataProcessor.getSQLSchema(DataProcessor.java:528)
     at oracle.apps.xdo.dataengine.DataProcessor.writeXMLSchema(DataProcessor.java:476)
     at CreateXDOReport.createXDOReport(CreateXDOReport.java:164)
     at CreateXDOReport.process(CreateXDOReport.java:108)
     at CreateXDOReport.main(CreateXDOReport.java:298)
I have tried reinstalling the patch but of no use.
Please guide me.

I changed the sql query
select 'TEST' from dual;
to select 'TEST' from dual
It is working fine now :)

SQL CASE statement in XML template- End tag does not match start tag 'group

Hi All,
I am developing a report that has the SQL CASE statement in the query. I am trying to load this into RTF with report wizard and it gives me below error
oracle.xml.parser.v2.XMLParseException: End tag does not match start tag 'group'
Does XML publisher support CASE statement?
My query is something like this
SELECT customercode,
SUM(CASE WHEN invoicedate >= current date - 30 days
THEN balanceforward ELSE 0 END) AS "0-30",
SUM(CASE WHEN invoicedate BETWEEN current date - 60 days
AND current date - 31 days
THEN balanceforward ELSE 0 END) AS "31-60",
SUM(CASE WHEN invoicedate < current date - 60 days
THEN balanceforward ELSE 0 END) AS "61>",
SUM(balanceforward) AS total_outstanding
FROM MyTable
GROUP BY customercode
ORDER BY total_outstanding DESC
Please advice if the CASE statement or the double quotes are causing this error
Thanks,
PP

I got this to work in the XML but the data is returning zeros for all the case statements. When I run this in toad I get results for all the case conditions but when ran in XML the data displayed is all zeros. I am not sure what I am missing. Can someone shed some light on this please
Thanks!
PP

Task.toXML() creates xml that does not validate against WorklistTask.xsd

I am using the worklist API and I am using the toXML() function provided in the Task object to serialize my Task info to XML. It produces XML that looks alot like a "task" Element. But, it does not validate against the WorkflowTask.xsd schema. What is even more odd is that XML looks different than the xml I see when I look at the data in the BPEL Console.
For example, the first XML document below is from Task.toXML. notice that it's first child element is taskId. According to the xsd, that is not valid. The second xml document in this post is from the console. it appears to be valid.
Am I doing something wrong or should I just not expect the worklist api to produce valid xml? (correction: should I not expect the worklist api to xml that validates?)
<task xmlns="http://xmlns.oracle.com/pcbpel/taskservice/task"><taskId>0D7B97F1B138EE21E04017AC2B194357</taskId><title>Payment not posted by payee</title><isGroup>true</isGroup><acquiredBy/><owner>bpeladmin</owner><conclusion/><state>ASSIGNED</state><subState>ASSIGNED</subState><processId>ResearchRequestWorkflow</processId><processName>ResearchRequestWorkflow</processName><versionNumber>1</versionNumber><notm>1</notm><taskGroupId/><taskType>http://blade-11.payveris.com:9700/orabpel/default/ResearchRequestWorkflow/1.0/taskConfigResearchRequest.xml</taskType><identificationKey>PAULA MERRILL, 2069</identificationKey><priority>3</priority><creator>bpeladmin</creator><creationDate>2006-02-23T14:53:08.000-05:00</creationDate><updatedBy>bpeladmin</updatedBy><modifyDate>2006-02-23T14:53:08.000-05:00</modifyDate><flexString1>1140724383057</flexString1><flexString2>PAULA MERRILL</flexString2><flexString3>PAULA MERRILL</flexString3><flexString4>PaymentId3489</flexString4><flexLong1>0</flexLong1><flexLong2>0</flexLong2><flexDouble1>0.0</flexDouble1><flexDouble2>0.0</flexDouble2><processVersion>1.0</processVersion><instanceId>2304</instanceId><domainId>default</domainId><approvers/><hasSubTasks>false</hasSubTasks><processOwner>bpeladmin</processOwner><pattern>SINGLE_APPROVAL</pattern><taskNumber>10240</taskNumber><systemString1/><systemString2/><systemString3/><versionReason>Task Created</versionReason><assigneeGroups>ResearchManager</assigneeGroups><payload confirmation_number="1140724383057" due_date="2006-02-22-05:00" reason="Payment not posted by payee"><requester xmlns="http://www.pp.com/schema"><first>PAULA MERRILL</first><last>PAULA MERRILL</last><tax_id/></requester><payment_type xmlns="http://www.pp.com/schema" number="">insuranceauto</payment_type><record_info xmlns="http://www.pp.com/schema"><creation app="EU" by="282950" date="2006-02-23T14:53:03.056-05:00"/><updation app="EU" by="282950" date="2006-02-23T14:53:03.056-05:00"/></record_info><payment xmlns="http://www.pp.com/schema" id="3489"><bank_info bank_id="2" funds_model="RISK"/><payment_info><confirmation_number>5428</confirmation_number><amount formattedValue="77.00" value="77"/><payment_date>2006-01-06-05:00</payment_date><check_number>5851</check_number><funded>false</funded><merged>false</merged><network id="3" status="ACTIVE" type="C">MOORE</network><alert_on_completion>false</alert_on_completion><alert_number_days_before>0</alert_number_days_before><scheduled_info id="2278"><scheduled_for_date formatted="01/06/2006">2006-01-06-05:00</scheduled_for_date><scheduled_on_date formatted="01/06/2006">2006-01-06-05:00</scheduled_on_date><created_user_id>282950</created_user_id><updated_user_id>0</updated_user_id></scheduled_info></payment_info><payee_info id="24958" relationship_id="6004"><payee_account_number>JUNIT123</payee_account_number><nick_name>blahblah</nick_name><name>complexpayeenameforatest</name><address1>123 main street</address1><address2>c/o anybody</address2><city>Dark Cityrandomizer</city><state>CT</state><zip>06512</zip><network id="3" status="ACTIVE" type="C">MOORE</network></payee_info><customer_info id="2069"><name>PAULA MERRILL</name><customer_account_id>8</customer_account_id><customer_account_number>213</customer_account_number><customer_routing_number>111111111</customer_routing_number><address1>Ernest Hemingway Drive</address1><city>Springfield</city><state>IL</state><zip>62703</zip></customer_info><state_info><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>958</network_batch_id><state_date>2006-10-24-05:00</state_date><state formatted="Check Cashed by Payee" id="2">Cleared</state><trace_number>211170100000003</trace_number></state_info><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>0</money_batch_id><good_funds_batch_id>0</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="6">Created</state><record_info><creation app="BPEL" by="0" date="2006-01-06T11:14:33-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>0</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="6">Created</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T11:14:35-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>0</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="22">Waiting for Decision</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T11:14:36-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="12">Ready for Funding</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:40:01-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="9">Funded</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:40:01-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>0</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>0</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="12">Ready for Funding</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:40:03-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>958</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="In Process" id="9">Funded</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:43:56-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>958</network_batch_id><state_date>2006-01-06-05:00</state_date><state formatted="Mailed" id="11">Payment Sent</state><trace_number>211170100000003</trace_number><record_info><creation app="BPEL" by="0" date="2006-01-06T12:43:59-05:00"/></record_info></state_history><state_history><failed_reason_code>0</failed_reason_code><money_batch_id>824</money_batch_id><good_funds_batch_id>1817</good_funds_batch_id><network_batch_id>958</network_batch_id><state_date>2006-10-24-05:00</state_date><state formatted="Check Cashed by Payee" id="2">Cleared</state><trace_number>211170100000003</trace_number><record_info><creation app="EU" by="9999999" date="2006-02-03T12:38:08-05:00"/></record_info></state_history><record_info><creation app="BPEL" by="0" date="2006-01-06T11:14:33-05:00"/><updation app="EU" by="9999999" date="2006-02-03T12:38:08-05:00"/></record_info><research_request>false</research_request></payment></payload></task>
When Im look at the same task in the BPELConsole, the task looks like:
<task>
<title>Payment not posted by payee</title>
<assigneeUsers/>
<assigneeGroups>ResearchManager</assigneeGroups>
<acquiredBy/>
<owner>bpeladmin</owner>
<payload confirmation_number="1140724383057" due_date="2006-02-22-05:00" reason="Payment not posted by payee" >
<requester>
<first>PAULA MERRILL</first>
<last>PAULA MERRILL</last>
<tax_id/>
</requester>
<payment_type number="" >insuranceauto</payment_type>
<record_info>
<creation app="EU" by="282950" date="2006-02-23T14:53:03.056-05:00" />
<updation app="EU" by="282950" date="2006-02-23T14:53:03.056-05:00" />
</record_info>
<payment id="3489" >
<bank_info bank_id="2" funds_model="RISK" />
<payment_info>
<confirmation_number>5428</confirmation_number>
<amount formattedValue="77.00" value="77" />
<payment_date>2006-01-06-05:00</payment_date>
<check_number>5851</check_number>
<funded>false</funded>
<merged>false</merged>
<network id="3" status="ACTIVE" type="C" >MOORE</network>
<alert_on_completion>false</alert_on_completion>
<alert_number_days_before>0</alert_number_days_before>
<scheduled_info id="2278" >
<scheduled_for_date formatted="01/06/2006" >2006-01-06-05:00</scheduled_for_date>
<scheduled_on_date formatted="01/06/2006" >2006-01-06-05:00</scheduled_on_date>
<created_user_id>282950</created_user_id>
<updated_user_id>0</updated_user_id>
</scheduled_info>
</payment_info>
<payee_info id="24958" relationship_id="6004" >
<payee_account_number>JUNIT123</payee_account_number>
<nick_name>blahblah</nick_name>
<name>complexpayeenameforatest</name>
<address1>123 main street</address1>
<address2>c/o anybody</address2>
<city>Dark Cityrandomizer</city>
<state>CT</state>
<zip>06512</zip>
<network id="3" status="ACTIVE" type="C" >MOORE</network>
</payee_info>
<customer_info id="2069" >
<name>PAULA MERRILL</name>
<customer_account_id>8</customer_account_id>
<customer_account_number>213</customer_account_number>
<customer_routing_number>111111111</customer_routing_number>
<address1>Ernest Hemingway Drive</address1>
<city>Springfield</city>
<state>IL</state>
<zip>62703</zip>
</customer_info>
<state_info>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>958</network_batch_id>
<state_date>2006-10-24-05:00</state_date>
<state formatted="Check Cashed by Payee" id="2" >Cleared</state>
<trace_number>211170100000003</trace_number>
</state_info>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>0</money_batch_id>
<good_funds_batch_id>0</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="6" >Created</state>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T11:14:33-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>0</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="6" >Created</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T11:14:35-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>0</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="22" >Waiting for Decision</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T11:14:36-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="12" >Ready for Funding</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:40:01-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="9" >Funded</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:40:01-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>0</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>0</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="12" >Ready for Funding</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:40:03-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>958</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="In Process" id="9" >Funded</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:43:56-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>958</network_batch_id>
<state_date>2006-01-06-05:00</state_date>
<state formatted="Mailed" id="11" >Payment Sent</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T12:43:59-05:00" />
</record_info>
</state_history>
<state_history>
<failed_reason_code>0</failed_reason_code>
<money_batch_id>824</money_batch_id>
<good_funds_batch_id>1817</good_funds_batch_id>
<network_batch_id>958</network_batch_id>
<state_date>2006-10-24-05:00</state_date>
<state formatted="Check Cashed by Payee" id="2" >Cleared</state>
<trace_number>211170100000003</trace_number>
<record_info>
<creation app="EU" by="9999999" date="2006-02-03T12:38:08-05:00" />
</record_info>
</state_history>
<record_info>
<creation app="BPEL" by="0" date="2006-01-06T11:14:33-05:00" />
<updation app="EU" by="9999999" date="2006-02-03T12:38:08-05:00" />
</record_info>
<research_request>false</research_request>
</payment>
</payload>
<conclusion/>
<state>ASSIGNED</state>
<subState>ASSIGNED</subState>
<processId>ResearchRequestWorkflow</processId>
<processName>ResearchRequestWorkflow</processName>
<processVersion>1.0</processVersion>
<instanceId>2304</instanceId>
<domainId>default</domainId>
<processOwner>bpeladmin</processOwner>
<taskId>0D7B97F1B138EE21E04017AC2B194357</taskId>
<versionReason>Task Created</versionReason>
<taskGroupId/>
<taskType>http://blade-11.payveris.com:9700/orabpel/default/ResearchRequestWorkflow/1.0/taskConfigResearchRequest.xml</taskType>
<identificationKey>PAULA MERRILL, 2069</identificationKey>
<comments/>
<priority>3</priority>
<creator>bpeladmin</creator>
<updatedBy>bpeladmin</updatedBy>
<hasSubTasks>false</hasSubTasks>
<approvers/>
<pattern>SINGLE_APPROVAL</pattern>
<flexString1>1140724383057</flexString1>
<flexString2>PAULA MERRILL</flexString2>
<flexString3>PAULA MERRILL</flexString3>
<flexString4>PaymentId3489</flexString4>
<flexDouble1/>
<flexDouble2/>
<flexLong1/>
<flexLong2/>
<flexDate1/>
<flexDate2/>
<flexDate3/>
<attachment/>
<taskNumber>10240</taskNumber>
<creationDate>2006-02-23T14:53:08.955-05:00</creationDate>
<modifyDate>2006-02-23T14:53:08.955-05:00</modifyDate>
<isGroup>true</isGroup>
<versionNumber>1</versionNumber>
<notm>1</notm>
<expirationDate/>
<expirationDuration/>
</task>
Message was edited by:
gjacobi

I am using oracle.tip.pc.services.hw.task.impl.Task
that object has a toXML method.
To get that object, I am using the RemoteWorklistServiceClient.getWorlistTaskById method.
A word of caution. Not only am I still having the issue above (I had to hack my own WorkflowTask.xsd to make it validate) but I have noticed that the toXML() method actually returns different results when you think it would not. For example, I have something similar to the following code:
task.toXML()
task.toElement()
task.getPayload()
task.toXML()
The first and last toXML methods produce strings that do not match (it adds some empty elements to the end of the document). Weird. Very Weird.
Greg

Installed Photoshop Elements 13. Upon activation, get through sign in screen, but when doing serial number validation, validate goes round but does not validate. Connect Later is only way out of screen. How do I validate. Checked account but product n

How do one validate Photoshop 13. (Windows 8) Upon activation, get through to sign in screen, but when doing serial number validation, validate goes round but does not validate. Connect Later is only way out of screen. Checked account but product not listed. Installed with serial number that was sent by Adobe. Have attempted numerous times at different times of the day. On-line connection working.

Have you bothered to do any research at all? Not every app was upgrade to 5.5. Those that weren’t will next be upgraded to CS6.
Bob

"Battery serial does not validate", but the number is within the range

My sister came home from abroad for Christmas, and I checked her PB 12-inch battery serial number. Her battery has the serial number ZZ3480FJPVEA as far as I can see. This falls into the replacement range:
12-inch
iBook G4 A1061 ZZ338 - ZZ427.
On the exchange page, Apple writes: "If the first 5 digits of your battery’s 12-digit serial number fall within the noted ranges, please order a replacement battery immediately." But the battery serial does not validate even if I replace the zero with the letter "O".
Are there batteries within the range that still are ok?
Ingmar
PowerBook G4 12-inch Mac OS X (10.4.8)

I could not post an answer to the topic without marking the question
"answered", though it wasn't!
Strange, because the question is not marked as answered and it is not necessary to mark it in order to reply (simply click on the "reply" link near each post you want to reply to).
However when you feel that your question is answered - or the forum cannot be of further assistance - mark the question as answered and maybe also give some final notes.
If you got helpful replies, then you may award the posters by granting points. You can do so by clicking to "helpful" and "solved" buttons appearing near each post (you need to be logged in).
The buttons mean what they state: "Helpful" in the sense of user gave a useful answer or further information allowing you to solve an issue with some work of your own. "Solved" means that this post of the user is mainly responsible for managing an issue.
You can only mark one posting as "solved" in a thread, and - I hope this is correct - two or three times marking posts as "helpful". With the last, I'm not sure, you may have a look at "Help & Terms of Use".

Digital signature does not validate with the given key

We are switching our single-signon provider from openssl to Weblogic's SAML. I am trying to create a test application that will send mock SAML assertions to our test Weblogic SAML server before we begin integration with the client that will send real SAML assertions.
I have configured a Weblogic 10.3.5 instance to be a SAML Service Provider as well as created an application that creates test SAML assertions to post to the SAML server. I'm currently using a self-signed certificate to sign the SAML assertion. I've imported the self-signed cert into both the DemoIdentiy.jks and cacerts on the Weblogic SAML server.
The Weblogic SAML server is giving the following error when trying to validate the signature of the assertion:
<SAML2Assert: Start verify assertion signature>
<SAML2Assert: The assertion is signed.>
<SAML2Assert: Digital signature does not validate with the given key
org.opensaml.xml.validation.ValidationException: Digital signature does not validate with the given key
at org.opensaml.xml.signature.SignatureValidator.validate(SignatureValidator.java:68)
at com.bea.security.saml2.util.SAML2Utils.verifySamlObjectSignature(SAML2Utils.java:229)
at com.bea.security.saml2.providers.SAML2Assert.verifySignature(SAML2Assert.java:285)
>
I get this error when the SAML assertion includes both the cert and the public key, just the cert, just the public key or neither.
I'm pretty sure I've configured the SAML instance correctly since I followed the steps provided by another group who got this working with a different client. The only difference is they are using a real signed certificate (Verisign i believe) instead of a self signed cert.
I'm looking for any help to track down which step in the process I've missed or implemented incorrectly.
Thanks!
Edited by: 911967 on Feb 6, 2012 12:26 PM

So I found my own answer to the issue. The error was being caused by an the following xml in the assertion:
<ds:Reference URI="">
The value of URI attribute must have a '#' followed by the same value of the ID attribute in the parent 'Assertion' element (in our case a random string):
<saml:Assertion xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" ID="a5k42vnhsywezqzyufq15c4bb9xuzeozrmbppj38xe" IssueInstant="2012-03-12T14:33:25.986Z" Version="2.0">
<saml:Issuer>ISSUER_NAME</saml:Issuer>
<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
*<ds:Reference URI="#a5k42vnhsywezqzyufq15c4bb9xuzeozrmbppj38xe">*
How this is related to the digital signature is beyond me, though I admit I'm very new to saml and digital signing. However I spent a great deal of time investigating my certs and how I was creating the signature, which it seems is unrelated to the actual issue. I also wasn't able to find any docs specifying that this attribute was required, though I might have just missed it.

[svn] 3313: Fix for SDK-16981 - @ param tag does not recognize tab character as delimiter between paramName and paramDescription

Revision: 3313
Author: [email protected]
Date: 2008-09-23 10:02:50 -0700 (Tue, 23 Sep 2008)
Log Message:
Fix for SDK-16981 - @param tag does not recognize tab character as delimiter between paramName and paramDescription
QA: Yes
Doc:
Tests: checkintests
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-16981
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

I submitted my podcast and I got an email saying error, I checked with the feed validator and got this message: This feed does not validate. line 40, column 6: Undefined item element: itunes:order, how do sort this out, someone help me please.

I submitted my podcast and I got an email saying error, I checked with the feed validator and got this message: This feed does not validate. line 40, column 6: Undefined item element: itunes:order, how do sort this out, someone help me please.

Ignore it. 'itunes:order' is a recent addition which FeedValidator doesn't know about. If your podcast is rejected that is unlikely to be the reason. Of course as you haven't posted the feed URL nor the text of the error message I can't make any further comment.

Cflayout does not validate in strict XHTML

Greetings
Is there a workaround for this?
# Error Line 6, Column 70: there is no attribute "align"
…ript">_cf_loadingtexthtml="<div align='center'><img src='/CFIDE/scripts/ajax/r…
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
# Error Line 6, Column 78: document type does not allow element "div" here
…f_loadingtexthtml="<div align='center'><img src='/CFIDE/scripts/ajax/resources…
✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
# Error Line 6, Column 142: required attribute "alt" not specified
…ign='center'><img src='/CFIDE/scripts/ajax/resources/cf/images/loading.gif'/>";
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
# Error Line 10, Column 9: end tag for "div" omitted, but OMITTAG NO was specified
</script><script type="text/javascript" src="/CFIDE/scripts/ajax/messages/cfmes…
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 6, Column 59: start tag was here
…text/javascript">_cf_loadingtexthtml="<div align='center'><img src='/CFIDE/scr…
Thanks.....

Could you show us an example of the cflayout code?

WebLogic does not validate minOccurs="1" in webservices

Hello,
My WebService is deployed on WebLogic 10.3.3.
WSDL/XSD describes input parameter number as mandatory:
<xs:element minOccurs="1" maxOccurs="1" name="number" type="xs:int"/>
MinOccurs="1" means that XML message must contain <number> tag, isn't it?
I expect WebLogic has to validate all requests and server error response should be thrown when request is invalid.
Unfortunatelly, my SOAP client is able to send SOAP request without <number> tag and my webservice implementation receives such an invalid request.
Could you tell me please, is it correct behavior or is it defect in WebLogic?
Should my webservice perform it's own XML validation?

I added @SchemaValidation in my Java class, recompiled it and redeployed.
Server was restarted and cache and tmp folders were deleted.
Unfortunately, it does not work.
Scheme validation works without @SchemaValidation if add <validate-request>true</validate-request> into weblogic-webservices.xml.
My soap client received SOAP Fault and 500 Internal Server Error for request without mandatory tag.
But I use weblogic.wsee.tools.anttasks.JwscTask and it generate weblogic-webservices.xml without <validate-request>.
Therefore @SchemaValidation is the best solution for me.
Which reasons @SchemaValidation doesn't work?

Jsp:include tag does not preserve encoding of the text

hi
I am using Apache web server and Tomcat 4.1.
I have a jsp:include tag (in say test1.jsp) and I am trying to include a data1.html file. This html file contains UTF-8 encoded text. When this JSP is executed, the UTF-8 text is displayed as garbage characters.
I have included following in the JSP
<%@ page contentType="text/html; charset=UTF-8" %>
I have included following in the info.html
<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
However if I rename the info.html to data1.jsp and then include, the UTF-8 text gets displayed correctly.
I suppose, the JSP engine does not interprete the content of the html file correctly according to its encoding.
Where as if it is a .jsp, then it is int erpreting it appropriately?
Can anybody throw some lite on this?
regards
haresh
sample files.......
test1.jsp..........
<%@ page contentType="text/html; charset=UTF-8" %>
<%
response.setContentType("text/html; charset=UTF-8");
%>
<HTML>
<HEAD>
<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
</HEAD>
<BODY>
<jsp:include page="data1.html" flush="true"/>
</BODY>
</HTML>
data1.html.....
<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
<br>
हाती घ्याल ते तडीस न्या.
<br>

Your generated HTML will be flawed.
The output of the included JSP is included in the outputstream of the enclosing one.
Browsers will normally skip any illegal tags when encountered. This included your complete html headers from the included jsp and may (depending on the browser) include all code after the html close tag from that jsp.
Stricter browsers may simply refuse to display anything at all.
Read up on what the include mechanism exactly does and on wellformed HTML.

Duplicate item does not validate it

Hello
when I use F3 key to duplicate a lookup item (has invisible foreign key item) the duplicated item does not fire When-Validate-Item trigger to brings it invisible foreign key, How to solve this problem?

Use a key-dup-item trigger, and in it put:
duplicate_item;
set_item_property(:System.trigger_item,item_is_valid,property_false);
validate(item_scope);Not sure if both of the last two lines are necessary. It may work with only one of them.

The "a name" html tag does not work in Firefox.

The tag works in all versions of Internet Explorer, but does not work in Firefox versions 3, 4, 5, 10, 11, 12.

I haven't noticed any problems on most pages, but I have read about a problem where a script changes the length of the page content after loading (e.g., by collapsing content under headings, done on some FAQ or glossary pages).
For example, this should position the browser at the Reset Printer section:
http://kb.mozillazine.org/Problems_printing_web_pages#Reset_printer
A standard diagnostic step is to try Firefox's Safe Mode to see whether an odd behavior is caused by a custom setting or add-on.
First, I recommend backing up your Firefox settings in case something goes wrong. See [[Backing up your information]]. (You can copy your entire Firefox profile folder somewhere outside of the Mozilla folder.)
Next, restart Firefox in [[Safe Mode]] using
Help > Restart with Add-ons Disabled
In the Safe Mode dialog, do not check any boxes, just click "Continue in Safe Mode."
If links work correctly in Safe Mode, that usually points to an add-on or custom setting as the problem.
Let us know whether that makes any difference.

XHTML Generated by JBO tags does not validate

Similar Messages

Maybe you are looking for