So the difference between #2 and #3 in your list would be that #2
writes out the XML files directly, while #3 would do so through an API?
There is a bit of both right now in the OFBiz framework APIs. The
Entity Engine, for example, was at one point used with full round-
tripping quite a
On Thu, 2007-04-05 at 09:05 -0400, David E. Jones wrote:
So the difference between #2 and #3 in your list would be that #2
writes out the XML files directly, while #3 would do so through an API?
Yes, that is what I was thinking.
There is a bit of both right now in the OFBiz framework
how about
Leave the build in the components, like they are now for development.
copying all files needed to the runtime folder like that startofbiz.*
hotdeploy folder,etc, so the runtime can be the only folder distributed.
it would require a copy section be added to each build.xml
Jacopo
I am starting to sound like david, which I guess is a good thing.
I would like to see the CRM stick to the entities we already have.
it seems a major duplication of effort to have two copies of information
floating around.
Also that all function of the CRM stay in the folders that best support
Andrew,
Which of the incarnations of this method are actually used? I'd say
get rid of the rest.
There are lots of methods in various classes in OFBiz that are
redundant like this and should be eliminated, I'd even like to do
that with the majority of the methods in the
[
https://issues.apache.org/jira/browse/OFBIZ-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian Crum updated OFBIZ-642:
--
Attachment: htmlwidget.patch
htmlwidget.patch addresses item #3 - reduce HTML output by eliminating
[
https://issues.apache.org/jira/browse/OFBIZ-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian Crum updated OFBIZ-642:
--
Attachment: htmlwidget.patch
Oops, forgot to delete test code before creating patch.
Make OFBiz more
+1 !
Jacques
Andrew,
Which of the incarnations of this method are actually used? I'd say
get rid of the rest.
There are lots of methods in various classes in OFBiz that are
redundant like this and should be eliminated, I'd even like to do
that with the majority of the methods in the
[
https://issues.apache.org/jira/browse/OFBIZ-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487084
]
David Shere commented on OFBIZ-431:
---
This appears to still be occurring. With sample data, I ordered 10 GZ-1004s
Refactor UPS upsRateInquire.
-
Key: OFBIZ-873
URL: https://issues.apache.org/jira/browse/OFBIZ-873
Project: OFBiz (The Open for Business Project)
Issue Type: Improvement
Components: product
[
https://issues.apache.org/jira/browse/OFBIZ-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anil K Patel updated OFBIZ-873:
---
Attachment: upsRateInquire.patch
Refactored upsRateInquire.
Refactor UPS upsRateInquire.
[
https://issues.apache.org/jira/browse/OFBIZ-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anil K Patel reassigned OFBIZ-873:
--
Assignee: Tim Ruppert
Refactor UPS upsRateInquire.
-
[
https://issues.apache.org/jira/browse/OFBIZ-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Ruppert closed OFBIZ-867.
-
Resolution: Fixed
Thanks Anil, this is added in rev 526058
Add Support for ProductFeatureCategory in
[
https://issues.apache.org/jira/browse/OFBIZ-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Ruppert closed OFBIZ-873.
-
Resolution: Fixed
Thanks, Anil. This is added in revision 526067.
Refactor UPS upsRateInquire.
14 matches
Mail list logo
