Hey Separate-Deployment-with-Portlets-Developers
I am happy to see that more and more people work with Orbeon in Separate Deployment with Portlets. For me it works fine with Liferay 6.0.5 and a pritty new Orbeon nightly build. Orbeon.war includes to much resources which are not needed for separate deployment with portlets. Does anybody has experiences with "Slimming" the big fat Orbeon.war? - specially with Liferay? I have my own batch which kicks out resources I don't need. But still, the Orbeon.war needs to much resources I think. Cheers Karolin ===================================== unzip orbeon.war -d \orbeon cd WEB-INF Del jonas-web.xml Del sun-web.xml Del weblogic.xml Del commons-cli-1_0.jar REM delete Orbeon xForms test portlet Del liferay-display.xml Del liferay-portlet.xml Del portlet.xml REM delete xForms portlet samples Del *.xml cd resources rmdir /S /Q apps rmdir /S /Q forms Del *.xml REM Delete jar files we already loaded through our portal cd lib Del log4j*.jar Del xerces-resolver*.jar Del xerces-serializer*.jar Del xerces-xml-apis*.jar REM xerces-xercesImpl-2_9_orbeon_20070711.jar -> needed by Orbeon!! Del commons-beanutils-1_5.jar Del commons-codec-1_3.jar Del commons-collections-3_1.jar Del commons-lang-2_3.jar Del commons-logging-1_0_4.jar Del commons-pool-1.3.jar REM Del dom4j-1_6_1.jar(Specification-Version: 5.1.0.GA dom4j.jar) Del commons-io-1_1.jar Del commons-fileupload-1.2.1.jar REM Delete this jars if you don't use PDF stuff with xForms Del flyingsaucer-20100212-itext-2_1_7.jar Del flyingsaucer-core-renderer_orbeon_20100512.jar Del itext-bcmail-jdk14-138.jar Del itext-bcprov-jdk14-138.jar Del pdfbox-0_7_1.jar cd ..\.. REM delete xForms portlet sample for release rmdir /S /Q xforms-jsp Move orbeon.war orbeon-original.war zip -r -9 orbeon.war WEB-INF rmdir /S /Q xforms-jsp rmdir /S /Q WEB-INF |
Administrator
|
Karolin,
There are probably more JARs that can be removed. We should make such an official list today. You might not need ant, batik, barcode, pdfbox, and there might be a couple others. (Ideally the dependencies between Orbeon Forms "components" should be made clearer, but we haven't gotten to that yet.) -Erik On Tue, Dec 28, 2010 at 8:14 AM, Karolin Krieg <[hidden email]> wrote: > > Hey Separate-Deployment-with-Portlets-Developers > > I am happy to see that more and more people work with Orbeon in Separate > Deployment with Portlets. > For me it works fine with Liferay 6.0.5 and a pritty new Orbeon nightly > build. > > Orbeon.war includes to much resources which are not needed for separate > deployment with portlets. Does anybody has experiences with "Slimming" the > big fat Orbeon.war? - specially with Liferay? > > I have my own batch which kicks out resources I don't need. But still, the > Orbeon.war needs to much resources I think. > > Cheers Karolin > > > ===================================== > unzip orbeon.war -d \orbeon > > cd WEB-INF > Del jonas-web.xml > Del sun-web.xml > Del weblogic.xml > Del commons-cli-1_0.jar > > REM delete Orbeon xForms test portlet > Del liferay-display.xml > Del liferay-portlet.xml > Del portlet.xml > > REM delete xForms portlet samples > Del *.xml > cd resources > rmdir /S /Q apps > rmdir /S /Q forms > Del *.xml > > REM Delete jar files we already loaded through our portal > cd lib > Del log4j*.jar > Del xerces-resolver*.jar > Del xerces-serializer*.jar > Del xerces-xml-apis*.jar > REM xerces-xercesImpl-2_9_orbeon_20070711.jar -> needed by Orbeon!! > Del commons-beanutils-1_5.jar > Del commons-codec-1_3.jar > Del commons-collections-3_1.jar > Del commons-lang-2_3.jar > Del commons-logging-1_0_4.jar > Del commons-pool-1.3.jar > REM Del dom4j-1_6_1.jar(Specification-Version: 5.1.0.GA dom4j.jar) > Del commons-io-1_1.jar > Del commons-fileupload-1.2.1.jar > > REM Delete this jars if you don't use PDF stuff with xForms > Del flyingsaucer-20100212-itext-2_1_7.jar > Del flyingsaucer-core-renderer_orbeon_20100512.jar > Del itext-bcmail-jdk14-138.jar > Del itext-bcprov-jdk14-138.jar > Del pdfbox-0_7_1.jar > > cd ..\.. > REM delete xForms portlet sample for release > rmdir /S /Q xforms-jsp > > Move orbeon.war orbeon-original.war > > zip -r -9 orbeon.war WEB-INF > > rmdir /S /Q xforms-jsp > rmdir /S /Q WEB-INF > -- > View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Slimming-Downsize-Orbeon-war-for-Separate-Deployment-with-Portlets-tp3166132p3166132.html > Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com. > > > -- > You receive this message as a subscriber of the [hidden email] mailing list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws > > -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Hey Erik
The original Orbeon.war is 50'882 KB my slimmed Orbeon.war 35'592 KB. But still, using Orbeon.war in separate deployment Orbeon is still very big and lots of resources are loaded which I doubt are needed?! batik-all-1_6.jar --------------- Without batik-all-1_6.jar Orbeon.war doesn't deploy any more in Liferay 6.0.5 Portal. I wonder if it’s really necessary and why Orbeon includes batik-all in stet of the specific batik jars? Because some batik jars are often already included in separate deployment. (batik-xml.jar, batik-util.jar ...) Orbeon jars versions ------------------- I guess its due to Orbeon was not designed for separate deployment that official jars are complied in a special Orbeon version? Lots of this jars I could remove because they are already included in Liferay Portal but with an other version. xerces-xercesImpl-2_9_orbeon_20070711.jar exist-modules-1_2_6_orbeon_20090702.jar xerces-serializer-2_9_orbeon_20070711.jar msv-xsdlib-20070407_orbeon_20100309.jar msv-20081113_orbeon_20081209.jar flyingsaucer-core-renderer_orbeon_20100512.jar exist-ngram-module-1_2_6_orbeon_20090702.jar antlr-2_7_4_orbeon.jar xerces-resolver-2_9_orbeon_20070711.jar saxpath-dev_orbeon.jar saxon-9-1-0-8_orbeon_20101223.jar jakarta-oro-2_0_8_orbeon.jar exist-optional-1_2_6_orbeon_20090702.jar exist-1_2_6_orbeon_20090702.jar Orbeon jars ----------- I wonder if Orbeon jars itself like the big orbeon-resources-public.jar can get slimmed. There are lots of resources I doubt are really needed like: orbeon-resources-public.jar\ops\firebug\ orbeon-resources-public.jar\ops\unit-tests\ orbeon-resources-public.jar\ops\yui\examples\ orbeon-resources-public.jar\ops\yui\yahoo\ orbeon-resources-public.jar\ops\yui\yahoo-dom-event\ orbeon-resources-public.jar\ops\yui\yuitest\ ..... I know that depending on the system where Orbeon is integrated some jars can get removed or not. I appreciate your help very much to Cheers Karolin |
Administrator
|
Karolin,
I am pretty sure Batik is not really needed, but I am not sure why it's not working if you remove it. There are two reasons we have our "own" -orbeon JARs: 1. to avoid conflict with JARs present somewhere else (your app, the JDK) 2. some have patches against a standard version For #1, those are "re-rooted", i.e. they are put in a different package to avoid conflicts. #1 and #2 are sometimes combined. E.g. Saxon both has patches and is re-rooted. Either way, at this time you don't have a choice and have to use those versions instead of the Liferay versions. Now this said, it is clear that some trimming could be done, but if you are running in an environment with GB of disk and RAM, it's probably not worth the effort saving a few MB here or there. Performance will likely not change a bit because of such trimming. What we would like to do, ideally, would be to move to a modular, OSGi-based architecture: this would allow: * avoiding the pain of re-rooting JARs completely * splitting the product into mandatory and optional modules If anybody is interested in prototyping that, let us know! ;) -Erik On Mon, Jan 3, 2011 at 3:48 AM, Karolin Krieg <[hidden email]> wrote: > > Hey Erik > > The original Orbeon.war is 50'882 KB my slimmed Orbeon.war 35'592 KB. But > still, using Orbeon.war in separate deployment Orbeon is still very big and > lots of resources are loaded which I doubt are needed?! > > batik-all-1_6.jar > --------------- > Without batik-all-1_6.jar Orbeon.war doesn't deploy any more in Liferay > 6.0.5 Portal. > I wonder if it’s really necessary and why Orbeon includes batik-all in stet > of the specific batik jars? Because some batik jars are often already > included in separate deployment. (batik-xml.jar, batik-util.jar ...) > > Orbeon jars versions > ------------------- > I guess its due to Orbeon was not designed for separate deployment that > official jars are complied in a special Orbeon version? Lots of this jars I > could remove because they are already included in Liferay Portal but with an > other version. > > xerces-xercesImpl-2_9_orbeon_20070711.jar > exist-modules-1_2_6_orbeon_20090702.jar > xerces-serializer-2_9_orbeon_20070711.jar > msv-xsdlib-20070407_orbeon_20100309.jar > msv-20081113_orbeon_20081209.jar > flyingsaucer-core-renderer_orbeon_20100512.jar > exist-ngram-module-1_2_6_orbeon_20090702.jar > antlr-2_7_4_orbeon.jar > xerces-resolver-2_9_orbeon_20070711.jar > saxpath-dev_orbeon.jar > saxon-9-1-0-8_orbeon_20101223.jar > jakarta-oro-2_0_8_orbeon.jar > exist-optional-1_2_6_orbeon_20090702.jar > exist-1_2_6_orbeon_20090702.jar > > Orbeon jars > ----------- > I wonder if Orbeon jars itself like the big orbeon-resources-public.jar can > get slimmed. There are lots of resources I doubt are really needed like: > > orbeon-resources-public.jar\ops\firebug\ > orbeon-resources-public.jar\ops\unit-tests\ > orbeon-resources-public.jar\ops\yui\examples\ > orbeon-resources-public.jar\ops\yui\yahoo\ > orbeon-resources-public.jar\ops\yui\yahoo-dom-event\ > orbeon-resources-public.jar\ops\yui\yuitest\ > ..... > > I know that depending on the system where Orbeon is integrated some jars can > get removed or not. > > I appreciate your help very much to > > Cheers > Karolin > > -- > View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Slimming-Downsize-Orbeon-war-for-Separate-Deployment-with-Portlets-tp3166132p3171875.html > Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com. > > > -- > You receive this message as a subscriber of the [hidden email] mailing list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws > > -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Free forum by Nabble | Edit this page |