Hi Isomorphic,
I'm testing SmartGWT for quite a time now and plan to do a B2B webapp. While doing so I started with the BuiltInDS example added Oracle and Relogin support, switched from Dev To SuperDev and am now playing around with the declarative security.
All the time I was wondering if its possible to shorten the undeploy-build-war-deploy cycle. Today I found out that Tomcat has shared libs for all apps it hosts. I already put my ODBC driver there but didn't think of that I could also put my smartgwt jars there.
Today I tried it with the following line in my catalina.properties:
I changed my ANT targets for clean and lib to clean there and copy the needed files there, as well as my war-target to ignore the apps WEB-INF/lib-files I copied (resulting in an empty WEB-INF/lib dir).
So far this works like a charm, the app's war-file is way smaller than it used to be and the war is build and deployed faster.
Do you know if this approach (resulting in shared SmartGWT jars if I might run more than one app sometime) has any downsides (with respect to shared instances, not with the "jar hell", I'm aware of these)?
I'm aware that this question is not really SmartGWT question, so I'm also fine with trial and error if you can't say anything here.
Best regards,
Blama
PS: I also saw http://www.smartclient.com/smartgwte...endencies.html today and will look into it to reduce my jar-footprint. Your framework is REALLY impressive.
I'm testing SmartGWT for quite a time now and plan to do a B2B webapp. While doing so I started with the BuiltInDS example added Oracle and Relogin support, switched from Dev To SuperDev and am now playing around with the declarative security.
All the time I was wondering if its possible to shorten the undeploy-build-war-deploy cycle. Today I found out that Tomcat has shared libs for all apps it hosts. I already put my ODBC driver there but didn't think of that I could also put my smartgwt jars there.
Today I tried it with the following line in my catalina.properties:
Code:
common.loader=${catalina.base}/lib,${catalina.base}/lib/*.jar,\ ${catalina.home}/lib,${catalina.home}/lib/*.jar,\ ${catalina.base}/lib/common,${catalina.base}/lib/common/*.jar,\ ${catalina.home}/lib/common,${catalina.home}/lib/common/*.jar,\ ${catalina.base}/lib/common/SmartGWT,${catalina.base}/lib/common/SmartGWT/*.jar,\ ${catalina.home}/lib/common/SmartGWT,${catalina.home}/lib/common/SmartGWT/*.jar
So far this works like a charm, the app's war-file is way smaller than it used to be and the war is build and deployed faster.
Do you know if this approach (resulting in shared SmartGWT jars if I might run more than one app sometime) has any downsides (with respect to shared instances, not with the "jar hell", I'm aware of these)?
I'm aware that this question is not really SmartGWT question, so I'm also fine with trial and error if you can't say anything here.
Best regards,
Blama
PS: I also saw http://www.smartclient.com/smartgwte...endencies.html today and will look into it to reduce my jar-footprint. Your framework is REALLY impressive.
Comment