I am not quite sure if a JIRA with exactly my non thread-safe issue
could be found.. so I started with the target to upgrade that class and
all related..but those related drove us further to more and more - at
least for the moment it seems no chance that way
thanks,
Flopa
If you are mostly interested by the framework fixes, you may try to
apply the patches you may found in respective Jira issues...
Jacques
From: "Florin Popa" <[email protected]>
We have a separate Eclipse project which contains ONLY the resources we
ever touched. But even like this no one of the procedures seems easy for
the moment
regards,
Flopa
Given the amount of changes required to back port you're probably
better to upgrade to a newer revision, depending on how you've
handled your custom code and what tests you have in place to verify
your main areas of functionality, it should be relatively
straightforward.
Regards
Scott
HotWax Media
http://www.hotwaxmedia.com
On 25/01/2010, at 7:01 AM, Florin Popa wrote:
Hello all,
We started to develop an e-commerce application based on Ofbiz
framework around 2 years ago.
The version we started from is a revision 691692.
Main problem is that we already have few systems launched into
production, based on that revision.
Meanwhile, doing some mass tests, we encountered a lot of problems
- mostly related to transactions...
We noticed the implementation of
/framework/entity/src/org/ofbiz/entity/transaction/TransactionUtil.java
has lots of problems from this point of view - maybe not thread safe.
We just checked out today revision 902810 and it seems someone
really improved a lot that source code from threads-safe point of
view.
Trying to upgrade only that class into our old version drove to
upgrade for more and more classes. We encountered lots of
incompatibilities - the source code has been in some places fully
changed. Right now, having more than 800 compilation errors I would
not feel too optimist to integrate only what I need from the newer
version into the old one.
On the other hand, trying to get 902810 and then put over our work
might also cause same problems because the entity layer and
conditions handling seems to be changed.. I even expect to be worse
that way because maybe web templates are also changed.
Which way could someone suggest to proceed for a better version
where all database/entity layer/transaction later problems are fixed?
Many thanks,
Flopa
