Thanks for the reply. We will update the JIRA with the relevant information.
On Tue, Jul 12, 2016 at 5:20 PM, Kishanthan Thangarajah <kishant...@wso2.com > wrote: > WebContextRoot is only applicable to carbon webapp. Other webapps (store > and publisher in this case) will still be deployed under their respective > context. The issue here is with the log messages printed on to the console > which still has the web context root appended to those additional contexts > urls. That is where the fix would be. > > On Tue, Jul 12, 2016 at 4:24 PM, Chamin Dias <cham...@wso2.com> wrote: > >> Please refer : https://wso2.org/jira/browse/CARBON-15987 to track the >> fixes. >> >> Thanks >> >> On Tue, Jul 12, 2016 at 3:39 PM, Chamin Dias <cham...@wso2.com> wrote: >> >>> Hi, >>> >>> Scenario : >>> >>> 1) Change the <WebContextRoot> in carbon.xml as "/apim" (this is the >>> only change) >>> >>> 2) Start the servers and urls can be visible as below. >>> Management console url- https://localhost:9443/apim/carbon >>> Publisher url- https://localhost:9443/apim/publisher >>> Store url-https://localhost:9443/apim/store >>> >>> 3) When we tried to access the publisher and store urls, still it's >>> redirected to the management console (i.e : >>> https://localhost:9443/apim/carbon) >>> >>> >>> We have tested the same scenario for the previous APIM versions >>> (1.10,1.9.1,1.9.0,1.8.0,1.7.0,1.6.0 and 1.5.0) and noticed the same >>> behaviour. Do we need some other configuration in addition to modifying >>> <WebContextRoot> in carbon.xml? If not, we wonder if this is a known fact. >>> >>> Tested the scenario with App manager 1.1.0 as well. Observed the same >>> behaviour. >>> >>> Thanks. >>> >>> On Tue, Jul 12, 2016 at 11:47 AM, Chamin Dias <cham...@wso2.com> wrote: >>> >>>> Hi, >>>> >>>> We were working on APIMANAGER-5043 >>>> <https://wso2.org/jira/browse/APIMANAGER-5043> issue (for upcoming >>>> APIM 2.0.0 release). The issue was reproduced. We did a background search >>>> and tried the workaround suggested in the Dev mail thread : *[Dev] How >>>> to deploy Jaggery application as web root context* >>>> >>>> Unfortunately we were not able to solve the issue by following the >>>> workaround. Any help will be appreciated since we are about the release >>>> APIM 2.0.0 soon. >>>> >>>> Thanks. >>>> >>>> -- >>>> Chamin Dias >>>> *Software Engineer* >>>> Mobile : +94 (0) 716 097455 <%2B94%20%280%29%20773%20451194> >>>> Email : cham...@wso2.com >>>> Blog : https://chamindias.wordpress.com/ >>>> >>> >>> >>> >>> -- >>> Chamin Dias >>> *Software Engineer* >>> Mobile : +94 (0) 716 097455 <%2B94%20%280%29%20773%20451194> >>> Email : cham...@wso2.com >>> Blog : https://chamindias.wordpress.com/ >>> >> >> >> >> -- >> Chamin Dias >> *Software Engineer* >> Mobile : +94 (0) 716 097455 <%2B94%20%280%29%20773%20451194> >> Email : cham...@wso2.com >> Blog : https://chamindias.wordpress.com/ >> > > > > -- > *Kishanthan Thangarajah* > Technical Lead, > Platform Technologies Team, > WSO2, Inc. > lean.enterprise.middleware > > Mobile - +94773426635 > Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>* > Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>* > -- Chamin Dias *Software Engineer* Mobile : +94 (0) 716 097455 <%2B94%20%280%29%20773%20451194> Email : cham...@wso2.com Blog : https://chamindias.wordpress.com/
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
