Hi All,
I saw some documentation on URL mapping for applications on tenant mode in
AS 5.0.1 [1]https://docs.wso2.org/display/AS501/URL+Mapping+for+Applications
and
seems it has been removed on latest version - 5.2.1.
Is there any possible way to implement it on 5.2.1? I tried on p2 and
couldn't
Thanks Gayan and Kasun. I have updated the page [1]. Please have a look.
[1]
https://docs.wso2.org/display/DVS360/FAQ#FAQ-HowcanIavoidJavaversionproblemswhencreatingaxis2servicesanddeployinginAS
?
Thanks,
Tania
On Tue, May 13, 2014 at 11:11 AM, Kasun Gajasinghe kas...@wso2.com wrote:
On
Hi ESB Team,
Please apply the pull request -
https://github.com/wso2-dev/product-esb/pull/12
Thanks,
Nuwanw
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
https://github.com/wso2/carbon-utils
--
Best Regards,
Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/
WSO2, Inc.
lean .
For Dev Studio we have to keep a consistent look for a given set of icons
for a given category. Ex: Endpoints, Extension etc... That's why they all
are in the same color. We can keep these icons for Dev Studio and color up
the icons that you guys need for the connector store to make them sync up
carbon-utils repo should be merged with carbon-commons.
On Tue, May 13, 2014 at 1:30 PM, Malaka Silva mal...@wso2.com wrote:
https://github.com/wso2/carbon-utils
--
Best Regards,
Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype :
Hi,
For inbound endpoint hot deployment [1] class is being used. However when I
touch the file updateSynapseArtifact() is not called. Also
undeploySynapseArtifact() is not called when file is deleted.
Anything else we need to do to support hot deployments? Do we need to
register this?
1)
All new deployers should be registered with Axis2 deployment engine before
it can be used. I think in synapse case, all the artifact deployers are
registered via the ServiceBusInitializer.
On Tue, May 13, 2014 at 2:52 PM, Malaka Silva mal...@wso2.com wrote:
Hi,
For inbound endpoint hot
Hi,
I couldn't build the Endpoint Look-up Sample alone. Only after I built the
product 4.6.0 I was able to build it.
Following is the build failure.
[INFO]
[INFO] BUILD FAILURE
[INFO]
Hi All,
Following updates has been discussed on $subject.
1) The isCoordinator check is not necessary for publishing the cache
invalidation message.
2) Separate the implementation of publisher and subscriber into 2 classes.
3) Alter the implementation to support, when the isCoordinator node goes
Hi Manoj,
Please apply the patch attached in [1] to the location in [2] (patch0008).
@Asela/@Prabath, would be great if you could review this fix as well please.
[1] - https://wso2.org/jira/browse/IDENTITY-2385
[2] -
Hi Shazni,
I have updated the code with aforesaid changes in my git fork
[1]https://github.com/amalhub/carbon4-kernel/commit/7d1711a6de7ebf04e22ec1e9634e88088b954c4f
.
Please run the tests on your clustered setup.
[1]
On Tue, May 13, 2014 at 4:30 PM, Amal Gunatilake am...@wso2.com wrote:
Hi All,
Following updates has been discussed on $subject.
1) The isCoordinator check is not necessary for publishing the cache
invalidation message.
2) Separate the implementation of publisher and subscriber into 2
Hi Amal,
Messages are not getting received after this modification. I noticed very
less number of messages getting published too. No modification on registry
kernel side is made.
Shazni Nazeer
Senior Software Engineer
Mob : +94 715 440 607
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog
After changing the cert in the ELB we were able to achieve the mutual auth
between ELB and AS. But the requirement was to get the auth working between
ESB and the AS (bypassing the ELb). For this, the ideal solution would be
SSL Tunneling. So I'll investigate on that topic and see what we can do.
Hi,
Getting the following.
[ERROR] The build could not read 1 project - [Help 1]
[ERROR]
[ERROR] The project
org.wso2.carbon:product-releases-features:4.2.0-chunk11
(/home/dulanja/work/repos/svn/carbon/platform/branches/turing/product-releases/chunk-11/features/pom.xml)
has 1 error
[ERROR]
Thanks Ruwan!
On Tue, May 13, 2014 at 6:38 PM, Ruwan Yatawara ruw...@wso2.com wrote:
Hi Dulanja,
This should be fixed now. Please take an update.
Thanks and Regards,
Ruwan Yatawara
WSO2 Inc.
email : ruw...@wso2.com
mobile : +94 77 9110413
blog : http://thoughts.ruwan-ace.com/
www:
Hello all,
Isuru and I had a look at this, and we found the reason for this behaviour
is to do with the isRest property not being set to true - by default when
we send text/xml we assume that the invocation is not rest and therefor is
a SOAP service invocation.
The problem with this is that a
Hi guys,
Looks like format support is already there for HTTP Endpoint - just not in
the UI. We can add the attribute format=rest to solve this issue. :)
Thanks
On Tue, May 13, 2014 at 6:51 PM, Ravi Undupitiya r...@wso2.com wrote:
Hello all,
Isuru and I had a look at this, and we found the
On Tue, May 13, 2014 at 6:55 PM, Ravi Undupitiya r...@wso2.com wrote:
Hi guys,
Looks like format support is already there for HTTP Endpoint - just not in
the UI. We can add the attribute format=rest to solve this issue. :)
I think we can include this in the http endpoint getting created for
-1
HTTP EP is designed for outbound REST calls. So putting format=rest, is
meaningless and hinders its whole purpose. We need to find a better
alternative. May be we have to filter-out SOAP vs POX at the
Axis2FlexibleMEPClient level ?
On Wed, May 14, 2014 at 1:25 AM, Ravi Undupitiya
Hi Kasun,
At present the Axis2FlexibleMEPClient detects a REST request by checking
the HTTP method used and if the content type belongs to any of the
following:
application/xml
application/x-www-form-urlencoded
multipart/form-data
application/json
If the HTTP method is anything other than POST -
I think at axis2 level we already do this (identifying soap vs pox based on
Action). Can't we do the same?
On Wed, May 14, 2014 at 2:05 AM, Ravi Undupitiya r...@wso2.com wrote:
Hi Kasun,
At present the Axis2FlexibleMEPClient detects a REST request by checking
the HTTP method used and if the
Hi Kasun,
On Tue, May 13, 2014 at 7:35 PM, Ravi Undupitiya r...@wso2.com wrote:
Hi Kasun,
At present the Axis2FlexibleMEPClient detects a REST request by checking
the HTTP method used and if the content type belongs to any of the
following:
application/xml
On Fri, Apr 25, 2014 at 3:26 PM, Sagara Gunathunga sag...@wso2.com wrote:
On Wed, Apr 23, 2014 at 1:03 PM, Madhuka Udantha madh...@wso2.com wrote:
On Tue, Apr 22, 2014 at 11:43 AM, Udara Rathnayake uda...@wso2.comwrote:
Hi all,
At the moment we do have our products within
TID: [0] [SCC] [2014-05-13 20:54:52,103] ERROR
{org.wso2.carbon.transaction.manager.TransactionManagerComponent} - Error
in binding transaction manager for tenant: 12
{org.wso2.carbon.transaction.manager.TransactionManagerComponent}
java.lang.RuntimeException: An error occurred while creating
Hi,
On Tue, May 13, 2014 at 8:55 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:
TID: [0] [SCC] [2014-05-13 20:54:52,103] ERROR
{org.wso2.carbon.transaction.manager.TransactionManagerComponent} - Error
in binding transaction manager for tenant: 12
Hi all,
Noticed following error after adding the toolbox deployment feature plus
latest BAM publisher dependencies in to the social framework. I'm using
embedded Cassandra node within ES.
ERROR {me.prettyprint.cassandra.connection.NodeDiscovery} - Discovery
Service failed attempt to connect
Hi Udara,
This is a known bug in Hector. It's a missing null check. But we don't have
to worry about it, because this does not impact anything. And this is fixed
in next version of Hector. For now, as a workaround you can change the log
level. Better to make it FATAL rather than OFF.
Thanks,
On Tue, May 13, 2014 at 9:19 PM, Melan Nimesh me...@wso2.com wrote:
Hi,
On Tue, May 13, 2014 at 8:55 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:
TID: [0] [SCC] [2014-05-13 20:54:52,103] ERROR
{org.wso2.carbon.transaction.manager.TransactionManagerComponent} - Error
in binding
Hi,
I am getting the following build failure.
[INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @
org.wso2.carbon.apimgt.impl ---
[INFO] Compiling 102 source files to
What is your Java version?
Try using Oracle JDK 6?
On Tue, May 13, 2014 at 3:21 PM, Shani Ranasinghe sh...@wso2.com wrote:
Hi,
I am getting the following build failure.
[INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @
org.wso2.carbon.apimgt.impl ---
[INFO] Compiling
Hi,
yes, I am building a development branch. the latest version for the
component.
Java version 1.7
On Tue, May 13, 2014 at 3:23 PM, Isuru Perera isu...@wso2.com wrote:
What is your Java version?
Try using Oracle JDK 6?
On Tue, May 13, 2014 at 3:21 PM, Shani Ranasinghe sh...@wso2.com
Same error is mentioned here in *API Manager build failure in 4.2.0
support branch* which should be solved by building the kernel patch.
Thanks,
Bhathiya
On Tue, May 13, 2014 at 3:25 PM, Shani Ranasinghe sh...@wso2.com wrote:
Hi,
yes, I am building a development branch. the latest version
Hi Bhathiya,
Yes as mentioned in the mail it was the kernel patch, which was not
correctly built. Thanks for pointing this out.
On Tue, May 13, 2014 at 3:31 PM, Shani Ranasinghe sh...@wso2.com wrote:
Thanks Bhathiya. Will check.
On Tue, May 13, 2014 at 3:28 PM, Bhathiya Jayasekara
sent from my nexus4, ignore any typos
On May 14, 2014 2:27 AM, Bhathiya Jayasekara bhath...@wso2.com wrote:
Hi Udara,
This is a known bug in Hector. It's a missing null check. But we don't
have to worry about it, because this does not impact anything. And this is
fixed in next version of
Hi All,
Please find the $subject at:
http://ec2-54-198-211-48.compute-1.amazonaws.com/chunk11/13-05-2014/
Built from revision: 202760.
Thanks
Dulanja
--
Dulanja Liyanage
WSO2 Inc.
M: +94776764717
___
Dev mailing list
Dev@wso2.org
Hi Shazni,
Let's go with the notification based mechanism as Azeez suggested.
Hi Azeez,
Please let me know where is the interface located and which dataholder
holds the osgi service.
Thank you Best regards,
*Amal Gunatilake*
Software Engineer
WSO2 Inc.; http://wso2.com
38 matches
Mail list logo
