Best practices for multi-channel/shared data validation

I am in the midst of the redesign of a CORBA-based application framework. The target architecture is J2EE. One architectural goal is that EJB's are used to house (or at least front-end) all core business logic and rules - no underlying knowledge or concern about page flow, data collection or

session race / transfer issue

We have encountered a problem in which it appears (from user's description, transaction records, web application logs, and web server access logs), that user sessions are being transferred from one user to another. For example, two authenticated users: * user A with session id 1 from ip 1.2.3.4

Validation mask ranges

We are in a bind so I reposting under a different topic. Sorry, but ... We are trying to limit user input to the following ranges in ISO-8859-1: 32-126 160-255 As well as characters 9, 10 and 13. We have tried various things but have run into problems with the #' characters, plus it is

RE: Validation mask ranges

MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. From: Brown, James Sent: 2004 August 19 12:22 To: '[EMAIL PROTECTED]' Subject

How to set mask to validate ISO-8859-1 character set

What is the correct way to setup struts validation to allow a user to enter the following characters in ISO-8859-1 character set: Hex codeEquivalent characters 0x09\t 0x0A\n 0x0D\r 0x21-0x7E !#$%'()*+,-./0123456789:;=[EMAIL PROTECTED]|}~ 0xA0-0xFF

Recommendations for a JavaScript date picker

Any recommendations for a JavaScript date picker? I have taken a quick look at struts:layout but I do not need all that it has to offer nor the overhead. Integration into struts (and struts validation) would be beneficial, but not required. -- James THIS COMMUNICATION MAY CONTAIN