We could create a branch, convert the code there to remove javolution and then
run some profiling on the two instances; we could define in advance (before
starting the actual work) the tools and tests we will use to measure the
performance.
Then people will run the same tests in their own boxes
That's the thing - measuring performance can be tricky. A while back I
ran across some code that didn't use fixed-count loops, but instead ran
the test code through a loop indefinitely until the loop execution time
stabilized - then the stabilized time was used as the measurement. That
I do think it's definitely worthwhile trying this out. Looking at the history
of javolution on their main page[1], they don't appear to have made much in the
way of changes for at least 2 years and possibly up to 5, meanwhile the JDK/JVM
continues to progress.
I was expecting to check the
Please revert this as this is not fixing an error. There was no error to
begin with.
This commit only reflects a different viewpoint on what the function of the
screen should be.
2012/5/31 m...@apache.org
Author: mor
Date: Thu May 31 05:29:45 2012
New Revision: 1344568
URL:
Pierre, you'll need to do a better job of articulating your opinion if you want
a committer to take it into account. Only PMC members can request a revert
with little explanation (although that rarely happens, if ever).
Regards
Scott
On 31/05/2012, at 8:13 PM, Pierre Smits wrote:
Please
Hi Hans,
I'm sorry but could you go into a little more detail about the problem and
proposal? I'm not sure I understand well enough to even know what questions to
ask.
What would it mean to define a new entity resource reader-name? As far as I
understand they aren't actually defined
Scott,
You you are right, i am re-reading my email and it is too short.
The problem:
1. currently security data is part of seed and get always loaded.
2. if the security data of a component is not loaded, makes this
component invisible.
3. In a multi tenant environment I would like to have
Hey guys,
sry for the late response.
The new branch is for the further jackrabbit / ofbiz integration, to
keep the new experimental features away from the trunk until they work
reliable. I didn't remove the jcr code form the trunk because the
basic content repository functionality works and can
Thank you Sascha,
please see inline:
On May 31, 2012, at 11:23 AM, Sascha Rodekamp wrote:
Hey guys,
sry for the late response.
The new branch is for the further jackrabbit / ofbiz integration, to
keep the new experimental features away from the trunk until they work
reliable. I didn't
Scott,
Thanks again for pointing out that:
1. committers can and do implement changes without scrutiny from the
community,
2. this project has no PMC that ensures that the same set of rules apply
to both committers and other community members.
3. you tend to make up the rules as
1. I asked for a better explanation of the problem you see with this commit, I
actually prefer to have every commit scrutinized by anyone who is willing.
2. The same set of rules don't apply to committers and community members, hence
the commit access granted to committers through the
Hi Jacopo,
nope the branch is up to date so i don't lose anything if you remove it.
2012/5/31 Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com:
Thank you Sascha,
please see inline:
On May 31, 2012, at 11:23 AM, Sascha Rodekamp wrote:
Hey guys,
sry for the late response.
The new
Okay thanks for the additional detail, below is my attempt to further
understand a bit, please bear with me.
If we take as an example the accounting application, you'd like to be able to
make that available to some tenants but not others. At the moment in order to
do that you'd need to
Ankit Jain created OFBIZ-4912:
-
Summary: Error on Show Cart page
Key: OFBIZ-4912
URL: https://issues.apache.org/jira/browse/OFBIZ-4912
Project: OFBiz
Issue Type: Bug
Components: order
[
https://issues.apache.org/jira/browse/OFBIZ-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Jain updated OFBIZ-4912:
--
Attachment: OFBIZ-4912.patch
Attached patch will fix the issue.
Error on Show Cart
3. In a multi tenant environment I would like to have certain
components visible in a certain tenant and not in other tenants.
I see a fundamental flaw in the concept. Multi-tenancy is supposed to be
one instance of OFBiz running multiple instances of data. In other
words, the applications
Thank you for the replies up to now, let me make it even more simple:
instead of having all components enabled by default (security loaded), i
want to enable the component i want to use inside my custom component in
hot-deploy (only load security files of the components i want to use)
makes
We are already much further Adrian...allowing customizations and data
model differences per tenant...
Regards,
Hans
On 05/31/2012 06:44 PM, Adrian Crum wrote:
3. In a multi tenant environment I would like to have certain
components visible in a certain tenant and not in other tenants.
I see
please find my answer in-line...
On 05/31/2012 06:20 PM, Scott Gray wrote:
Okay thanks for the additional detail, below is my attempt to further
understand a bit, please bear with me.
If we take as an example the accounting application, you'd like to be able to
make that available to some
Deepak Dixit created OFBIZ-4913:
---
Summary: Application Menu items should be link not hidden form.
Key: OFBIZ-4913
URL: https://issues.apache.org/jira/browse/OFBIZ-4913
Project: OFBiz
Issue
[
https://issues.apache.org/jira/browse/OFBIZ-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Dixit updated OFBIZ-4913:
Attachment: OFBIZ-4913.patch
Set link type as anchor instead of auto for orderentry,
Component/TenantComponent entities are defined in framework/entity.
However, that code does not use them. entityext does. They should be
moved to the later component.
I've currently got org.ofbiz.entity.Main that can load a delegator,
without any of service or any other component loaded. No
[
https://issues.apache.org/jira/browse/OFBIZ-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tri Duc Vo updated OFBIZ-4759:
--
Attachment: OFBIZ-4759_VietnameseUiLabels(v2).patch
Dear mr Jacques // cc All
Here's our Patch for
Taher Alkhateeb created OFBIZ-4914:
--
Summary: LookupDecorator not working with Arabic characters
Key: OFBIZ-4914
URL: https://issues.apache.org/jira/browse/OFBIZ-4914
Project: OFBiz
Issue
Taher Alkhateeb created OFBIZ-4915:
--
Summary: LookupDecorator not working with Arabic characters
Key: OFBIZ-4915
URL: https://issues.apache.org/jira/browse/OFBIZ-4915
Project: OFBiz
Issue
[
https://issues.apache.org/jira/browse/OFBIZ-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taher Alkhateeb updated OFBIZ-4915:
---
Attachment: search_party_before_submit.png
Typing search for name before pressing submit
[
https://issues.apache.org/jira/browse/OFBIZ-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taher Alkhateeb updated OFBIZ-4915:
---
Attachment: search_party_after_submit.png
No results returned and encoding of searched text
The only problem there would be that the information would need to be known
when the record was created since fromDate forms part of the primary key. It's
entirely possible that the user could create the contact mech themselves via
the ecommerce app and then later an external service runs to
On Jun 1, 2012, at 6:44 AM, Scott Gray wrote:
The only problem there would be that the information would need to be known
when the record was created since fromDate forms part of the primary key.
It's entirely possible that the user could create the contact mech themselves
via the
29 matches
Mail list logo
