search

bmdhaker / share-extras

Automatically exported from code.google.com/p/share-extras
0 stars 0 forks source link

share-oauth: Way of deploying #77

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
In my opinion, JAR-modules should be able to be deployed in tomcat/shared/lib. 
The oauth module does not function until it is deployed in 
tomcat/webapps/*/WEB-INF/lib. This is in the application archive and in my 
opinion not the sustainable way.

For my knowledge, why this dependency? Can it be solved?

Kindest regards!
Koen Bonnet

Original issue reported on code.google.com by koen.bon...@contezza.nl on 23 Apr 2012 at 4:47

GoogleCodeExporter commented 8 years ago 
The reason for this requirement is solely down to the way webap class loading 
works, which means that code deployed in shared/lib has no visibility of 
classes from the webapps. For Java code this is significant, as it means you 
cannot extend webapp-provided classes.

So unfortunately, it is not possible to do it any other way, although I will 
log an enhancement for packaging those affected JARs inside an AMP, since that 
makes deploying into the webapp somewhat easier.

Original comment by will.abson on 27 Jun 2012 at 2:05