Hi Pradeep,
Guess I managed to make a breakthrough with regard to this issue :)
I did some debugging and noticed that the AxisConfiguration for a tenant is
not getting created when a tenant login to the server. By debugging further
I managed to get the tenant's AxisConfiguration created by fixing the
ActivationHandler as follows;
shariq@shariq-laptop:~/src/trunk/platform/components/stratos/org.wso2.carbon.activation$
svn diff
Index:
src/main/java/org/wso2/carbon/activation/module/ActivationHandler.java
===================================================================
--- src/main/java/org/wso2/carbon/activation/module/ActivationHandler.java
(revision
129954)
+++ src/main/java/org/wso2/carbon/activation/module/ActivationHandler.java
(working
copy)
@@ -57,7 +57,7 @@
int tenantId = getTenantId(messageContext);
if (service != null &&
"ActivationService".equals(service.getName())) {
log.debug("Granted access to the Activation Service");
- if (tenantId > 0) {
+ if (tenantId != MultitenantConstants.SUPER_TENANT_ID) {
TenantAxisUtils.getTenantAxisConfiguration(getTenantDomain(messageContext),
messageContext.getConfigurationContext());
log.debug("Loaded Tenant Configuration");
As you can see the tenantId check is wrong. Now when the tenant login the
you will notice that the tenant AxisConfiguration is created. But still
when we deploy a service it gets deployed in ST space. This looks like an
issue in the DeploymentInterceptor, you might need to
debug DeploymentInterceptor to see what going wrong there ...
On Tue, Jun 12, 2012 at 6:19 PM, Pradeep Fernando <[email protected]> wrote:
> Hi,
>
> im working on it
>
> --Pradeep
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
--
Thanks,
Shariq.
Phone: +94 777 202 225
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
