Posted by
David E. Jones on
URL: http://ofbiz.116.s1.nabble.com/Dev-Upgrading-from-2-1-1-tp168461p168462.html
Anton Mazkovoi wrote:
> The first decision we have to make is whether to upgrade to the latest
> source in SVN or the snapshot of EE that is shipped with opentaps 0.9.0.
> As we have some patches to merge into the code (I will send details on
> these in another e-mail) we would prefer to go with the latest source. I
> would really appreciate if you could give me some insight on its
> stability and readiness for production prime time.
As Si mentioned if you want to contribute patches to fix issues or move the tool forward (which would be great!) then yeah, go with the latest revision of the SVN trunk.
There shouldn't be much risk in this as the Entity Engine is really quite stable and hasn't seen many changes in a long time, and no significant backward compatibility breaking in a very long time.
> I would also be very interested to know, if it is possible to use the
> GeronimoTransactionFactory to manage transactions in various application
> servers (i.e. not just Geronimo). Has anyone tried this?
The GeronimoTransactionFactory is just for the embedded Geronimo JTA implementation (using the Jencks Geronimo wrappers). However, there are other TransactionFactory implementations, and even a JNDI one which is most likely to be used when deploying in a more traditional application server that has the JTA interface implementations and JDBC DataSources and such in JNDI.
> I would also love to hear from anyone who has upgraded from 2.1.1 to the
> latest Entity Engine builds. Are there any guides available that
> describe the required steps? So far I have found:
>
http://ofbizwiki.go-integral.com/Wiki.jsp?page=UpgradingOverview>
> However, I have noticed that the package names in EE had "core" removed.
>
> Are there any other things people have come across that we should keep
> in mind during the upgrade?
A few things have been mentioned in other replies to this messages. When upgrading just the Entity Engine you don't have to worry about migrating data or anything like that, which means that most of what users of higher level parts of OFBiz have to go through will not be necessary for you.
The main things that I'm guessing will require effort are any code changes you've made as fair amount has changed over the last few years since 2.1.1. I'd recommend doing a diff between your stuff and the 2.1.1 code base (if you can) and then make sure each change has a new home. That will probably be the bulk of the work needed.
The configuration and such is still almost exactly the same. There are quite a few new features, but older entity definitions and client code using the EE API should just need some import changes and that's it (ie a quick <ctrl>-<shift>-o in Eclipse).
> During the years of Entity Engine 2.1.1 usage, we have patched a few
> things. Some of them seem to be in the latest source already. However,
> there are still some things that are not there. I will follow up with
> another e-mail describing the patches we have come up with, as we would
> like to get them committed, if possible.
It would be great to see these and in general get your feedback. You've obviously put the Entity Engine through the paces, so anything you have to say or contribute would be well appreciated.
> P.S. Please forgive me if this e-mail should have been sent to the
> "users" list instead. As I plan to follow up with an e-mail discussing
> patches, to keep the thread in one place, I chose the dev list.
This is fine. I'm delighted to just see an understanding of the difference between typical users and dev mailing lists!
-David
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev