that is compatible with features used by ofbiz. Has support for
DELETE, INSERT, INSERT SELECT, SELECT, UPDATE, and VIEW.
Modified the delegator side of the above to handle the new
interfaces. Now supports complex alias. Only SELECT is supported,
and the parseCondition code is disabled for the time being.
The plan(sic) here is to obviously support the other sql statements.
Then, to have a jdbc wrapper around all this, so external tools, that
only know how to talk jdbc, can actually talk directly to the
delegator.
Plus, many more people can understand sql syntax. This allows them
to do things with ofbiz, that they would find much more difficult if
they had to write <view-entity> definitions.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@880835 13f79535-47bb-0310-9956-ffa450edef68
Now client code can create local instances of specific converters without interfering with the operation of the factory method.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@835667 13f79535-47bb-0310-9956-ffa450edef68
This change can be reverted if any major issues come up. I will monitor the dev mailing list and fix any issues that are reported.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@834552 13f79535-47bb-0310-9956-ffa450edef68
Since the new converters aren't finished, I set it up so conversions fall back on the old ObjectType.java conversion code when needed.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@833786 13f79535-47bb-0310-9956-ffa450edef68
I replaced 4 while loops by for loops. Doing that I removed the empty checks. So I also used a FastList in StrungUtile.split() which I also refactored a bit.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@833725 13f79535-47bb-0310-9956-ffa450edef68
This changes just do that : set temporary the property in memory, and reset it back to its original value
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@824937 13f79535-47bb-0310-9956-ffa450edef68
The card id is stored in the Person.memberId field. It's used as a promo code. So if the same id is defined as a promocode, any promotion using this promo code will be added to the cart when you select a client from the Client Profile screen. Else a message will pop when selecting the client.
The idea is to generate promo codes and to use them as card id when creating the physical card.
The Client Profile screen (from Promo button in promo panel) allow you to search for all client (all fields empty) or to focus on a client (at least one field files). For now the search use a stric equals but I plan to allow also contains (ie %like%)
You may edit the client profile and as explained above select a client to apply promotions related to his/her card id.
I plan to add a status bar at bottom of the POS screen to see promocodes used (you may still enter arbitrary promo code with the Promo Code button) or even maybe rather the related promotions (but I doubt there will enough place).
The promo code is used as long as the cart is open.
There are also some generics enhancement in PosTransaction not all related to this new feature.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@823475 13f79535-47bb-0310-9956-ffa450edef68
I removed the deprecated methods from the Delegator interface. So, any replacements of GenericDelegator.getGenericDelegator(...) with the new factory method will have to include code to replace the deprecated method calls.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@821391 13f79535-47bb-0310-9956-ffa450edef68
Out of the box Tomcat allows you to configure "privileged" applications by specifying the context as follows.
<Context path="/manager" debug="0" privileged="true"
docBase="/usr/local/kinetic/tomcat6/server/webapps/manager">
</Context>
Since OFBiz is an embedded version of Tomcat it does not currently include a similar configuration for privileged applications.
The Tomcat manager application is a "privileged" application that includes utilities for monitoring JMX resources such as thread counts, connections, and any other configured JMX parameter. We use JMX with Hyperic to monitor our OFBiz servers
BTW, I used almost the same for Lambda Probe (https://issues.apache.org/jira/browse/OFBIZ-1397)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@816335 13f79535-47bb-0310-9956-ffa450edef68
org.ofbiz.base.container.NamingServiceContainer by default binds a server socket to all available network interfaces. Configuration of this container is done in
framework/base/config/ofbiz-containers.xml
<!-- load the naming (JNDI) server -->
<container name="naming-container" class="org.ofbiz.base.container.NamingServiceContainer">
<property name="port" value="1099"/>
</container>
Only the port can be configured.
Additional configuration property needs to be implemented:
<property name="host" value="0.0.0.0"/>
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@814390 13f79535-47bb-0310-9956-ffa450edef68