I finally got the second delegator to work. The external db delegator
throws errors initially because it cannot find OFBiz tables but works as
needed the warnings are thrown. Most of the instructions to get to this
point was provided in
https://cwiki.apache.org/confluence/display/OFBIZ/Handling+of+External+data
but it doesn't include anything about renaming readers and loaders which
seems necessary in order for start not to fail.
I think more documentation is needed on the subject of the creation and
use of new delegators.
On 01/16/2014 12:18 PM, Christian Carlow wrote:
I plan on using mini-lang simple-methods to implement the import
scripts and noticed that the <entity-condition> tag has a
delegator-name attribute. I'm not sure if this means it is required to
create a separate delegator when connecting to external dbs with
entities names matching those of OFBiz. I'll probably trying creating
a separate delegator again to handle the external db.
On 01/16/2014 11:53 AM, Christian Carlow wrote:
Seems like the relevant information to resolve this issue has been
removed from
https://cwiki.apache.org/OFBIZ/ofbiz-tutorial-a-beginners-development-guide.html.
On 01/16/2014 10:53 AM, Christian Carlow wrote:
I'm working on importing data into OFBiz and have encountered a
stoppage issue related to external db entity names matching those of
OFBiz. I added a <group-name> element to the default delegator in
entityengine.xml because I gave up trying to create a separate
delegator for the external entity described in
https://cwiki.apache.org/confluence/display/OFBIZ/Handling+of+External+data.
I suppose if a separate delegator existed to handle the external db
then there wouldn't be a conflict.
The documentation instructs to refer to
https://cwiki.apache.org/OFBIZ/ofbiz-tutorial-a-beginners-development-guide.html
on how to clean up entities that match the current DB but I can't
find anything in that doc that mentioned cleanup.
Can someone advise how these cases are typically handled?
``````````````````````
