Hi All,
I have notified that Sandesha2 module cant be engaged in the way which was
described in
[1]http://wso2.org/project/app-server/4.1.2/docs/commodity_quote_guide.html.
In the client side it shows the follwoing error,
ERROR [2012-06-21 12:19:47,991] The endpoint reference (EPR) for the
These are the Jira Issues related to this,
https://wso2.org/jira/browse/CARBON-13490
https://wso2.org/jira/browse/CARBON-13499
Thanks
AndunSLG
On Fri, Jun 22, 2012 at 1:34 PM, Andun Gunawardena an...@wso2.com wrote:
Hi All,
I have notified that Sandesha2 module cant be engaged in the way
Lakmali,
Can you please explain why we need this SuperTenantRolePlayer and why it
always returns false for isUltimateDestination()? Looks like, we can't
always return false here and have to figure out whether this is the
ultimate destination of the message. If the message is going into a tenant,
Hi,
On Fri, Jun 22, 2012 at 2:18 PM, Isuru Suriarachchi is...@wso2.com wrote:
Lakmali,
Can you please explain why we need this SuperTenantRolePlayer and why it
always returns false for isUltimateDestination()? Looks like, we can't
always return false here and have to figure out whether this
On Fri, Jun 22, 2012 at 2:42 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:
Hi,
On Fri, Jun 22, 2012 at 2:18 PM, Isuru Suriarachchi is...@wso2.comwrote:
Lakmali,
Can you please explain why we need this SuperTenantRolePlayer and why it
always returns false for isUltimateDestination()?
Hi Isuru,
On Fri, Jun 22, 2012 at 2:58 PM, Isuru Suriarachchi is...@wso2.com wrote:
On Fri, Jun 22, 2012 at 2:42 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:
Hi,
On Fri, Jun 22, 2012 at 2:18 PM, Isuru Suriarachchi is...@wso2.comwrote:
Lakmali,
Can you please explain why we need
On Fri, Jun 22, 2012 at 3:13 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:
Hi Isuru,
On Fri, Jun 22, 2012 at 2:58 PM, Isuru Suriarachchi is...@wso2.comwrote:
On Fri, Jun 22, 2012 at 2:42 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:
Hi,
On Fri, Jun 22, 2012 at 2:18 PM, Isuru
On Fri, Jun 22, 2012 at 3:47 PM, Isuru Suriarachchi is...@wso2.com wrote:
On Fri, Jun 22, 2012 at 3:13 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:
I just looked into this and looks like we can't figure out whether the
incoming request is going to a service hosted in super tenant or to a
Amila has sent the following response on 26th March 2010.
Unfortunately we can not do this since axiom method looks like this.
.setProcessed();
it does not allow to unset it.
But when I am going through the code I saw Axis2 only gets the relevant
soap headers to do the must understand header
OK, now I realize the problem. This has been there since 2010, but we
didn't deploy RM enabled services on the ST in Stratos AS, so we didn't see
the problem. After the merging, things have started to fail.
Let me think of a solution.
On Fri, Jun 22, 2012 at 8:10 PM, Afkham Azeez az...@wso2.com
The following solution came to my mind. We need to use a ThreadLocal
variable + Axis2 handler combination.
We have to introduce a TenantCheckHandler which will set a ThreadLocal
boolean variable called isSuperTenantRequest to true if it is a super
tenant request false if it is a tenant request.
Small mistake, method should be;
public boolean isUltimateDestination() {
return TenantCheckHandler.isSuperTenantRequest();
}
On Fri, Jun 22, 2012 at 8:17 PM, Afkham Azeez az...@wso2.com wrote:
The following solution came to my mind. We need to use a ThreadLocal
variable + Axis2
I think the solution is even simpler. We just need the following:
public boolean isUltimateDestination() {
return (CarbonContext.getCurrentContext().getTenantId() ==
MultitenantConstants.SUPER_TENANT_ID);
}
On Fri, Jun 22, 2012 at 8:18 PM, Afkham Azeez
This fix should work. I have committed the fix. I have verified that the
proper tenant IDs are coming into the conditions. Please verify resolve
the Jiras.
On Fri, Jun 22, 2012 at 8:24 PM, Afkham Azeez az...@wso2.com wrote:
I think the solution is even simpler. We just need the following:
Hi All,
I have verified that the issues are not there after the Revision 130953.
So resolved the issues.
Thanks
AndunSLG
On Fri, Jun 22, 2012 at 8:36 PM, Afkham Azeez az...@wso2.com wrote:
This fix should work. I have committed the fix. I have verified that the
proper tenant IDs are coming
15 matches
Mail list logo
