THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- What is the best practice to modify an existing component or create a new one?
- What is considered the best practice in creating a custom web application with OFBIZ?
- How to Extend an existing component in customized application?
- How to manage your source differences?
- Which variables are available in screen context?
- Tips & Tricks while working with Groovy
- Deprecating entities
- Add a WAR file
- Using locale XSD files instead of OFBiz remote (at http://ofbiz.apache.org/dtds) for validation and content completion
- UBPL Introduction
- How to know which ant tasks are available : ant -p
- Ofbiz as a development framework - release 9.04
- Ofbiz as a development framework - upcoming release 10.04
- Field Description tooltip help
- How to not have a string escaped for html : org.ofbiz.base.util.StringUtil.wrapString(uiLabelMap.yourString)
- Turning Firefox cache on/off (mostly for javascript testing)
- Validation in forms
- How to change the default messages
- Profiling Ofbiz with YourKit in Eclipse
- Note on creating a view-entity using entity or view-entity from other components
- When and when not recompiling
Eclipse
...
What is considered the best practice in creating a custom web application with OFBIZ?
A David Jones's tip
One approach is to simply copy an entire component into a new directory and start hacking away at it until it fit your needs. This is a fine practice if you never have plans of bringing it up to date with a current revision or version. OFBIZ is currently making about 40 commits a week. By the time you complete your customizations, you are out of date.
...
Therefore it is important to make sure that if you're using entities from other component, make sure they are loaded BEFORE your component.
A tip from FooShyn
| Anchor | ||||
|---|---|---|---|---|
|
When and when not recompiling
This is a big, and often not enough known OFBiz greart fearture. Most of the time you don't need to restart when you change things in dev mode (dev mode depends on the content of cache.properties file, see here how to set it).
It's easier to name the main cases (I'll not get into details) where you need to restart:
- Containersn and alike configuration (this one seems obvious, changes related to the embedded application server - Tomcat - needs a restart)
- Java change (compilation)
- Service definition change (if your service is written in minilang you don't need to retart when changing the implementation)
- DB definition change (entity, field, etc.)
If the caches are on (ie not on dev mode), it's the same (you don't need to recompile) but you need to clear the caches. See at ...webtools/control/FindUtilCache You might even clear only the cache where things changed (production performance).