Re: Active Directory, JNDI, EOModel

2017-07-24 Thread Chuck Hill
Hi Tim, Take a look at the JNDIAdaptor class. There are connection dictionary parameters in there, one of those might be what you want. Or can you specify that on the connection URL? Chuck From: Tim Worman Date: Monday, July 24, 2017 at 11:43 AM To: Chuck Hill Cc: WebObjects Development

Re: Active Directory, JNDI, EOModel

2017-07-24 Thread Tim Worman
Using Wireshark, below is what I’m seeing for the two queries. The biggest difference right off the bat is that the WO/EOModel search seems to search ROOT as the base DN whereas the Apache DirectoryStudio is using “DC=adinstance,DC=ucla,DC=edu” as the base. The WO/EOModel search also appears to

Re: ERCoreBusinessLogic

2017-07-24 Thread GILQUIN Pierre
Great, thanks Ted, The example in BugTracker is written ERXAuditKey. A s was missing ! Le 24.07.2017 à 12:54, Theodore Petrosky a écrit : 1. Add the ERCBL framework to the project 2. In the entity modeler, add to the User Info the attribute names you want to watch: You must make sure the

Re: Migrating to google cloud

2017-07-24 Thread Paul Hoadley
Hi Mark, On 23 Jul 2017, at 10:18 pm, Mark Gowdy wrote: > Has anyone considered using the more advanced ELB setup as an alternative to > apache and the adaptor? > Similar to how mod_proxy works. > > Static stuff could be served from S3, and ELB would load balance across the > instances? Sou

Re: ERXFileUtilities rendering file name's type extension unusable

2017-07-24 Thread Johann Werner
If the two dots are meant to prevent switching to a parent directory you could change the regex to something like fileName.replaceAll("(/|^)\\.\\.(/|$)", "$1$2“); So this would only match two dots if they entirely describe a directory name and would match e.g. /var/../etc/foo /abc/.. ../foo b

Re: ERXFileUtilities rendering file name's type extension unusable

2017-07-24 Thread Fabian Peters
Hi Ralf, > I think the separator search has to match the platform running the app (and > you may better use then a File object), or be much stricter and search always > for all separators. For example suppose you are running on a Unix and get the > following path: > > \/etc/passwd > > Now yo