We could add a warning message to the EntityCondition classes (like the
one on line 411 of GenericEntity.java), then start checking the logs for
the warning messages.
-Adrian
Scott Gray wrote:
Thanks Adrian, I understand the implications now.
So what's the next step, should we add type check
Thanks Adrian, I understand the implications now.
So what's the next step, should we add type checking to the
EntityConditions and then perhaps only enforce the correct types on
some volunteer machines until we can fix a good portion of the problem
code and then move it to the trunk?
Regards
Scot
Scott Gray wrote:
Ok it makes more sense to me now, conversion needs to take place at a
level where the relevant information is still available so doing it on
a low level isn't really an option (even though that's been allowed to
happen up until now). I guess I was having trouble understanding w
[
https://issues.apache.org/jira/browse/OFBIZ-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-1982.
--
Resolution: Fixed
Thanks Marco !
The last patch (framework) is in trunk revision: 704697
>
Ok it makes more sense to me now, conversion needs to take place at a
level where the relevant information is still available so doing it on
a low level isn't really an option (even though that's been allowed to
happen up until now). I guess I was having trouble understanding why
we needed to do a
On Oct 11, 2008, at 9:40 AM, David E Jones wrote:
On Oct 10, 2008, at 4:09 AM, Bilgin Ibryam wrote:
On Fri, 2008-10-10 at 09:16 +0200, Christian Geisert wrote:
David E Jones schrieb:
[..]
Either way you need to check out the other OFBiz related
presentations,
training, and BOFs:
htt
127.0.0.0 should work fine again after rev. 704678
Thanks
Scott
2008/10/15 Adrian Crum <[EMAIL PROTECTED]>:
> Changing to localhost fixed it - thanks!
>
> -Adrian
>
> Scott Gray wrote:
>>
>> localhost will work but I'm fixing it for ip addresses now, sorry for
>> the trouble.
>>
>> Regards
>> Sco
Changing to localhost fixed it - thanks!
-Adrian
Scott Gray wrote:
localhost will work but I'm fixing it for ip addresses now, sorry for
the trouble.
Regards
Scott
2008/10/15 Adrian Crum <[EMAIL PROTECTED]>:
Actually, no. I'm using 127.0.0.0. Should I use localhost instead?
-Adrian
Scott G
Hi Jacopo,
It seems that this link does not exist anymore. Is there another mean ?
Thanks
Jacques
PS : resurrection of an old thread from 2006...
From: "Jacopo Cappellato" <[EMAIL PROTECTED]>
Anna,
the quick answer is yes and no.
At now, when the order is created, the product configuration i
localhost will work but I'm fixing it for ip addresses now, sorry for
the trouble.
Regards
Scott
2008/10/15 Adrian Crum <[EMAIL PROTECTED]>:
> Actually, no. I'm using 127.0.0.0. Should I use localhost instead?
>
> -Adrian
>
> Scott Gray wrote:
>>
>> That's weird, I tested it before enabling it ag
Actually, no. I'm using 127.0.0.0. Should I use localhost instead?
-Adrian
Scott Gray wrote:
That's weird, I tested it before enabling it again and the problem had
gone away. What domain are you accessing ofbiz through? Just plain
old localhost?
Thanks
Scott
2008/10/15 Adrian Crum <[EMAIL P
[
https://issues.apache.org/jira/browse/OFBIZ-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Risaliti closed OFBIZ-1998.
-
Resolution: Fixed
Fixed in rev. 704645.
> PAYMENT SET REF. button is not working correctly becau
[
https://issues.apache.org/jira/browse/OFBIZ-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Risaliti updated OFBIZ-1998:
--
Attachment: PaymentSetRef.patch
First patch for PAYMENT SET REF.
> PAYMENT SET REF. button is
PAYMENT SET REF. button is not working correctly because it sets now only the
first payment of the cart
---
Key: OFBIZ-1998
URL: https://issues.apache.org/jira/bro
That's weird, I tested it before enabling it again and the problem had
gone away. What domain are you accessing ofbiz through? Just plain
old localhost?
Thanks
Scott
2008/10/15 Adrian Crum <[EMAIL PROTECTED]>:
> Nothing in my browser is changed. I don't even close the browser window
> between v
Nothing in my browser is changed. I don't even close the browser window
between versions.
-Adrian
BJ Freeman wrote:
just to make sure do you have cookies enable for the URL you are using.
I have this type of problem, since I have to manually enable cookies for
each domain I use.
Adrian Crum s
just to make sure do you have cookies enable for the URL you are using.
I have this type of problem, since I have to manually enable cookies for
each domain I use.
Adrian Crum sent the following on 10/14/2008 10:02 AM:
> I've been having problems with the login screen constantly appearing
> since
[
https://issues.apache.org/jira/browse/OFBIZ-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Risaliti closed OFBIZ-1997.
-
Resolution: Fixed
Fix Version/s: SVN trunk
Fixed in rev. 704590.
Markus, I have commited
[
https://issues.apache.org/jira/browse/OFBIZ-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Risaliti reassigned OFBIZ-1997:
-
Assignee: Marco Risaliti
> German translations for product module
> -
I've been having problems with the login screen constantly appearing
since this revision - meaning I'm logged in, but when I click on various
application links I'm required to log in again.
I tried a fresh checkout - same problem. If I revert the Revision 703784
changes, the login screen stops
I mean in a specific log
Please let me know if this makes sense
From: "Jacques Le Roux" <[EMAIL PROTECTED]>
Maybe we could add an interrupting tool (at different code points if needed) on the demo server which would catch and put in log
all points needed to be changed before really changing the
From: "Adrian Crum" <[EMAIL PROTECTED]>
David E Jones wrote:
What I'm proposing is to fix this further up the stack in the GenericEntity.set method instead of lower down. I guess either way
we have the two options I mentioned earlier:
1. fail fast(er) by having OFBiz throw an exception
2. try
[
https://issues.apache.org/jira/browse/OFBIZ-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-1955.
--
Resolution: Incomplete
> Create a party relationship between a new customer and the product sto
David E Jones wrote:
What I'm proposing is to fix this further up the stack in the
GenericEntity.set method instead of lower down. I guess either way we
have the two options I mentioned earlier:
1. fail fast(er) by having OFBiz throw an exception
2. try to auto-convert
#1 will result, as Adri
Scott Gray wrote:
The service event handler, that's what I meant :-)
The guess the point I was trying to make was that with so many
services being called via the event handler aren't we making a pretty
huge exception to the rule that we're trying to enforce? The
performFind service would need to
In addition, the service event handler has the information needed to
perform a proper conversion (locale and time zone). The entity engine
does not.
-Adrian
David E Jones wrote:
I wouldn't say that bugs would be "created" by this change, more than
existing bugs would be exposed (that are on
German translations for product module
--
Key: OFBIZ-1997
URL: https://issues.apache.org/jira/browse/OFBIZ-1997
Project: OFBiz
Issue Type: Improvement
Components: product
Affects Versions: SV
[
https://issues.apache.org/jira/browse/OFBIZ-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus Studer updated OFBIZ-1997:
-
Attachment: product-translations-german.diff.zip
patch file with german translations for product
Inline:
2008/10/14 David E Jones <[EMAIL PROTECTED]>:
>
> I wouldn't say that bugs would be "created" by this change, more than
> existing bugs would be exposed (that are only visible on certain databases,
> etc).
You know what I mean though, whatever we call them there is going to
be a lot to fi
Hi Vikas,
I'd prefer to wait, before committing, that the changes are documented
Thanks
Jacques
From: "Vikas Mayur" <[EMAIL PROTECTED]>
I think it would be good to document such change.
- Vikas
On Oct 13, 2008, at 8:36 PM, Jacques Le Roux wrote:
Hi Vikas,
Did not look into detail yet, bu
I wouldn't say that bugs would be "created" by this change, more than
existing bugs would be exposed (that are only visible on certain
databases, etc).
The service engine doesn't actually do automated mapping, is the
service event handler that does this for web requests before the
actua
Ok I see your point, thanks for explaining.
#1 makes sense but it will be interesting to see how many bugs are
created, also doesn't the service engine currently perform automatic
conversion without any problems?
Regards
Scott
2008/10/14 David E Jones <[EMAIL PROTECTED]>:
>
> On Oct 13, 2008, at
On Oct 13, 2008, at 10:10 PM, Scott Gray wrote:
Inline:
2008/10/14 David E Jones <[EMAIL PROTECTED]>:
Scott, are you referring to the call to PreparedStatement.setString
on
SQLProcessor line 553? In other words, the difference in the
Postgres JDBC
driver is that they used to auto-convert
33 matches
Mail list logo