Previously, we have excluded the spring packages in Carbon from exposing to webapps. Ideally, we should exclude all these third-party dependencies that shouldn't be exposed. Then, webapp developers has the flexibility to add dependencies not limiting to wso2 provided dependency versions without facing classloading issues.
So, +1 to exclude solr packages. On Mon, Jul 6, 2015 at 2:00 PM, Niranjan Karunanandham <[email protected]> wrote: > Hi all, > > I created a simple Spring web using Spring Boot 1.1.10.RELEASE (for > integration tests in AS) and when I tried to upload the web app to AS 5.3.0 > SNAPSHOT, I get the error mentioned in JIRA [1]. I am able to upload this > same web app in AS 5.2.1. On looking into this, I found out this happens > when there is solr 5.0.0 [2]. As per the offline discussion I had with > Kasung, I was able to solve this by excluding org.apache.solr.* in the > webapp-classingloading-environments.xml > <PRODUCT_HOME>/repository/conf/tomcat) for the *Carbon* Environment which > is set as the default webapp-classloading environment. Shall we add this > (exclude org.apache.solr.* for Carbon in > webapp-classingloading-environments.xml) to the product-as pack by default? > > > [1] - https://wso2.org/jira/browse/WSAS-2000 > [2] - https://jira.spring.io/browse/DATASOLR-228 > > Regards, > Nira > > -- > > *Niranjan Karunanandham* > Senior Software Engineer - WSO2 Inc. > WSO2 Inc.: http://www.wso2.com > -- *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. email: kasung AT spamfree wso2.com linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
