JSF autocomplete - fails XHTML validation

My JSF pages (mojarra 2.0.1) generate a hidden state holder with an autocomplete="off"' property as part of the </h:form> closing tag:
<input type="hidden"
name="javax.faces.ViewState"
id="javax.faces.ViewState"
value="-1715251979060474851:6281790946545926031"
autocomplete="off" />
</form>The autocomplete property is not valid XHTML so it does not validate under XHTML 1.0 Transitional, or any other common XHTML DTD as far as I can tell (see: [http://validator.w3.org/]).
I'd like to validate under XHTML 1.0 Transitional. Has anyone got a good fix for this?

The autocomplete was added as a fix, so you do not want to disable this. See: [Issue 1129|https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1129]
There are a couple of ways to pass validation.
*1) add ATTLIST to doctype - does not work*
I found a way to pass XHTML validation as suggested by: [https://wiki.mozilla.org/The_autocomplete_attribute_and_web_documents_using_XHTML]
Its a little bit it of a cheat really, but I add *[<!ATTLIST input autocomplete CDATA #IMPLIED>]* into my doctype and it will pass the W3C XHTML validator:
<?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"
[<!ATTLIST input autocomplete CDATA #IMPLIED>]>This method passes validation, but this leaves your HTML with a "]>" at the start of the page, so is not usable
*2) Custom DTD*
The other way is to download the DTD from W3C, modify it and use your own custom DTD.
Also a cheat but gets you through the W3C tests.
Edited by: zsaurnni on Dec 7, 2009 10:24 PM

Similar Messages

Creating XHTML valid PayPal Forms

Hi,
Trying to create an XHTML valid paypal form for view cart, etc. This is the code from the paypal website:
<form target="paypal" action="https://www.paypal.com/cgi-bin/webscr" method="post">
<input type="hidden" name="cmd" value="_cart">
<input type="hidden" name="business" value=".............">
<input type="hidden" name="display" value="1">
<input type="image" src="https://www.paypal.com/en_GB/i/btn/btn_viewcart_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online.">
<img alt="" border="0" src="https://www.paypal.com/en_GB/i/scr/pixel.gif" width="1" height="1">
</form>
My solution so far is:
<form target="paypal" action="https://www.paypal.com/cgi-bin/webscr" method="post">
<fieldset class="paypal">
<div class="paypal">
<input type="hidden" name="cmd" value="_cart"/>
<input type="hidden" name="business" value="............."/>
<input type="hidden" name="display" value="1"/>
<input type="image" src="https://www.paypal.com/en_GB/i/btn/btn_viewcart_LG.gif" name="submit" alt="PayPal - The safer, easier way to pay online." />
<img alt=""src="https://www.paypal.com/en_GB/i/scr/pixel.gif" width="1" height="1" />
</div>
</fieldset>
</form>
The last error is with regard to the <form target=" "> I have experimented using JavaScript:
<script type="text/javascript">
//<![CDATA[
function submitform()
document.myform.submit();
//]]>
</script>
But not sure once I name the script if I can just remove target??
Any help would be greatly appreciated.
Regards,
Ozan89

1) Do we need to use WML renderkit for displaying information on a PDA.
- I'm not too experienced with PDA's, but I'm guessing most of them (new ones) support XHTML these days. You could easily use JSF for this. Which PDA's are you going to support? Is there a specific set of them or just about any PDA out there?
2) How can I develop a single JSP/JSF page and display both on laptop browser and PDA browser.
-If the PDA browser supports XHTML you could do CSS styling based on the user agent so that the page displays differently on the two.
3) Can plain HTML support this funtionality
- Again I'm not sure about PDA compability here, but I would think that many PDA's support plain HTML.
4) Are there examples which demonstrates developing this kind of application:
The WALL project seems like a good place to start searching.

Inconsistent Form Behavior on Failed Struts Validation

So I'm working on a strange bug regarding an Edit User form for an application, where some fields revert to their default and some fields do not.
We have a form for editing users in our system, with most of the usual information inputted in text boxes (login, first name, last name, password, password confirmation). We also have three possible levels of 'admin' - none, admin, and superadmin. These are chosen via radio buttons. There are also a couple of checkboxes (like 'user is active'). Overall, it's a fairly simple form.
When the form is submitted, we do struts validation. We've set up the validation via comment annotation in our Java code, like so:
     * @struts.validator type="minlength"
     *                   arg1value="${var:minlength}"
     * @struts.validator-var name="minlength" value="8"
     * @struts.validator type="maxlength"
     *                   arg2value="${var:maxlength}"
     * @struts.validator-var name="maxlength" value="50"
    public void setPassword1(String string) {
        password1 = string;
    }All of the fields in our form are set from user properties, so they're initialized by the values in the user object. For example, if we had user John Smith, an admin, with login 'jsmith,' we'd have the first name and last name fields initialized to John and Smith, and the radio buttons for Admin set to 'admin.' For reference, here's the EditUser.jsp code for the radio buttons, based off of the selectedAdminRole property:
<div class="InputElement">
        <label for="selectedAdminRole"><bean:message key="userForm.adminType"/></label>
          <html:radio styleId="selectedAdminRole" property="selectedAdminRole" value="None"
                      disabled="${userForm.loggedInUser.admin and userForm.userId == userForm.loggedInUser.id}">None</html:radio>
          <html:radio property="selectedAdminRole" value="Admin"
                      disabled="${userForm.loggedInUser.admin and userForm.userId == userForm.loggedInUser.id}">Admin</html:radio>
          <c:if test="${userForm.loggedInUser.superAdmin}">
              <html:radio property="selectedAdminRole" value="SuperAdmin">Super</html:radio>
          </c:if>
     </div>As you can see above, the struts validator requires passwords to be at least 8 characters long. So if the user tries to change their password to something with less than that, they'll fail validation and they'll end up back on the form with the validation errors in red at the top of the page. However, the form data that they've edited will be preserved. So if John had tried to change his first name to 'Fred,' he'd still see 'Fred' in the First Name text field, even though it wouldn't actually get saved to the user object until he submitted the form with no errors. This works with radio buttons too - if John had tried to set his admin status down to 'none' from 'admin,' the radio button 'none' would still be checked. Basically, it preserves all your progress on the form until you navigate away.
Unfortunately, it does NOT do this when you create a new user. Creating a new user uses the same form, and since there's no user object to get the fields from, they all get initialized to blank - except for one of the checkboxes ('user is active') and the radio buttons for admin (starts with 'none' checked). Now, if the user fills out the form and hits submit, but fails the struts validation, it preserves all the form data in the text fields, but reverts the checkboxes and the radio buttons to their default state.
This leads to the following problem: say I'm trying to create a new admin, Jane Smith. I fill out the whole form, check the 'admin' button, and then enter a four-letter password. I submit, and the form fails struts validation and throws me back to the page with an error message informing me that passwords need to be at least 8 characters. I look over the form again - the login field is still 'janesmith,' the first name field is still 'Jane,' the last name field is still 'Smith,' everything looks fine except I screwed up the password. I enter an 8 letter password and resubmit. Jane then logs in and complains that she's not an admin, because I didn't notice that the 'admin' button had reset itself to the default of 'none' when I failed validation.
My question is, why does it reset the radio buttons and checkboxes - but not the text fields - on failed validation when a new user is being created, but resets nothing at all when an existing user is being edited? I'd like it to reset none of the information when a new user is being created, but I cannot figure out the reason for this inconsistent behavior.
If anyone can help me figure out how to get this working so that nothing gets reset - or at least explain to me the reason for this inconsistent behavior - I would be very grateful. I will also try to provide any additional information I can if this isn't enough.

So what you are saying is that radio and checkboxes don't retain their state when validation fails?
Checkboxes are always troublesome because of their design. If not selected, they don't submit any value - so you have to specifically unset them.
My first instinct would be to look at the formbean which you are populating from, and see what (if anything) modifies its values.
- for originally loading the new user page is it an action or JSP? Does it apply any default values to the form?
- check the "input" page you redirect to when validation fails. Is it an action or a JSP?
- is the same form being uses on the newUser jsp and whatever action you are submitting it to?
- is there a form reset() method?
My theory is that the "input" page you are redirecting to when validation fails is an action, and it sets some values on the form prior to loading.
But thats just a guess at this point. Its hard to debug this without a working example. Its been a while since I worked with struts, and never with annotations providing the validation.
Suggestion for debugging: dump the contents of the form bean at strategic points in the process to see that the values are what you think they should be.
- running the save action
- just after validation
- on the jsp page.
Hope this helps some,
evnafets

XHTML Validation and Accessibility

We've recently completed developing some Application Express systems for a customer, and they were disappointed the pages did not pass W3C XHTML validation to meet their accessibility targets.
I've had the chance to do a bit of a post-mortem and nailed some issues that were down to our templates. I've also noted some previous threads here (notably Re: Validation!!! and Re: HTML DB and Accessibility (AA-Compliance) and look forward to resolution of markup validation issues in future releases. In the meantime, here are the most frequent problems we encountered. I'd appreciate any explanations, and any suggestions on how to improve matters in the short term.
INVALID ENTITIES
The majority of the validation errors are like:
Cannot generate system identifier for general entity "p_fname"
General entity "p_fname" not defined and no default entity
Reference not terminated by REFC delimiter
Reference to external entity in attribute value
Reference to entity "p_fname" for which no system identifier could be generated
Entity was defined here
Where the App Ex engine is generating internal URLs and not escaping ampersands, that are then interpreted by the validator as forming part of an entity. This isn't disastrous, but an early fix in a future release would be welcome as it would reduce the number of errors and make it easier to spot any arising from invalid template code.
Am I right in thinking that storing CSS, images and scripts externally to App Ex would eliminate this?
STANDARD HTML BUTTONS
All "HTML Buttons" result in:
Value of attribute "type" cannot be "BUTTON"; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
There is no attribute "onClick"
End tag for "input" omitted, but OMITTAG NO was specified
Where the engine is generating an attribute value in uppercase and attribute names in camel-hump case instead of all lowercase. We can work round this by creating an "HTML Button" template with valid attributes and values.
ITEM LABEL
Reference to non-existent ID "P1_DATASET_CATEGORIES"
Where the label is the overall label for a checkbox item with multiple checkboxes, all of which have their own valid label. Should the engine include the checkbox item as a hidden item? Can we work round this by doing that manually, e.g. in Post Element Text?
HEADERS
Reference to non-existent ID "GV_VALUE"
Where a report has report has Headings Type "None" and hence no <th>s for headers attributes to refer to. Is there a workaround for this?
REPORT BREAK FORMATTING
End tag for "br" omitted, but OMITTAG NO was specified
<br> tags inserted by break processing within the engine are not terminated " />". This is not controllable by any template (that I am aware of) - anything that can be done?
TEXT FIELDS
This is rather puzzling, as it seems to be random: items on some pages are affected, those on others are not. Anyone have an explanation?
There is no attribute "TYPE"
There is no attribute "NAME"
There is no attribute "SIZE"
There is no attribute "MAXLENGTH"
There is no attribute "VALUE"
There is no attribute "id"
Element "INPUT" undefined
End tag for "INPUT" omitted, but OMITTAG NO was specified
Reference to non-existent ID "P5_ENTRIES_DISPLAYED"
Where the engine is generating an element and attribute names in uppercase instead of all lowercase. From earlier threads, I'm presuming nothing can be done at present.
HYPERLINK
There is no attribute "HREF"
Element "A" undefined
As above: element and attribute names in uppercase instead of all lowercase.
TABLE HEADING/DATA ALIGNMENT
Value of attribute "align" cannot be "LEFT"; must be one of "left", "center", "right", "justify", "char"
Attribute value generated in uppercase. Any workaround?
REPORT SORT ARROW
End tag for "img" omitted, but OMITTAG NO was specified
Sort arrow <img> element not terminated " />". Any workaround? (Or can this be suppressed completely/replaced?)

Hello,
Most of your issues are things we are aware of and hope to get fixed in 3.0 as they are produced from an engine specifically using htf package to render elements which we will be changing. Unfortunatly with most of those issues I see there I don't think you can do much.
I doubt the html the engines produce will pass xhtml strict in 3.0 but we will pass xhtml transitional (other than maybe urls in links) with a custom DTD that takes into account things we output in our namespace.
Carl

Mitigation control: Sending failed No valid SAP sender address

GRC 5.3 SP10 RAR
In mitigation control: I have created a new control ID. When I am trying to assign it to a user getting error
"Sending failed No valid SAP sender address"
Please advise to resolve the issue. I need to mitigate user.

Hello Pal,
Please go to RAR configuration -> Risk Analysis -> Additional Options. Here check if you have the parameter Enable Monitor Notification set to YES. If you do then set this one to NO. Also, kindly check and make sure that you have a valid email address maintained for each of the mitigation control monitor in Mitigation tab.
If you wish to have the parameter set to yes only then you need to do the JAVA mail settings in Visual Admin. Check configuration of the JAVA mail client, which can be done using Visual Administrator, to send the Email Notification.
(Configuration > Java Mail Client > Properties > Smtp).
Regards, Varun
Edited by: Thakur Varun on May 21, 2010 3:47 PM

ICal Import Failed Multiple validation errors occurred.

I am trying to move my old iCal calendars that used to sync fine to the new ones to sync to mobile me
I exported each calendar but when I try to import each I get
iCal Import Failed Multiple validation errors occurred.
It occurs whether or not I choose to keep or remove unsafe alarms.
I have deleted iCal caches etc.

i'm having this problem as well. (in addition to duplicate calendars of the ones i was able to manually import.) any help would be greatly appreciated.
/rant on
this isn't really the way i had hoped to spend my saturday night, i'm really disappointed that ical didn't sync intuitively to mobileme--isn't that why i pay for a subscription?
/rant off.

ORA-04098 trigger"BANKTRAN_BEF_DEL" is invalid and and failed re-validation

Hey Experts,
I created follwoing trigger successfully...
create or replace trigger BANKTRAN_BEF_DEL
before delete on BANKTRAN
declare
weekend_error EXCEPTION;
not_authentocated_user EXCEPTION;
begin
if TO_CHAR(SysDate,'DY') = 'SAT' or TO_CHAR(SysDate,'DY') = 'SUN' THEN
RAISE weekend_error;
end if;
if SUBSTR(User,1,3) <> 'ATN' THEN
RAISE not_authentocated_user ;
end if;
EXCEPTION
WHEN weekend_error THEN
RAISE_APPLICATION_ERROR (-20001,
'Deletions not allowed on weekends');
WHEN not_authentocated_user THEN
RAISE_APPLICATION_ERROR (-20002,
'Deletions only allowed by authentocated users');
end;
but when deleting the records using query delete from BANKTRAN
getting the below error
ORA-04098 trigger"BANKTRAN_BEF_DEL" is invalid and and failed re-validation
Edited by: SShubhangi on Jan 7, 2013 4:21 PM

Alright.
Now Try the DML that causes the Trigger to fire.
And post the details.
PS:- Please use {noformat}{noformat} before and after the SQL statements/results or code samples.
It makes post more readable and you get better help.

Failed Core Validation

How to diagnose why XMLSignature.validate is returning "failed core validation"?
JWSDP 2.0 demos GenDetached and Validate work fine. Modified both to function properly with "file:" input rather than "http:", thus inserted calls to SetBaseURI for the JDK bug work around. Modified versions work fine also [with file: input].
Then moved both pieces of code into my application. Unlike GenDetached.java, which simply generates an internal KeyPair, I create a keystore using keytool -genkeypair. Modified the GenDetached code to read the keystore, extract the cert and thus the public key, and separately the private key. Signed with the private key. Transformed a JAXB object and inserted it into an XML file my application creates. Output looks good. But the code imported from Validate.java indicates "failed core validation", though the one and only reference validation status is "true", i.e., successful.
If I run Validate.java on the XML generated by my app, not GenDetached.java, it too indicates "failed core validation". So something must be wrong with the signing process.
How does one go about diagnosing "failed core validation"? The whole process appears to be simple pass/fail, with no explanation or diagnostic available. Thanks.

More information...
Have modified my app to not only transform a JAXB object and an OutputStream object but also a DOM object, see code as follows:
// output the resulting document to a JAXBResult
TransformerFactory tf = TransformerFactory.newInstance();
Transformer trans = tf.newTransformer();
JAXBContext jcs = JAXBContext.newInstance("com.cryptek.jtdi.dim.dmt.jaxb");
JAXBResult jaxbResult = new JAXBResult(jcs);
trans.transform(new DOMSource(doc), jaxbResult);
JAXBElement<SignatureType> jaxbElement = (JAXBElement<SignatureType>)jaxbResult.getResult();
// output the resulting document to stdout
trans.transform(new DOMSource(doc), new StreamResult(new FileOutputStream("signature.xml")));
// output the resulting document to a DOMResult
DOMResult domResult = new DOMResult();
trans.transform(new DOMSource(doc), domResult);
debugLogger.info("dom " + domResult.toString());
DumpNode(domResult.getNode(), 0);
Very curiously, DumpNode is revealing a <SignatureValue> identical to that produced by the JAXB object, i.e., a value which Validate.java rejects for "failed core validation" but approves reference validation.
Here is the log data for the JAXB transform object and the DOM transform object. Note <SignatureValue> in both cases is the same:
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - dom javax.xml.transform.dom.DOMResult@14ce5eb
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [#document: null] name #document type 9 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [Signature: null] name Signature type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [SignedInfo: null] name SignedInfo type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [CanonicalizationMethod: null] name CanonicalizationMethod type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [SignatureMethod: null] name SignatureMethod type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [Reference: null] name Reference type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [DigestMethod: null] name DigestMethod type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [DigestValue: null] name DigestValue type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [#text: HNq7BMuL4wdr6g6YJOuS8DlTcDA=] name #text type 3 value HNq7BMuL4wdr6g6YJOuS8DlTcDA=
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [SignatureValue: null] name SignatureValue type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [#text: gdnCqYJAy7z2xFV35trujkinUluBfp5rbif14yfDPrmrYIZCWlekeA==] name #text type 3 value gdnCqYJAy7z2xFV35trujkinUluBfp5rbif14yfDPrmrYIZCWlekeA==
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [KeyInfo: null] name KeyInfo type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [KeyValue: null] name KeyValue type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [DSAKeyValue: null] name DSAKeyValue type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [P: null] name P type 1 value null
2007-07-27 10:00:09,484 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [#text: /KaCzo4Syrom78z3EQ5SbbB4sF7ey80etKII864WF64B81uRpH5t9jQTxeEu0ImbzRMqzVDZkVG9
xD7nN1kuFw==] name #text type 3 value /KaCzo4Syrom78z3EQ5SbbB4sF7ey80etKII864WF64B81uRpH5t9jQTxeEu0ImbzRMqzVDZkVG9
xD7nN1kuFw==
2007-07-27 10:00:09,484 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [Q: null] name Q type 1 value null
2007-07-27 10:00:09,484 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [#text: li7dzDacuo67Jg7mtqEm2TRuOMU=] name #text type 3 value li7dzDacuo67Jg7mtqEm2TRuOMU=
2007-07-27 10:00:09,500 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [G: null] name G type 1 value null
2007-07-27 10:00:09,500 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [#text: Z4Rxsnqc9E7pGknFFH2xqaryRPBaQ01khpMdLRQnG541Awtx/XPaF5Bpsy4pNWMOHCBiNU0Nogps
QW5QvnlMpA==] name #text type 3 value Z4Rxsnqc9E7pGknFFH2xqaryRPBaQ01khpMdLRQnG541Awtx/XPaF5Bpsy4pNWMOHCBiNU0Nogps
QW5QvnlMpA==
2007-07-27 10:00:09,500 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [Y: null] name Y type 1 value null
2007-07-27 10:00:09,500 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [#text: MFc9VKzBT0ilHvURWYyFmwhPyCMdzVSqqkLe/SH+Y40vbZmUbyUboJHA/da0ad1CTjQjvCORXDb1
wml6N+/DOQ==] name #text type 3 value MFc9VKzBT0ilHvURWYyFmwhPyCMdzVSqqkLe/SH+Y40vbZmUbyUboJHA/da0ad1CTjQjvCORXDb1
wml6N+/DOQ==
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - schemaVersion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v1.0
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - schemaPublicationStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . Published
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - processingUrgencyIndicator . . . . . . . . . . . . . . . . . . . . . . . . . . false
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.schemaVersion . . . . . . . . . . . . . . . . . . . . . . . . . . . . v1.0
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.schemaPublicationStatus . . . . . . . . . . . . . . . . . . . . . . . Published
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.CanonicalizationMethodType.Algorithm . . . . http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.SignatureMethodType.HMACOutputLength[0] . . .
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.SignatureMethodType.Algorithm . . . . . . . . http://www.w3.org/2000/09/xmldsig#dsa-sha1
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.ReferenceType[0].DigestMethodType.Other[0] .
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.ReferenceType[0].DigestMethodType.Algorithm . http://www.w3.org/2000/09/xmldsig#sha1
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.ReferenceType[0].DigestValue . . . . . . . . HNq7BMuL4wdr6g6YJOuS8DlTcDA=
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.ReferenceType[0].id . . . . . . . . . . . . . null
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.ReferenceType[0].URI . . . . . . . . . . . . file:/C:/JTDITransport_svn/foo.txt
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.ReferenceType[0].Type . . . . . . . . . . . . null
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignatureValueType.id . . . . . . . . . . . . . . . . . . . null
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignatureValueType.value . . . . . . . . . . . . . . . . . . gdnCqYJAy7z2xFV35trujkinUluBfp5rbif14yfDPrmrYIZCWlekeA==
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.KeyValueType.DSAKeyValueType.P . . . . . . . . . /KaCzo4Syrom78z3EQ5SbbB4sF7ey80etKII864WF64B81uRpH5t9jQTxeEu0ImbzRMqzVDZkVG9
xD7nN1kuFw==
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.KeyValueType.DSAKeyValueType.Q . . . . . . . . . li7dzDacuo67Jg7mtqEm2TRuOMU=
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.KeyValueType.DSAKeyValueType.G . . . . . . . . . Z4Rxsnqc9E7pGknFFH2xqaryRPBaQ01khpMdLRQnG541Awtx/XPaF5Bpsy4pNWMOHCBiNU0Nogps
QW5QvnlMpA==
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.KeyValueType.DSAKeyValueType.Y . . . . . . . . . MFc9VKzBT0ilHvURWYyFmwhPyCMdzVSqqkLe/SH+Y40vbZmUbyUboJHA/da0ad1CTjQjvCORXDb1
wml6N+/DOQ==
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.KeyValueType.DSAKeyValueType.J . . . . . . . . . null
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.KeyValueType.DSAKeyValueType.Seed . . . . . . . null
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.KeyValueType.DSAKeyValueType.PgenCounter . . . . null
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.KeyValueType.java.lang.String . .
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.java.lang.String . .
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . null
And here is the OutputStream result. Note <SignatureValue> is NOT the same as the above, and that Validate.java approves these results:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
<SignedInfo>
<CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments"/>
<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#dsa-sha1"/>
<Reference URI="file:/C:/JTDITransport_svn/foo.txt">
<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<DigestValue>HNq7BMuL4wdr6g6YJOuS8DlTcDA=</DigestValue>
</Reference>
</SignedInfo>
<SignatureValue>E/402n/h/7G4z5tU4hq1UoNc5qM5e7KShpKl/E2Rtx20jrPN1rKVdg==</SignatureValue>
<KeyInfo>
<KeyValue>
<DSAKeyValue>
<P>/KaCzo4Syrom78z3EQ5SbbB4sF7ey80etKII864WF64B81uRpH5t9jQTxeEu0ImbzRMqzVDZkVG9xD7nN1kuFw==</P>
<Q>li7dzDacuo67Jg7mtqEm2TRuOMU=</Q>
<G>Z4Rxsnqc9E7pGknFFH2xqaryRPBaQ01khpMdLRQnG541Awtx/XPaF5Bpsy4pNWMOHCBiNU0NogpsQW5QvnlMpA==</G>
<Y>MFc9VKzBT0ilHvURWYyFmwhPyCMdzVSqqkLe/SH+Y40vbZmUbyUboJHA/da0ad1CTjQjvCORXDb1wml6N+/DOQ==</Y>
</DSAKeyValue>
</KeyValue>
</KeyInfo>
</Signature>

Trouble with notifications - failed schema validation

I am trying to send an Email notification from a workflow and am getting the following error:
System.Web.Services: System.Web.Services.Protocols.SoapException: The request failed schema validation: The element 'Message' in namespace 'http://schemas.microsoft.com/exchange/services/2006/types' has invalid child element 'Header' in namespace 'http://schemas.xmlsoap.org/soap/envelope/'.
List of possible elements expected: 'Sensitivity, Body, Attachments, DateTimeReceived, Size, Categories, Importance, InReplyTo, IsSubmitted, IsDraft, IsFromMe, IsResend, IsUnmodified, InternetMessageHeaders, DateTimeSent, DateTimeCreated, ResponseObjects,
ReminderDueBy, ReminderIsSet, ReminderMinutesBeforeStart, DisplayCc, DisplayTo, HasAttachments, ExtendedProperty, Culture, Sender, ToRecipients, CcRecipients, BccRecipients, IsReadReceiptRequested, IsDeliveryReceiptRequested, ConversationIndex, ConversationTopic,
From, InternetMessageId, IsRead, IsResponseRequested, References, ReplyTo' in namespace 'http://schemas.microsoft.com/exchange/services/2006/types'.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.ResourceManagement.WebServices.Mail.Exchange.ExchangeServiceBinding.CreateItem(CreateItemType CreateItem1)
   at Microsoft.ResourceManagement.Mail.ExchangeProxy.ExecuteCreateItem(CreateItemType request)
   at Microsoft.ResourceManagement.Mail.ExchangeServer.SendNotification(NotificationMessage message)
   at Microsoft.ResourceManagement.Mail.NotificationMessage.Send(Int32 timeoutInMilliseconds)
   at Microsoft.ResourceManagement.Workflow.Hosting.SendMailWorkItemProcessor.SendMailMessage(MessageContent messageContent, Int32 timeoutInMilliseconds)
   at Microsoft.ResourceManagement.Workflow.Hosting.SendMailWorkItemProcessor.ProcessWorkItem(WorkItem workItem
It appears that the Exchange web service doesn't like the schema FIM is presenting. Anyone seen this? Is there a trace setting that will dump out the call to the Exchange
server?
I have tested that I can hit
https://fqdn_server/ews/exchange.asmx
from the FIM Service account and the certificate is correct.

After getting product support involved, it turns out that we were pointing the FIM Service at an Exchange 2013 server but the mailbox had been created on and was physically stored on an Exchange 2010 server. By pointing FIM at the 2010 server or by trying
to send notifications to mailboxes on the 2013 server, we could make it work. Moving the mailbox from the 2010 server to the 2013 server did not solve the problem. It had something to do with mailboxes that were originally created on a 2010 server but
were accessed over EWS from a 2013 server.
It also was not a FIM issue. We used an EWS diagnostic tool (EWSEditor) to test outside of FIM and saw the same results.
The final result to get the specific user working for notifications was to create a new mailbox for them on the Exchange 2013 server.

E-Mail Validation fails (email validation)

Hi,
according to the RFC, emails addresses in the following
format are allowed: [email protected]
but SPRY fails on validating this email address. Is there a
fix for that? And if not, which file would I have to update in
order to allow this email format?
Thanks!
Nils

Hi Nils,
You need to modify
http://labs.adobe.com/technologies/spry/widgets/textfieldvalidation/SpryValidationTextFiel d.js
Open that file and do a search for 'email', you should see a
regular expression after it that looks something like this:
var rx = /^[\w\.-]+@[\w\.-]+\.\w+$/i;
You'll probably want to add the + to it like this:
var rx = /^[\w\.-\+]+@[\w\.-]+\.\w+$/i;
I'll file a bug on our side to make sure we allow all chars
specified in the RFC.
--== Kin ==--

First JSF Test fails

Hi,
I'm new to JSF and was just about testing a first simple test.
I'm using Tomcat (for WSDP), WSDP and Eclipse with the sysdeo-tomcat-plugin.
I followed a tutorial in a book ("Java Server Faces" by Andi Bosch, Addison-Wesley) so I'm sure that my code should work.
When I try to start the Tomcat, I get the following messages and my JSF pages are not accessable after that.
Tomcat Messages:
16.08.2006 16:17:28 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
16.08.2006 16:17:28 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2003 ms
16.08.2006 16:17:28 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
16.08.2006 16:17:28 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Sun-Java-System/Web-Services-Pack-1.4
16.08.2006 16:17:28 org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
16.08.2006 16:17:30 org.apache.catalina.core.StandardContext listenerStart
SCHWERWIEGEND: Skipped installing application listeners due to previous error(s)
16.08.2006 16:17:30 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error listenerStart
16.08.2006 16:17:30 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Context startup failed due to previous errors
16.08.2006 16:17:30 org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
[...] (Cuted for more clearness)
org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on port 8080
16.08.2006 16:17:39 org.apache.catalina.startup.Catalina start
INFO: Server startup in 11166 ms

Can nobody give me a hint? I have no ideas what "previous errors" could mean.

JSF 1.1 Tabset validation

Hi!
I have a simple page with a tabset and 2 tabs on it (JSF 1.1 Netbeans 6 vwp). I have a save button also. The two tabs have components that have required property true. I can save the page without getting a validation error if the unvisible tab is unfilled. I can reach all components in Invoke Apllication phase but only the visible tab is validated.
How is it possible to validate all tabs on the tabset?
Or how is it possible to recognize wich tabs are not wisited by the user and inform it?
Thanks in advance!
Peter

If required is "false", then validators will not execute when the field is empty.
The spec defines how to override the error message for when "required" validation fails, though I don't have the spec handy at the moment.
-- Adam Winer (EG member)

Failed Item Validation = Process Before Headers isn't run? (APEX 2.2.0)

Hi, all,
I have an item validation that fails. When the page reloads, I see the following in the debug output:
Do not run process "P41_BEFORE_HEADER", process point=BEFORE_HEADER, condition type=, when button pressed=If that process doesn't run, a flag I used to decide whether or not to display certain Page 0 regions never gets set properly, resulting in a mess.
Is there a way around this? The only thing that I can think of is to run the same code in a failed validation that gets run in my process. Is there a more elegant way?
Thanks!

I ended up finding Page rendering process doesn't run after validation error which basically says to make a PL/SQL region with an empty template and put any display-related PL/SQL there. I set the PL/SQL region's display point to "After Header", which is before any of my other regions.
I have a bunch of P0 regions that get conditionally displayed based on session state items set in the "Before Headers" process. All of the items are cleared by an application After Footer process. I don't want to rely on the session state, however, as the user might navigate using the browser buttons on a failed submit, and that might produce odd results. Unfortunately, I've realized that the application-wide processes don't get run either.
It seems that my option is just to create a PL/SQL function
FUNCTION SHOW_REGIONS
THIS_REGION BOOLEAN := FALSE
, THAT_REGION BOOLEAN := FALSE
, THE_OTHER_REGION BOOLEAN := FALSE
and call that function from my empty PL/SQL region, passing in true values for the regions that I want to show. Either this function would set application-level items, or other functions to get the individual flags could be called from each of the Page 0 region conditional display code. I think I will do the latter, unless there is some better way.
Thanks!
Message was edited by:
Don_84
CREATE OR REPLACE PACKAGE BODY
    TEST_PAGE_0_CONDITIONS
AS
    my_flag_one BOOLEAN := FALSE;
    my_flag_two BOOLEAN := FALSE;
    PROCEDURE SET_DISPLAY_FLAGS
            FLAG_ONE BOOLEAN := FALSE,
          , FLAG_TWO BOOLEAN := FALSE
    IS
    BEGIN
        my_flag_one := FLAG_ONE;
        my_flag_two := FLAG_TWO;
    END;
    FUNCTION GET_ONE
        RETURN BOOLEAN
    IS
    BEGIN
        RETURN my_flag_one;
    END;
    FUNCTION GET_TWO
        RETURN BOOLEAN
    IS
    BEGIN
        RETURN my_flag_two;
    END;
END;

Clean Install Solaris 10 05/09 - Update Manager Fails with Valid Acct

I have a clean install of Solaris 10 05/09, and Update Manager fails to register using a valid accout which I can login with at the Sun website. Why is this happening? How can this be fixed?

Here's the output from the script....
User: root
Logname: root
Tue Oct 6 15:35:18 EDT 2009
unknown
smpatch settings:
patchpro.backout.directory - ""
patchpro.baseline.directory - /var/sadm/spool
patchpro.download.directory - /var/sadm/spool
patchpro.install.types - rebootafter:reconfigafter:standard
patchpro.patch.source - https://getupdates1.sun.com/
patchpro.patchset - current2
patchpro.proxy.host - ""
patchpro.proxy.passwd **** ****
patchpro.proxy.port - 8080
patchpro.proxy.user - ""
smpatch analyze:
Failure: Cannot connect to retrieve current2.zip: This system is currently unreg istered and is unable to retrieve patches from the Sun Update Connection. Please register your system using the Update Manager, /usr/bin/updatemanager or provid e valid Sun Online Account(SOA) credentials.
Entitlement:
cat: cannot open /var/sadm/spool/cache/entitlement/*entitlement_client
Sun UC patch revision:
120336-04
121082-06
121119-16
121454-02
123004-03
123006-07
123631-03
123896-05
123896-15
124187-07
137138-09
Solaris release:
Solaris 10 5/09 s10x_u7wos_08 X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 30 March 2009
Solaris Kernel: Generic_141415-10
Machine Type: i86pc
Platform: i86pc
Java versions:
System default:
java version "1.5.0_21"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_21-b01)
Java HotSpot(TM) Client VM (build 1.5.0_21-b01, mixed mode, sharing)
Java 5:
java version "1.5.0_21"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_21-b01)
Java HotSpot(TM) Client VM (build 1.5.0_21-b01, mixed mode, sharing)
Java 6:
Unable to locate JRE meeting specification "1.6*"
Java used by smpatch and updatemanager:
/usr/sbin/pprosvc:JAVACMD="/usr/jdk/latest/bin/java -version:1.5*"
/bin/updatemanager:JAVA_EXEC="/usr/jdk/latest/bin/java -version:1.5*"
Cacao Java version:
java-home=/usr/jdk/jdk1.5.0_21
Cacao Base Directories:
cacao.install.rt.base.dir=/
cacao.install.etc.base.dir=/
Software Cluster:
CLUSTER=SUNWCall
All ccr properties:
18:
Property not defined: 18
cns.assetid:
cns.br.SunUCenabled:
true
cns.ccr.keyGenPath:
/usr/lib/cc-ccr/bin/ccrKeyGen
cns.clientid:
cns.httpproxy.auth:
cns.httpproxy.ipaddr:
cns.httpproxy.port:
cns.regtoken:
cns.security.password:
cns.security.privatekey:
cns.security.publickey:
cns.swup.UMautolaunch:
false
cns.swup.autoAnalysis.enabled:
true
cns.swup.checkinInterval:
2
cns.swup.lastCheckin:
0
cns.swup.patchbaseline:
current
cns.swup.regRequired:
true
cns.transport.serverurl:
patchsvr not installed.
Sun UC package status:
SUNWbreg not installed
SUNWdc not installed
Cacao instances:
online 15:19:45 svc:/application/management/common-agent-container-1:def ault
Services in maintenance/disabled state:
svc:/application/print/server:default (LP print server)
State: disabled since Tue Oct 06 15:15:37 2009
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: man -M /usr/share/man -s 1M lpsched
Impact: 2 dependent services are not running:
svc:/application/print/rfc1179:default
svc:/application/print/ipp-listener:default
Please attach /tmp/unknown-061009-suc-out.Z in your reply to the Sun Update Conn ection Technical Support Team.
#

Crystal Reports 12 merge module fails ICE validation during installation

Hi there,
I am using the CR 2008 merge module that I downloaded from this site, and am using MSI Factory 2.0 to install my product. The ICE validation fails during the build with the following errors.
C:\v9.wxs(6680) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'INSTALLDIR' which cannot be merged from the merge module 'C:\Program Files\Common Files\Merge Modules\CRRuntime_12_0.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
C:\v9.wxs(6680) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'ProgramMenuFolder' which cannot be merged from the merge module 'C:\Program Files\Common Files\Merge Modules\CRRuntime_12_0.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
C:\v9.wxs(6680) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'CommonAppDataFolder' which cannot be merged from the merge module 'C:\Program Files\Common Files\Merge Modules\CRRuntime_12_0.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
C:v9.wxs(6680) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'ProgramFilesFolder' which cannot be merged from the merge module 'C:\Program Files\Common Files\Merge Modules\CRRuntime_12_0.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
light.exe : error LGHT0204 : ICE79: Feature 'CMS' referenced in column 'InstallExecuteSequence'.'Condition' of row 'CMSsetupConfiguration.9CED35E4_C9E6_11D3_9833_00A0C9DA4FE9' is invalid.
Any ideas what this means?
Thanks,
Rod

Hi Falk, thanks for your interest.
Yes, I can build the setup, but I need to have zero ICE validation warnings in order to pass the Vista Certification process. It seems to me that the default merge module for CR2008 has been put together in a way that fails best practice - eg. ICE validation.
The merge module is simply added to a feature within the installer product, and if I turn on the switch to "Ignore ICE warnings", then the build works OK and I can install the product no problems. However if I turn off the "Ignore ICE warnings", then the build fails and stops dead.
The snippet I posted here was from the log file.
Hope this helps,
Best regards,
Rod

JSF autocomplete - fails XHTML validation

Similar Messages

Maybe you are looking for