Web Form Validation Message Language Setting at Runtime when work in multi lingual environment

Question

Business Catalyst use the default culture language to display web form validation message.
When we are in multi lingual environment and not using subdoamin to handle multilingual sites, we found that the validation message did appear in the default culture setting. To make this work, we need to add the below script in our template.
<script type="text/javascript">
$(document).ready(function(){               
var head= document.getElementsByTagName('head')[0];
var script= document.createElement('script');
script.src= '/BcJsLang/ValidationFunctions.aspx?lang=FR';
script.charset = 'utf-8';
script.type= 'text/javascript';
head.appendChild(script);
</script>
Assuming the template is in french. You can change the lang parameter in the script according to your language.

Answer 1

After user 1 submits the page, it might not even be committed, so there is no way to have the pending data from user1 seen by user2.
However, we do have a new feature in ADF 11g TP4 that I plan to blog more about called Auto-Refresh view objects. This feature allows a view object instance in a shared application module to refresh its data when it receives the Oracle 11g database change notification that a row that would affect the results of the query has been changed.
The minimum requirements in 11g TP4 to experiment with this feature which I just tested are the following:
1. Must use Database 11g
2. Database must have its COMPATIBLE parameter set to '11.0.0.0.0' at least
3. Set the "AutoRefresh" property of the VO to true (on the Tuning panel)
4. Add an instance of that VO to an application module (e.g. LOVModule)
5. Configure that LOVModule as an application-level shared AM in the project properties
6. Define an LOV based on a view accessor that references the shared AM's VO instance
7. DBA must have performed a 'GRANT CHANGE NOTIFICATION TO YOURUSER'
8. Build an ADF Form for the VO that defined the LOV above and run the web page
9. In SQLPlus, go modify a row of the table on which the shared AM VO is based and commit
When the Database delivers the change notification, the shared AM VO instance will requery itself.
However that notification does not arrive all the way out to the web page, so you won't see the change until the next time you repaint the list.
Perhaps there is some way to take it even farther with the active data feature PaKo mentions, but I'm not familiar enough with that myself to say whether it would work for you hear.