The xsd for the resource xml files is invalid. In addition, the format of the value of the xml:lang attribute in resource xml files is invalid, according to the xml standard.
The attached patch:
provides a valid xsd
updates UtilProperties and the Label Manager to deal with the correct formatting of the xml:lang value, while still working with the old format, following Adrian Crum's recommendation on the mailing list
includes simple unit tests for UtilProperties to ensure it does work with both formats
changes the Label Manager to include a reference to the new xsd, and to use the correct format of the xml:lang value, when writing a resource xml file.
Some minor code cleanups to these files.
jleroux: the base test suite was successfully run locally once UtilIOTests have been commented out (still an issue with it on Windows)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1305004 13f79535-47bb-0310-9956-ffa450edef68
The xsd for the resource xml files is invalid. In addition, the format of the value of the xml:lang attribute in resource xml files is invalid, according to the xml standard.
The attached patch:
provides a valid xsd
updates UtilProperties and the Label Manager to deal with the correct formatting of the xml:lang value, while still working with the old format, following Adrian Crum's recommendation on the mailing list
includes simple unit tests for UtilProperties to ensure it does work with both formats
changes the Label Manager to include a reference to the new xsd, and to use the correct format of the xml:lang value, when writing a resource xml file.
Some minor code cleanups to these files.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1304193 13f79535-47bb-0310-9956-ffa450edef68
* no active committer was maintaining the webslinger component
* the component was experimental and not really used by OFBiz
* the component was really big (lot of jars etc...) and we are trying to slim down the OFBiz framework and keep only the essential/useful features
* this fixes a security issue reported to the OFBiz PMC
The only Webslinger feature used by the OFBiz framework was the "service debug mode" (enabled by default with the property servicedispatcher.servicedebugmode): I have considered to keep it but it was impossible because it relied on Webslinger legacy code (in the org.webslinger.invoker.* package) that was never contributed as a source file to the OFBiz project; I have tried to review the source file from an external Webslinger repo but I couldn't find them; the only site about Webslinger I could find is this:
http://www.webslinger.org/Downloads
but the svn resources mentioned there are broken. The fact that the OFBiz frameework was dependent (for a feature useful only in development mode) on an external project that doesn't publish its source code (at least in an easy to find location) convinced me that it was better to clean up the dependency completely; on the bright side OFBiz should now use less memory.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1301866 13f79535-47bb-0310-9956-ffa450edef68
Similarly to Groovy services, the Groovy Events Handler sets the base script class containing helper methods; these helper methods have been enhanced in order to be used by groovy method executed as services or events in a transparent way.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1298908 13f79535-47bb-0310-9956-ffa450edef68
The engine comes from http://java.net/projects/scripting. I had to modify the code slightly because the BshScriptEngine class implemented Compilable - but the Compilable methods were not implemented. So I removed implements Compilable. I renamed the jar to signify that the code has been modified.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1297478 13f79535-47bb-0310-9956-ffa450edef68
In particular these chenges should make it easier to implement JSR-223 (even if I think that we should still treat Groovy in a special way).
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1296762 13f79535-47bb-0310-9956-ffa450edef68
- Addresses BIRT engine with a new POJO based runtime
- Add more content types
* Post Script
* Open Document Text
* Open Document Spreadsheet
* Open Document Presentation
- Remove warning messages at compile time
- Set an override content type in the view handler
A contribution of Chattree
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1293999 13f79535-47bb-0310-9956-ffa450edef68
The Merge contains the basic integration of jackrabbit into ofbiz and provides a simple API for further development.
Features:
API for easy CRUD operations
Versioning
Multi Language Support
Object Content Mapping
Sample Implementation in Example Area
See this merge as first step. The development is still in progress but this is the stable starting point for all feature developments.
Detailed description can be found in the Wiki: https://cwiki.apache.org/OFBIZ/jackrabbit-branch-development.html
For any questions, requests, issues use the jira post: https://issues.apache.org/jira/browse/OFBIZ-4659
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1231647 13f79535-47bb-0310-9956-ffa450edef68