Changes in the relevant css files were not made. As a result the spinner is showing a horizontal repeat. This has been corrected.
Tomahawk themes/tomahawk/webapp/tomahawk/images/spinner.gif is now removed framework/images/webapp/images.spinner.gif will be used by all themes in order for the same consistent spinner image to be used.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1328738 13f79535-47bb-0310-9956-ffa450edef68
This patch will enable NOT-IN operator to the performFind service.
Only two lines of the file framework/common/src/org/ofbiz/common/FindServices.java were modified to enable de NOT-IN operator.
An use case is provided to test
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1328637 13f79535-47bb-0310-9956-ffa450edef68
A hideResultInLog service attribute is added. If set to true the service result will be hidden from possible exposition in ServiceDispatcher.runSync()
This is convenient when used for sending a password to an user (the password must be legible in the sent mail).
I'm sure a lot of you would want to have no logs at all in production. But by experience I know that we need to log info in logs even in production. Especially when the system is quickly moving ahead...
So this is a sure mean to hide any password in logs, being current or backuped somewhere on the servers disks...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1328122 13f79535-47bb-0310-9956-ffa450edef68
view was previously joined to another view, the conditions on the inner
view were added to the outer-most WHERE clause. This caused multiple
problems. One, if the join was optional, the generated sql actually made
it required(because it was in the WHERE, and not in the ON clause).
Second, the outer WHERE may reference a field that was not available *at
all* in the generated nested select(view table).
The fix is to *not* recurse thru all view member entities when finding
conditions, and instead attach them to a new WHERE clause on the
generated inner SELECT(view table).
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1327735 13f79535-47bb-0310-9956-ffa450edef68
case where getSerivceLogMap is called, and the elements are enumerated.
This could cause an error when the calling code was enumerating the map,
to print out it's information, but a service that was represented in the
map would finish, and get removed from the map. The calling code that
had the map might then get stuck in a loop that would never end(internal
to the map itself).
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1327731 13f79535-47bb-0310-9956-ffa450edef68
standard OutOfMemory type conditions; therefore, there is no reason to
actually catch and log any exception that won't be thrown anyways.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1327730 13f79535-47bb-0310-9956-ffa450edef68
reason that fails at class init time, then an exception will be thrown
then, and the class will not be usable.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1327729 13f79535-47bb-0310-9956-ffa450edef68
1. autocomplete feature shows the message "no records found" during a session timeout. This could be misleading for the user.
2. During a session timeout, clicking on ajax dialog button shows a large frame containing a message indicating session has timeout. Should show a more detailed message.
jleroux: what I adapted:
* Added <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> in htmlheader-for-ajax.ftl
* Replaced also spinner.gif in Tomahawk (better be consistent)
* Added a French label an kept those existing but English (improved by Wai)
* Removed the ajaxErrorText style in ajaxNotLoggedIn screen
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1327502 13f79535-47bb-0310-9956-ffa450edef68
started, a shutdown command get's issued, stopping is occurring, but
then the server state ends up being set to RUNNING.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1327254 13f79535-47bb-0310-9956-ffa450edef68
bother printing the thrown exception; this is a standard situation,
where the required jar may not have been downloaded, and the
instrumenter not compiled.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1327252 13f79535-47bb-0310-9956-ffa450edef68
Per the servlet specification, the web.xml file should allow an optional <distributable/> node to indicate that the application is clusterable. Currently, OFBiz does not respect this setting and assumes all applications should be distributed if any cluster configuration is provided in the ofbiz-containers.xml file. As a result, if, for example, the DeltaManager is enable, all applications attempt to cluster and communicate via DeltaManager.
The expected and proper functionality is to check the individual application's web.xml file for the <distributable/> node and only use the DeltaManager if found; otherwise the StandardManager should be used for sessions.
jleroux: replaced some tabs, reformatted, added a comment about <distributable/> in the *-containers.file
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1326064 13f79535-47bb-0310-9956-ffa450edef68