First of all, I would like to mention our tentative roadmap for the releases:
• February 2014 - Apache OFBiz 13.07.01
• March 2014 - Apache OFBiz 12.04.03
• April 2014 - Apache OFBiz 11.04.04 (last release of the 11.04 series?)
• August 2014 - Apache OFBiz 13.07.02
On Jan 5, 2014, at 1:52 PM, Pierre Smits pierre.sm...@gmail.com wrote:
With regards to integration with other solutions I would like to see the
uptake of a solution like Apache Shiro regarding authentication,
authorization, etc.
+1
Jacopo
On Jan 5, 2014, at 1:52 PM, Pierre Smits pierre.sm...@gmail.com wrote:
*Re: slimdown*
The path set in the recent past regarding slim down is a good path. This
should be continued. But, slim down should not be about only focussing on
the framework. More visibility on the website should be
[
https://issues.apache.org/jira/browse/OFBIZ-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862868#comment-13862868
]
simon maskell commented on OFBIZ-5282:
--
Hi and Happy new year to everyone
Thought I
It's a peculiar case (license header then just below function doc.).
It was just annoying me to think that somebody using the same JS editor than me
in Eclipse would not see this function documentation by default (it has much
arguments).
Jacques
On Sunday, January 05, 2014 3:53 PM,
At least it would be great to have a themeable backend OOTB. Hence, as much as
possible, the widget form for consistency.
Also, though limited, you can always inject js in forms, the price rules and
promotions below are good examples.
Jacques
On Saturday, January 04, 2014 7:09 PM
On Monday, January 06, 2014 10:03 AM, jacopo.cappell...@hotwaxmedia.com wrote
Then, here is my personal wish list:
* integrate Atomikos Transaction Manager (to replace the existing old and
incomplete Geronimo Transaction Manager); I did most
of the work some time ago and also Scott helped
It appears that the citing of Drupal/WordPress/Magento solicited quite a
lot of comment. It's a side issue really and whether some houses prefer to
integrate existing solutions is besides the point. More importantly, most
commentators would agree that theme developement in Ofbiz does require
[
https://issues.apache.org/jira/browse/OFBIZ-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862991#comment-13862991
]
Jacques Le Roux commented on OFBIZ-3198:
Actually the idea cames 1st to me when
I would recommend that you create a Jira issue for it and enlist some help.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 1/6/2014 8:31 AM, Gavin Mabie wrote:
It appears that the citing of Drupal/WordPress/Magento solicited quite a
lot of comment. It's a side issue really and
I stumbled upon this and I wonder also why those files (like
ParseException.java) are duplicated in
framework/sql/build/gen-src/javacc/org/ofbiz/sql
and
framework/base/build/gen-src/javacc/org/ofbiz/base/json/
Adam, could you enlight us?
Jacques
On Sunday, October 20, 2013 4:28 PM
Has anybody got any good ideas for a way to disable ECAS from triggering
without commenting them out from the core code?
Like overriding the service definitions in hot-deploy it would be handy to
be able to clear any ECAs that are listening on a particular service call
or entity update from
[
https://issues.apache.org/jira/browse/OFBIZ-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862994#comment-13862994
]
Adrian Crum commented on OFBIZ-3198:
That doesn't answer my question. A stock location
[
https://issues.apache.org/jira/browse/OFBIZ-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862994#comment-13862994
]
Adrian Crum edited comment on OFBIZ-3198 at 1/6/14 1:50 PM:
Hello Rupert,
You need to switch on delegator name default-no-eca like this :
Delegator delegator-no-eca =
GenericDelegator.getGenericDelegator(default-no-eca);
Nicolas
Le 06/01/2014 14:48, Rupert Howell a écrit :
Has anybody got any good ideas for a way to disable ECAS from triggering
Pierre Smits created OFBIZ-5461:
---
Summary: include ivy clearcache in build
Key: OFBIZ-5461
URL: https://issues.apache.org/jira/browse/OFBIZ-5461
Project: OFBiz
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/OFBIZ-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863001#comment-13863001
]
Adrian Crum commented on OFBIZ-5282:
Simon,
From my perspective, everyone seems to
Hey Nicolas - long time no speak.
Not a blanket switch off - a targetted one.
For Example I dont want :
eca service=changeOrderItemStatus event=commit
condition field-name=statusId operator=equals
value=ITEM_APPROVED/
action service=checkDigitalItemFulfillment mode=sync/
[
https://issues.apache.org/jira/browse/OFBIZ-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863018#comment-13863018
]
simon maskell commented on OFBIZ-5282:
--
Hi Adrian
We have one of our accountants
[
https://issues.apache.org/jira/browse/OFBIZ-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-5461:
Attachment: OFBIZ-5461-BUILD-ivy-cleancache.patch
This patch fixes the issue.
include ivy
Hi Rupert:
This would indeed be a really nice feature.
Wish I knew how to do it.
Regards,
Ruth Hoffman
http://www.ruthhoffman.com
rhoff...@aesolves.com
On 1/6/14 8:48 AM, Rupert Howell wrote:
Has anybody got any good ideas for a way to disable ECAS from triggering
without commenting them out
[
https://issues.apache.org/jira/browse/OFBIZ-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863030#comment-13863030
]
Jacques Le Roux commented on OFBIZ-3198:
Imagine (a world where) you don't have a
Pierre Smits created OFBIZ-5462:
---
Summary: build.xml includes both namespace for Apache Ivy and
ivy-init target
Key: OFBIZ-5462
URL: https://issues.apache.org/jira/browse/OFBIZ-5462
Project: OFBiz
[
https://issues.apache.org/jira/browse/OFBIZ-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863046#comment-13863046
]
Adrian Crum commented on OFBIZ-3198:
I don't have a problem imagining future
[
https://issues.apache.org/jira/browse/OFBIZ-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-5462:
Attachment: OFBIZ-5462-BUILD-ivy.patch
This patch fixes the issue.
build.xml includes both
[
https://issues.apache.org/jira/browse/OFBIZ-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863054#comment-13863054
]
Paul Piper commented on OFBIZ-5040:
---
Since we have discussed this internally, perhaps
[
https://issues.apache.org/jira/browse/OFBIZ-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863054#comment-13863054
]
Paul Piper edited comment on OFBIZ-5040 at 1/6/14 3:41 PM:
---
[
https://issues.apache.org/jira/browse/OFBIZ-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux resolved OFBIZ-3198.
Resolution: Incomplete
In trunk, I added a geo point to FacilityLocation entity at
[
https://issues.apache.org/jira/browse/OFBIZ-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863066#comment-13863066
]
Jacques Le Roux commented on OFBIZ-3198:
Who knows, Google and Amazon could
Because that's how javacc works, it takes effort to keep it from not
generating those files.
And, those aren't the same classes, btw.
The fix for this would require changing javacc to allow for a different
exception to be thrown by the generated methods; this would then mean a
shared class
I agree that we should migrate FTL templates to ofbiz widgets for the sake
of consistency throughout the interfaces. However, I do have to say that
I would not use form widgets to develop a customer facing site. At this
point, Brainfood is pretty much at a consensus that we do not want to do
page
[
https://issues.apache.org/jira/browse/OFBIZ-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863289#comment-13863289
]
Pierre Smits commented on OFBIZ-5458:
-
After further analysis I found that in
[
https://issues.apache.org/jira/browse/OFBIZ-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863289#comment-13863289
]
Pierre Smits edited comment on OFBIZ-5458 at 1/6/14 7:29 PM:
-
Why have our own stuff at all? There are good JSON parsers and generators
around, one of the best for automatic type conversions and such being the one
built into Groovy (JsonSlurper, JsonBuilder, JsonOutput, etc).
-David
On Oct 20, 2013, at 8:28 AM, Adrian Crum
On Jan 6, 2014, at 5:09 AM, Jacques Le Roux jacques.le.r...@les7arts.com
wrote:
On Monday, January 06, 2014 10:03 AM, jacopo.cappell...@hotwaxmedia.com wrote
Then, here is my personal wish list:
* integrate Atomikos Transaction Manager (to replace the existing old and
incomplete Geronimo
One way to make the OFBiz Form/Screen/etc widgets more useful and extensible
would be to take another step beyond what Jacopo did a number of years ago with
the FTL macros to produce HTML/CSV/XML/etc.
The current implementation in OFBiz parses the XML file into Java classes and
then when
There are two problems with using DOM trees in OFBiz:
1. They consume a lot of memory. Keep in mind the entire XML file is
kept in memory, not just the bits you are interested in.
2. They are not thread-safe.
I did some refactoring a while ago where I replaced that approach with
a
One of my top annoyances with OFBiz coding is the inconsistency of tools,
especially the scripts and expressions within widgets and simple-methods.
A first step would be to make all expressions, conditions, etc use Groovy
instead of JUEL and the bits of BeanShell that are still used. Groovy
On Jan 6, 2014, at 12:26 PM, adrian.c...@sandglass-software.com wrote:
There are two problems with using DOM trees in OFBiz:
1. They consume a lot of memory. Keep in mind the entire XML file is kept in
memory, not just the bits you are interested in.
The parsed version is kept in memory,
It would be interesting to see the performance impact of that approach.
I overhauled Mini-language recently and in the process I made sure the
execution path was as short and straight as possible. That effort
produced a 40% performance improvement. I wonder how Java's
compile-time linking
Re: parsed version is kept in memory.
Would that be per tenant in a multi tenant setup or only once per running
Ofbiz instance?
Pierre Smits
*ORRTIZ.COM http://www.orrtiz.com*
Services Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail Trade
http://www.orrtiz.com
Quoting David E. Jones d...@me.com:
On Jan 6, 2014, at 12:26 PM, adrian.c...@sandglass-software.com wrote:
There are two problems with using DOM trees in OFBiz:
1. They consume a lot of memory. Keep in mind the entire XML file
is kept in memory, not just the bits you are interested in.
[
https://issues.apache.org/jira/browse/OFBIZ-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-5409:
---
Attachment: OFBIZ-5409 - Remove internal attributes for security reason and
secure json
[
https://issues.apache.org/jira/browse/OFBIZ-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863431#comment-13863431
]
Jacques Le Roux commented on OFBIZ-5409:
While creating a new patch, I stumbled
[
https://issues.apache.org/jira/browse/OFBIZ-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863438#comment-13863438
]
Pierre Smits commented on OFBIZ-5458:
-
Argh
public static String
[
https://issues.apache.org/jira/browse/OFBIZ-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863442#comment-13863442
]
Jacques Le Roux commented on OFBIZ-5461:
Hi Pierre,
Fast review: did you
[
https://issues.apache.org/jira/browse/OFBIZ-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863455#comment-13863455
]
Jacques Le Roux commented on OFBIZ-5241:
Should we give up, did someone test it
[
https://issues.apache.org/jira/browse/OFBIZ-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863455#comment-13863455
]
Jacques Le Roux edited comment on OFBIZ-5241 at 1/6/14 9:37 PM:
[
https://issues.apache.org/jira/browse/OFBIZ-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13863489#comment-13863489
]
Pierre Smits commented on OFBIZ-5461:
-
Hmm.
I must have gotten confused and made some
I can't think of any reason to do it different from how it is now, ie the
parsed version of the files are cached by their filename which is independent
of the tenant. You can have files that are used by only one tenant, but any
files that are used by more than one would be shared.
-David
On
On Jan 6, 2014, at 12:58 PM, adrian.c...@sandglass-software.com wrote:
Quoting David E. Jones d...@me.com:
On Jan 6, 2014, at 12:26 PM, adrian.c...@sandglass-software.com wrote:
There are two problems with using DOM trees in OFBiz:
1. They consume a lot of memory. Keep in mind the
Thanks for the info - that was informative!
I'm still not sold on keeping the DOM tree though. I seem to recall Adam
Heath doing a memory-use analysis a few years ago and he discovered that
even keeping a reference to a String from the DOM kept the whole tree in
memory. That is why he did all
[
https://issues.apache.org/jira/browse/OFBIZ-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-5461:
Attachment: (was: OFBIZ-5461-BUILD-ivy-cleancache.patch)
include ivy clearcache in build
[
https://issues.apache.org/jira/browse/OFBIZ-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-5461:
Attachment: OFBIZ-5462-BUILD-ivy-v2.patch
This patch resolves both this issue and issue OFBIZ-5462
54 matches
Mail list logo
