Re: [Dev] Creating A Custom Mediator For XSLT Transfomation : Binary Relay Enabled ESB
/05/soap-envelope;soapenv:Bodyns:binary xmlns:ns=http://ws.apache.org/commons/ns/payload PD94bWwgdmVyc2lvbj0nMS4wJyBlbmNvZGluZz0nVVRGLTgnPz48c29hcGVudjpFbnZlbG9wZSB4bWxuczpzb2FwZW52PSJodHRwOi8vc2NoZW1hcy54bWxzb2FwLm9yZy9zb2FwL2VudmVsb3BlLyI+PHNvYXBlbnY6SGVhZGVyIHhtbG5zOndzYT0iaHR0cDovL3d3dy53My5vcmcvMjAwNS8wOC9hZGRyZXNzaW5nIj48d3NhOlRvPmh0dHA6Ly9sb2NhbGhvc3Q6OTAwMC9zZXJ2aWNlcy9TaW1wbGVTdG9ja1F1b3RlU2VydmljZTwvd3NhOlRvPjx3c2E6TWVzc2FnZUlEPnVybjp1dWlkOjBmNzQwM2I0LWM1YmMtNDM0Ny04OTIxLTU2MmYyNzM2YTJhYjwvd3NhOk1lc3NhZ2VJRD48d3NhOkFjdGlvbj51cm46Z2V0UXVvdGU8L3dzYTpBY3Rpb24+PC9zb2FwZW52OkhlYWRlcj48c29hcGVudjpCb2R5PjxtMDpDaGVja1ByaWNlUmVxdWVzdCB4bWxuczptMD0iaHR0cDovL3NlcnZpY2VzLnNhbXBsZXMiPjxtMDpDb2RlPklCTTwvbTA6Q29kZT48L20wOkNoZWNrUHJpY2VSZXF1ZXN0Pjwvc29hcGVudjpCb2R5Pjwvc29hcGVudjpFbnZlbG9wZT4=/ns:binary/soapenv:Body/soapenv:Envelope .Original SOAP Message soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header xmlns:wsa= http://www.w3.org/2005/08/addressing;wsa:To http://localhost:9000/services/SimpleStockQuoteService/wsa:Towsa:MessageIDurn:uuid:0f7403b4-c5bc-4347-8921-562f2736a2ab/wsa:MessageIDwsa:Actionurn:getQuote/wsa:Action/soapenv:Headersoapenv:Bodym0:CheckPriceRequest xmlns:m0=http://services.samples m0:CodeIBM/m0:Code/m0:CheckPriceRequest/soapenv:Body/soapenv:Envelope Transforming On Progress. ...Transformed SOAP Message... m:getQuote xmlns:m=http://services.samples; m:request m:symbolIBM/m:symbol /m:request /m:getQuote .. ...Transformed SOAP Envelop.. ?xml version='1.0' encoding='utf-8'?soapenv:Envelope xmlns:soapenv= http://www.w3.org/2003/05/soap-envelope;soapenv:Bodyns:binary xmlns:ns=http://ws.apache.org/commons/ns/payload PG06Z2V0UXVvdGUgeG1sbnM6bT0iaHR0cDovL3NlcnZpY2VzLnNhbXBsZXMiPgogICA8bTpyZXF1ZXN0PgogICAgICA8bTpzeW1ib2w+SUJNPC9tOnN5bWJvbD4KICAgPC9tOnJlcXVlc3Q+CjwvbTpnZXRRdW90ZT4K/ns:binary/soapenv:Body/soapenv:Envelope .. -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 Any suggestions to overcome this problem ? Thanks AndunSLG [1] http://wso2.org/svn/browse/wso2/carbon/platform/branches/4.0.0/dependencies/synapse/2.1.0-wso2v7/modules/core/src/main/java/org/apache/synapse/mediators/transform/XSLTMediator.java?view=markup ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Mayhem Lab/RACE Lab; Dept. of Computer Science, UCSB; http://cs.ucsb.edu E-mail: hira...@cs.ucsb.edu hira...@wso2.com; Mobile: +1 (805) 895-7443 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Creating A Custom Mediator For XSLT Transfomation : Binary Relay Enabled ESB
On Sat, Sep 15, 2012 at 5:19 PM, Hiranya Jayathilaka hiranya...@gmail.comwrote: I don't know for sure whether this problem can be solved. But sometime back I wrote a custom mediator to do XSLT transformations using the StAX support available in the Java TrAX API. It showed a fairly good performance improvement against the existing implementation too. Solving the problem mentioned in this thread will be pretty hard. Perhaps we can relax the conditions a bit. We can wrap the output of the transformation in a SOAP envelope and put that back in the data handler. We will use s/use/loose/ any information in the original SOAP headers, but that won't be an issue for most practical scenarios. Thanks, Hiranya On Sat, Sep 15, 2012 at 9:23 AM, Andun Sameera an...@wso2.com wrote: Hi Amila, On Sat, Sep 15, 2012 at 9:22 PM, Amila Suriarachchi am...@wso2.comwrote: Does xslt engine supports xml stream level transformations? Yes. But not 100% streams, but we can transform StreamSource object to a StreamResult using the Transformer. After xslt transformations users may want to do further processing with the message. So in that case we can avoid building request Axiom object but may required to create the transformed Axiom object. Yes your argument is correct, sometimes we have to create the result message. But I got in to trouble even before. In the present scenario, XSLT mediator read some parameters from the request using AXIOM. It read weather transformation is happening to SOAP body or SOAP envelop etc. Based on those parameters after the transformation mediator reform the message. You can fine that logic in [1]http://wso2.org/svn/browse/wso2/carbon/platform/branches/4.0.0/dependencies/synapse/2.1.0-wso2v7/modules/core/src/main/java/org/apache/synapse/mediators/transform/XSLTMediator.java?view=markup . But here I have no such parameters, I have only a input stream and I transform it using the XSLT file. After transformation I have no clue to reform the message. What I do is set the output stream to the data-handler in binary relay dummy message. So some parts of the original message get dropped and everything crashes here after. thanks, Amila. On Sat, Sep 15, 2012 at 4:16 PM, Andun Sameera an...@wso2.com wrote: Hi All, My requirement is $Subject. Purpose of this is avoid using AXIOM to to XSLT transformation. Our plan was to do all the transformation using Input, Output Streams. javax.xml.transform.Transformer is used to do the transformation using streams. I developed the mediator using the following logic, - In the Binary Relay We get the Message as a Data Handler in a Dummy SOAP Message. From that we can get a Input Stream for the SOAP message which needs to be transformed using XSLT. - We can Get the input Stream for the XSLT file, which is in registry or local. - Using those two we can do the XSLT transformation. As a result we get a stream for the transformed SOAP message. - Finally I create a DataHandler using the stream and attached it to the Relay's Dummy SOAP message replacing existing one. The output of the mediator follows this logic is given below. I used the Sample 8http://wso2.org/project/esb/java/4.0.3/docs/samples/message_mediation_samples.html#Sample8of ESB. I replaced the XSLT mediator with my custom mediator in the Binary Relay. But there is a major problem here. Because of the logic we used the original SOAP message, soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header xmlns:wsa= http://www.w3.org/2005/08/addressing;wsa:To http://localhost:9000/services/SimpleStockQuoteService/wsa:Towsa:MessageIDurn:uuid:0f7403b4-c5bc-4347-8921-562f2736a2ab/wsa:MessageIDwsa:Actionurn:getQuote/wsa:Action/soapenv:Headersoapenv:Bodym0:CheckPriceRequest xmlns:m0=http://services.samples m0:CodeIBM/m0:Code/m0:CheckPriceRequest/soapenv:Body/soapenv:Envelope is now converted to. m:getQuote xmlns:m=http://services.samples; m:request m:symbolIBM/m:symbol /m:request /m:getQuote At the end Binary Relay Formatter will read the DataHandler and above SOAP message will be sent to the AXIS2 Server and It will crash, because this is not a valid SOAP message. This problem occurs because we are not using AXIOM anymore. In the normal XSLT mediator it uses org.apache.synapse.util.xpath.SourceXPathSupport class to find the part of the message which transformed using XSLT. So it can replace the transformed part of the original message. But here we cant use that kind of a logic. Because we use only streams. We cant build OMElements or etc. Need help to solve this problem. The custom mediator java files are attached here. Thanks AndunSLG References : [1] - http://wso2.org/project/esb/java/4.0.3/docs/samples/message_mediation_samples.html#Sample8 Console Output for the Custom Mediator : .Original SOAP Envelop
Re: [Dev] [API Manager]-Need small help to understand key validation logic
OK understood. Thanks.
-Hiranya
On Thu, Aug 30, 2012 at 11:28 AM, Sumedha Rubasinghe sume...@wso2.comwrote:
Hiranya,
Sanjeewa's concern is coming from an intermediate piece of code that went
into custom branch location.
I just went through the code with Lalaji. It seems the new logic added is
not relevant to this context. Let me explain in detail.
As part of a fulfilling a customer requirement, we are adding basic token
refresh functionality. So the logic that should be implemented is as
follows:
1. Subscriber requests for a token to be refreshed.
2. Check if a token exists for the given criteria
3. If #2 is true, regenerate a new token
4. Check if token mentioned in #2 is in the gateway cache. If yes, remove
it from cache
5. Persist the new token
This is a basic implementation of token refresh functionality where
following factors have not been addressed:
1. A refreshed token will have it's validity period extended by the
globally configured time period
2. Any subscriber having a valid login can get his application's token
refreshed (we do not have monetization capabilities as of now)
Lalaji will refactor the implementation to remove newly added lines from
'getKeyValidationInfo' method.
On Thu, Aug 30, 2012 at 10:56 AM, Hiranya Jayathilaka
hiranya...@gmail.com wrote:
Where does this piece of code come from? I looked at the APIKeyValidator
class in 1.0.0 branch and this is the full implementation of the method:
public APIKeyValidationInfoDTO getKeyValidationInfo(String context, String
apiKey,
String apiVersion)
throws APISecurityException {
String cacheKey = apiKey + : + context + : + apiVersion;
APIKeyValidationInfoDTO info = (APIKeyValidationInfoDTO)
infoCache.get(cacheKey);
if (info != null) {
return info;
}
synchronized (apiKey.intern()) {
// We synchronize on the API key here to allow concurrent
processing
// of different API keys - However when a burst of requests with
the
// same key is encountered, only one will be allowed to execute
the logic,
// and the rest will pick the value from the cache.
info = (APIKeyValidationInfoDTO) infoCache.get(cacheKey);
if (info != null) {
return info;
}
info = doGetKeyValidationInfo(context, apiVersion, apiKey);
if (info != null) {
infoCache.put(cacheKey, info);
return info;
} else {
throw new
APISecurityException(APISecurityConstants.API_AUTH_GENERAL_ERROR,
API key validator returned null);
}
}
}
Looks very different from what you have posted.
Thanks,
Hiranya
On Thu, Aug 30, 2012 at 5:17 AM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Hi All,
Can someone please help me to understand following part of code in API
manager component.
Following method is available inside APIKeyValidator class. There i can
see we check in database
even we had cached key. AFAIU isAccessTokenExists() method should not
call if info object is
not null. Also we can see same code repeated inside synchronized block
and outside it. My suggestion
is we shouldn't look at db for each api call as far as we have cached
info(this adds additional overhead).
Also we have to remove repeated code from synchronized block.
public APIKeyValidationInfoDTO getKeyValidationInfo(String context,
String apiKey,String apiVersion) throws APISecurityException {
String cacheKey = apiKey + : + context + : + apiVersion;
APIKeyValidationInfoDTO info = (APIKeyValidationInfoDTO)
infoCache.get(cacheKey);
ApiMgtDAO dao=new ApiMgtDAO();
try {
if (info != null) {
if (dao.isAccessTokenExists(apiKey)) {
This call doesn't make any sense because its just check is there a token
in IDN_OAUTH2_ACCESS_TOKEN table.
SQL SELECT ACCESS_TOKEN FROM IDN_OAUTH2_ACCESS_TOKEN WHERE
ACCESS_TOKEN= apikey
if we have cached info object associated with that token then obviously
that token is in database as well. Please
correct me if i understood this in a wrong way.
Thanks.
--
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +14084122715 | +94713068779
http://sanjeewamalalgoda.blogspot.com/blog
:http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.; http://wso2.org
E-mail: hira...@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
--
/sumedha
m: +94 773017743
b : bit.ly/sumedha
--
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.; http://wso2.org
E-mail: hira
Re: [Dev] FailOver endpoint is failing to invoke FailOver Logic for special Error Codes
),
null);
Assert.assertNotNull(response);
Assert.assertTrue(response.toString().contains(Response from
server: Server_1));
//Stop one server to generate a failure in one endpoint
//But the suspend cant be triggered here. because suspend the
endpoint happen only for Timeouts 101504,101508
axis2Server1.stop();
response =
lbClient.sendLoadBalanceRequest(getProxyServiceURL(failoverEndPoint_Specific_Errors),
null);
Assert.assertNotNull(response);
Assert.assertTrue(response.toString().contains(Response from
server: Server_2));
axis2Server1.start();
int counter=0;
while(!AxisServiceClientUtils.isServiceAvailable(
http://localhost:9001/services/LBService1;)) {
if(counter100){
break;
}
counter++;
}
if(counter100){
throw new AssertionError(Axis2 Server didn't started with
in expected time period.) ;
}
else{
//Checaxiaxis2Server1.start()s2Server1.stop()k that the
endpoint one is not suspended.
//If reply comes that means not suspended.
//Because suspend duration of the endpoint is 20 seconds. So
reply cant come in this time.
response =
lbClient.sendLoadBalanceRequest(getProxyServiceURL(failoverEndPoint_Specific_Errors),
null);
Assert.assertNotNull(response);
Assert.assertTrue(response.toString().contains(Response
from server: Server_1));
//Invoke a web service method which will invoke a time out
and cause the endpoint to suspend.
response =
lbClient.sendSleepRequest(getProxyServiceURL(failoverEndPoint_Specific_Errors),4000);
Assert.assertNotNull(response);
Assert.assertTrue(response.toString().contains(Response
from server: Server_2));
//Invoke a web service method which will invoke a time out
and cause the endpoint to suspend.
response =
lbClient.sendLoadBalanceRequest(getProxyServiceURL(failoverEndPoint_Specific_Errors),
null);
Assert.assertNotNull(response);
Assert.assertTrue(response.toString().contains(Response
from server: Server_2));
}
}
--
Dushan Abeyruwan
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/*
*Mobile:(+94)714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.; http://wso2.org
E-mail: hira...@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API Manager]-Need small help to understand key validation logic
Where does this piece of code come from? I looked at the APIKeyValidator
class in 1.0.0 branch and this is the full implementation of the method:
public APIKeyValidationInfoDTO getKeyValidationInfo(String context,
String apiKey,
String
apiVersion) throws APISecurityException {
String cacheKey = apiKey + : + context + : + apiVersion;
APIKeyValidationInfoDTO info = (APIKeyValidationInfoDTO)
infoCache.get(cacheKey);
if (info != null) {
return info;
}
synchronized (apiKey.intern()) {
// We synchronize on the API key here to allow concurrent processing
// of different API keys - However when a burst of requests with the
// same key is encountered, only one will be allowed to
execute the logic,
// and the rest will pick the value from the cache.
info = (APIKeyValidationInfoDTO) infoCache.get(cacheKey);
if (info != null) {
return info;
}
info = doGetKeyValidationInfo(context, apiVersion, apiKey);
if (info != null) {
infoCache.put(cacheKey, info);
return info;
} else {
throw new
APISecurityException(APISecurityConstants.API_AUTH_GENERAL_ERROR,
API key validator returned null);
}
}
}
Looks very different from what you have posted.
Thanks,
Hiranya
On Thu, Aug 30, 2012 at 5:17 AM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Hi All,
Can someone please help me to understand following part of code in API
manager component.
Following method is available inside APIKeyValidator class. There i can
see we check in database
even we had cached key. AFAIU isAccessTokenExists() method should not
call if info object is
not null. Also we can see same code repeated inside synchronized block and
outside it. My suggestion
is we shouldn't look at db for each api call as far as we have cached
info(this adds additional overhead).
Also we have to remove repeated code from synchronized block.
public APIKeyValidationInfoDTO getKeyValidationInfo(String context, String
apiKey,String apiVersion) throws APISecurityException {
String cacheKey = apiKey + : + context + : + apiVersion;
APIKeyValidationInfoDTO info = (APIKeyValidationInfoDTO)
infoCache.get(cacheKey);
ApiMgtDAO dao=new ApiMgtDAO();
try {
if (info != null) {
if (dao.isAccessTokenExists(apiKey)) {
This call doesn't make any sense because its just check is there a token
in IDN_OAUTH2_ACCESS_TOKEN table.
SQL SELECT ACCESS_TOKEN FROM IDN_OAUTH2_ACCESS_TOKEN WHERE
ACCESS_TOKEN= apikey
if we have cached info object associated with that token then obviously
that token is in database as well. Please
correct me if i understood this in a wrong way.
Thanks.
--
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +14084122715 | +94713068779
http://sanjeewamalalgoda.blogspot.com/blog
:http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.; http://wso2.org
E-mail: hira...@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ERROR on ESB when updating Synapse Configuration consecutively.
(SequenceDeployer.java:154) ... 19 more [2012-08-27 13:18:14,018] INFO - AbstractSynapseArtifactDeployer Restoring the artifact into the file : /home/nuwanw/svn/carbon/platform/branches/4.0.0/products/esb/4.5.0/modules/integration/tests/target/carbontmp1346053341660/wso2esb-4.5.0/repository/deployment/server/synapse-configs/default/sequences/main.xml [2012-08-27 13:18:14,024] INFO - SequenceDeployer Sequence named 'main' has been restored [2012-08-27 13:18:14,024] WARN - MediationPersistenceManager Mediation persistence manager is either not initialized or not in the 'accepting' mode. Ignoring the save request. [2012-08-27 13:18:17,096] INFO - SynapseTaskManager Shutting down the task manager [2012-08-27 13:18:17,098] INFO - XMLConfigurationBuilder Generating the Synapse configuration model by parsing the XML configuration [2012-08-27 13:18:17,099] ERROR - MultiXMLConfigurationSerializer Error while serializing the configuration to the file system java.nio.channels.ClosedByInterruptException at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:184) at sun.nio.ch.FileChannelImpl.size(FileChannelImpl.java:314) at org.apache.commons.io.FileUtils.doCopyFile(FileUtils.java:808) at org.apache.commons.io.FileUtils.doCopyDirectory(FileUtils.java:1094) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1055) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:927) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:896) at org.apache.synapse.config.xml.MultiXMLConfigurationSerializer.serialize(MultiXMLConfigurationSerializer.java:119) at org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.saveFullConfiguration(MediationPersistenceManager.java:497) at org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.persistElement(MediationPersistenceManager.java:443) at org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.access$1400(MediationPersistenceManager.java:51) at org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager$MediationPersistenceWorker.run(MediationPersistenceManager.java:422) [2012-08-27 13:18:22,561] INFO - SynapseTaskManager Shutting down the task manager [2012-08-27 13:18:22,567] INFO - XMLConfigurationBuilder Generating the Synapse configuration model by parsing the XML configuration [2012-08-27 13:18:22,569] ERROR - MultiXMLConfigurationSerializer Error while serializing the configuration to the file system java.nio.channels.ClosedByInterruptException at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:184) at sun.nio.ch.FileChannelImpl.size(FileChannelImpl.java:314) at org.apache.commons.io.FileUtils.doCopyFile(FileUtils.java:808) at org.apache.commons.io.FileUtils.doCopyDirectory(FileUtils.java:1094) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1055) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:927) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:896) at org.apache.synapse.config.xml.MultiXMLConfigurationSerializer.serialize(MultiXMLConfigurationSerializer.java:119) at org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.saveFullConfiguration(MediationPersistenceManager.java:497) at org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.persistElement(MediationPersistenceManager.java:443) at org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.access$1400(MediationPersistenceManager.java:51) at org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager$MediationPersistenceWorker.run(MediationPersistenceManager.java:422) -- Nuwan Wimalasekara Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API-Manager-1.0.0] Change of Tier type NOT gets effective on subscribers end
On Mon, Aug 13, 2012 at 11:14 AM, Sumedha Rubasinghe sume...@wso2.comwrote: On Mon, Aug 13, 2012 at 10:26 AM, Subash Chaturanga sub...@wso2.comwrote: On Mon, Aug 13, 2012 at 5:45 AM, Sumedha Rubasinghe sume...@wso2.comwrote: In a nutshell, we store the tier selected as part of user's subscription record. So even if you change the tier @ API level, that change does not propagate to the subscriber unless you update the subscription with new tier details. Hi Sumedha, I tried to do similar kind of thing. But there was no such. WDYM updating the subscription ? The only option there is to resubscribe. Still the application bounded is not available there. I was referring to removing ur subscription from the application. However, if you change a value in an existing tier, (eg: changing max request count) this gets picked up without having to update the subscription. On Mon, Aug 13, 2012 at 12:08 AM, Hiranya Jayathilaka hira...@wso2.comwrote: It's not natural for the API provider to change a tier of an API all the sudden, without the consent of the subscribers. Tier is a contract between the API provider and the subscriber. Subscriber chooses a tier at the point of subscription, after carefully reviewing it. The provider is supposed to keep supporting that. However if it must be done here are your options: Hi Hiranya, Yes, the subscriber chooses the tier at the point of subscription. But [1] - When provider changes the tier value, the value of the tier at subscriber end gets updated. So if this is the expected behavior, [1] is a bug and we should not allow the publisher to change the tier or provide some alternative.. Because that particular tier has dependent subscribers. AFAIC this not a bug. But more of a mutual understanding. If a provider decides to change it's SLA on a tier, propagating that is not a problem. Yes I agree. It's a more of a common sense issue. I don't see why anybody would want to change a tier for which customers have already subscribed. However if somebody really wants to do that, he need to go through a bit of trouble to make that happen. Thanks, Hiranya I think $subject is a possible use case a publisher may come across. As API-M provides API versioning capability it is not good to have multiple tiers per API at API creation. Hence, a possible suggestion is, we can recommend the publishers/subs, if they need $subject, you should go for a new version of the API with the changes and may be deprecate the previous. In that context, we can make the tier type *not* editable for publisher. WDYT ? Multiple tiers are there to introduce different SLAs (and pricing plans). When publishing an API, publisher selects under what categories his API will be exposed @. And when subscribing, subscribers decide what is the service level they expect/budget and the decide on the tier to subscribe to. 1. Change the tier definitions by editing the tiers.xml in registry 2. Update the subscription entry in API Manager DB Thanks, Hiranya On Sun, Aug 12, 2012 at 11:02 PM, Subash Chaturanga sub...@wso2.comwrote: Hi all, I just noticed $subject in 1.0.0 release. Once I change the tier type of my API from Bronze to Silver I could still send only one request per minute. More than one requests, it gives the same old throttled out response. Same applies when transform from Silver to Gold. Is this a known issue ? To change the tier type, I did that from publisher edit tab and saved, is there anything more to be done for that to be effective ? Thanks -- Subash Chaturanga Software Engineer WSO2 Inc. http://wso2.com email - sub...@wso2.com phone - 077 2225922 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- /sumedha +94 773017743 -- Subash Chaturanga Software Engineer WSO2 Inc. http://wso2.com email - sub...@wso2.com phone - 077 2225922 -- /sumedha +94 773017743 -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Changing JIRA project name of API Manager
On Mon, Aug 13, 2012 at 12:08 PM, Samisa Abeysinghe sam...@wso2.com wrote:
On Mon, Aug 13, 2012 at 12:00 PM, Sumedha Rubasinghe sume...@wso2.comwrote:
Project ID will be either AM or APIMANAGER. Name remains the same ('WSO2
API Manager https://wso2.org/jira/browse/APISTORE').
There will be components to reflect store, publisher, gateway, etc..
+1 for creating a new one.
+1 for APIMANAGER and the suggested components.
On Mon, Aug 13, 2012 at 11:56 AM, Samisa Abeysinghe sam...@wso2.comwrote:
What is the new name?
On Mon, Aug 13, 2012 at 11:54 AM, Sumedha Rubasinghe
sume...@wso2.comwrote:
Due to historical reasons JIRA project id for API Manager is 'APISTORE'
- https://wso2.org/jira/browse/APISTORE. JIRA doesn't allow us to
change the string 'APISTORE' once used.
During one of the discussions, it was decided to change this after
1.0.0 release. I am thinking of doing this now moving all unresolved
issues to new project. Any concerns?
--
/sumedha
+94 773017743
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Thanks,
Samisa...
Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
--
/sumedha
+94 773017743
Thanks,
Samisa...
Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Hiranya Jayathilaka
Senior Technical Lead;
WSO2 Inc.; http://wso2.org
E-mail: hira...@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API-Manager-1.0.0] Change of Tier type NOT gets effective on subscribers end
It's not natural for the API provider to change a tier of an API all the sudden, without the consent of the subscribers. Tier is a contract between the API provider and the subscriber. Subscriber chooses a tier at the point of subscription, after carefully reviewing it. The provider is supposed to keep supporting that. However if it must be done here are your options: 1. Change the tier definitions by editing the tiers.xml in registry 2. Update the subscription entry in API Manager DB Thanks, Hiranya On Sun, Aug 12, 2012 at 11:02 PM, Subash Chaturanga sub...@wso2.com wrote: Hi all, I just noticed $subject in 1.0.0 release. Once I change the tier type of my API from Bronze to Silver I could still send only one request per minute. More than one requests, it gives the same old throttled out response. Same applies when transform from Silver to Gold. Is this a known issue ? To change the tier type, I did that from publisher edit tab and saved, is there anything more to be done for that to be effective ? Thanks -- Subash Chaturanga Software Engineer WSO2 Inc. http://wso2.com email - sub...@wso2.com phone - 077 2225922 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] System.out.println on Carbon 4.0.0 when clustering enabled
On Sun, Aug 12, 2012 at 6:03 PM, Evanthika Amarasiri evanth...@wso2.comwrote: Yes. We too noticed this. Nirmal mentioned that this is already fixed and we will not see this in the next set of packs. Does is affect API Manager 1.0? Regards, Evanthika On Sat, Aug 11, 2012 at 1:07 AM, Sumedha Rubasinghe sume...@wso2.comwrote: [2012-08-11 00:56:07,130] INFO - TribesClusteringAgent Using multicast based membership management scheme -- /sumedha +94 773017743 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Hosting a web service in ELB + use of BinaryRelayBuilder in ELB -- blocker
If this is an admin service, you can use the relay module and the skip admin service handler. Thanks, Hiranya On Thu, Aug 9, 2012 at 9:30 AM, Nirmal Fernando nir...@wso2.com wrote: Hi All, While trying to host a web service in WSO2 ELB (Elastic Load Balancer) (as discussed in [1]), I've run into a blocking issue. In ELB we set the message builder of any request, belongs to any content type (currently there's a bug in axis2 level [2]) as org.wso2.carbon.relay.BinaryRelayBuilder. This means a web service inside an ELB gets the request in a binary mode (sample request received to the service is at [3]). Hence, I am seen a namespace mismatch error [4]. Is there a work around to get the actual request instead of the binary version of it, to this service, which is hosted in ELB? [1] [Dev] Load balancer member registration Web servicehttp://www.mail-archive.com/dev@wso2.org/msg08337.html [2] [Dev] Any content type filter (.*) is not working [3] ?xml version='1.0' encoding='utf-8'?soapenv:Envelope xmlns:soapenv= http://www.w3.org/2003/05/soap-envelope;soapenv:Bodyns:binary xmlns:ns=http://ws.apache.org/commons/ns/payload PHNvYXA6RW52ZWxvcGUgeG1sbnM6c29hcD0iaHR0cDovL3d3dy53My5vcmcvMjAwMy8wNS9zb2FwLWVudmVsb3BlIiB4bWxuczppbXBsPSJodHRwOi8vaW1wbC5zZXJ2aWNlLnJlZ2lzdGVyLm1lbWJlci5sYi5jYXJib24ud3NvMi5vcmciIHhtbG5zOnhzZD0iaHR0cDovL3V0aWwuc2VydmljZS5yZWdpc3Rlci5tZW1iZXIubGIuY2FyYm9uLndzbzIub3JnL3hzZCI+/ns:binary/soapenv:Body/soapenv:Envelope [4] [2012-08-08 17:21:34,363] ERROR - RPCMessageReceiver Exception occurred while trying to invoke service method addMember org.apache.axis2.AxisFault: namespace mismatch require http://impl.service.register.member.lb.carbon.wso2.org found http://ws.apache.org/commons/ns/payload at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:190) at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172) at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:409) at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:261) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) [2012-08-08 17:21:34,366] ERROR - ServerWorker Error processing POST request org.apache.axis2.AxisFault: namespace mismatch require http://impl.service.register.member.lb.carbon.wso2.org found http://ws.apache.org/commons/ns/payload at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:190) at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172) at org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:409) at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:261) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Thanks regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Any content type filter (.*) is not working
On Thu, Aug 9, 2012 at 9:12 AM, Nirmal Fernando nir...@wso2.com wrote: Hi All, In axis2.xml, We've added following configuration under messageBuilders element. messageBuilder contentType=.* class=org.wso2.carbon.relay.BinaryRelayBuilder/ Our expectation is to set org.wso2.carbon.relay.BinaryRelayBuilder as the message builder of a request of any content type. But this seems to be broken in trunk. No, actually it never worked correctly. Axis2 special cases several content types (eg: text/xml, application/xml) and hence unless we explicitly set the builder in axis2.xml against the content type, this won't work as expected. Thanks, Hiranya -- Thanks regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Compilation Error in Platform-Integration
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project org.wso2.carbon.automation.core: Compilation failure: Compilation failure: [ERROR] /home/carbon320/AM_RELEASE/platform/platform-integration/clarity-framework/org.wso2.carbon.automation.core/src/main/java/org/wso2/carbon/automation/core/utils/ArtifactDeployerUtil.java:[35,55] cannot find symbol [ERROR] symbol : class MassageStoreAdminClient [ERROR] location: package org.wso2.carbon.automation.api.clients.mediation [ERROR] /home/carbon320/AM_RELEASE/platform/platform-integration/clarity-framework/org.wso2.carbon.automation.core/src/main/java/org/wso2/carbon/automation/core/utils/ArtifactDeployerUtil.java:[35,55] cannot find symbol [ERROR] symbol : class MassageStoreAdminClient [ERROR] location: package org.wso2.carbon.automation.api.clients.mediation [ERROR] /home/carbon320/AM_RELEASE/platform/platform-integration/clarity-framework/org.wso2.carbon.automation.core/src/main/java/org/wso2/carbon/automation/core/utils/ArtifactDeployerUtil.java:[581,16] cannot find symbol [ERROR] symbol : class MassageStoreAdminClient [ERROR] location: class org.wso2.carbon.automation.core.utils.ArtifactDeployerUtil [ERROR] /home/carbon320/AM_RELEASE/platform/platform-integration/clarity-framework/org.wso2.carbon.automation.core/src/main/java/org/wso2/carbon/automation/core/utils/ArtifactDeployerUtil.java:[582,28] cannot find symbol [ERROR] symbol : class MassageStoreAdminClient [ERROR] location: class org.wso2.carbon.automation.core.utils.ArtifactDeployerUtil [ERROR] - [Help 1] -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error in Service Governance UI
This solved the problem. Thanks Ajith for all the help. Thanks, Hiranya On Thu, Jul 26, 2012 at 12:55 PM, Ajith Vitharana aji...@wso2.com wrote: Hi Hiranya, Add the following configuration files from G-Reg 4.5.0 to AM. (add svn externals and change the bin.xml). wso2am-1.0.0-SNAPSHOT/repository/resources === lifecycle-config.xsd lifecycle-local.xsd lifecycles/configurations.xml rxt.xsd services-config.xml services-config.xsd service-ui-config.xsd Thanks Ajith On Wed, Jul 25, 2012 at 2:18 PM, Ajith Vitharana aji...@wso2.com wrote: On Wed, Jul 25, 2012 at 2:03 PM, Hiranya Jayathilaka hira...@wso2.comwrote: Hi GReg Team, We need some help to get this issue resolved: https://wso2.org/jira/browse/APISTORE-525 Basically Service Add gives a dead page and throws up an exception on the console. However WSDL Add and other related governance UIs are working. Hi Hiranya, We have built the AM product out of G-Reg profile. After that we have changed the config files and locations according to new structure that introduced in C4 release. Therefore, please update the config files and locations according to the latest G-Reg build. Thanks Ajith Thanks -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794 -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794 -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Error in Service Governance UI
Hi GReg Team, We need some help to get this issue resolved: https://wso2.org/jira/browse/APISTORE-525 Basically Service Add gives a dead page and throws up an exception on the console. However WSDL Add and other related governance UIs are working. Thanks -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error in Service Governance UI
Can you please list what these config files are and where to put them? Thanks, Hiranya On Wed, Jul 25, 2012 at 2:18 PM, Ajith Vitharana aji...@wso2.com wrote: On Wed, Jul 25, 2012 at 2:03 PM, Hiranya Jayathilaka hira...@wso2.comwrote: Hi GReg Team, We need some help to get this issue resolved: https://wso2.org/jira/browse/APISTORE-525 Basically Service Add gives a dead page and throws up an exception on the console. However WSDL Add and other related governance UIs are working. Hi Hiranya, We have built the AM product out of G-Reg profile. After that we have changed the config files and locations according to new structure that introduced in C4 release. Therefore, please update the config files and locations according to the latest G-Reg build. Thanks Ajith Thanks -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794 -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager - How to restrict to HTTPS only?
There's a resource level setting in the ESB, but we don't use it in API Manager. Thanks, Hiranya On Tue, Jul 24, 2012 at 5:42 PM, Paul Fremantle p...@wso2.com wrote: With the API Manager Is it possible to restrict an API to just HTTPS? Paul -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Hybrid Message Builder REST API
On Wed, Jul 25, 2012 at 2:44 AM, Paul Fremantle p...@wso2.com wrote:
Hiranya
What are the undesirable side effects?
One that we have already found was that, URL path is not properly appended
to the outgoing request if the content type was text/xml. That is if we
send a request to http://localhost:8280/test/foo/bar, we generally expect
the /foo/bar part to get passed to the backend. That doesn't happen when
the request content type is set to text/xml. There can be more issues like
this. There's a ton of code fragments in both Axis2 and Synapse written
assuming that text/xml is only associated with SOAP 1.1.
This is going to become very important in high volume deployments and we
need to be able to enable passthru.
Are we currently using Message Relay at least?
Yes we do.
Thanks,
Hiranya
Paul
On 19 July 2012 15:29, Hiranya Jayathilaka hira...@wso2.com wrote:
On Thu, Jul 19, 2012 at 3:57 PM, Paul Fremantle p...@wso2.com wrote:
Why don't we just use binary relay or even Passthru transport here?
Doesn't that solve this?
It solves the parsing problem. But we have uncovered some undesirable
side effects.
Thanks,
Hiranya
Paul
On 19 July 2012 10:57, Dushan Abeyruwan dus...@wso2.com wrote:
Hi Sagara,
Yes, Originally I had this concern i.e the way to determine SOAP 1.1
and POX, I think ur suggestion is best suit in this case but anyway the
provided solution (Formatter/Builder concept) wont be a perfect one as u
mention, so will keep this as open and hope this will get sorted out in
AIXS2 context, mean time I will hold those issues reported to jira util
that.
cheers
Dushan
On Thu, Jul 19, 2012 at 2:48 PM, Sagara Gunathunga sag...@wso2.comwrote:
On Thu, Jul 19, 2012 at 2:04 PM, Dushan Abeyruwan dus...@wso2.comwrote:
Hi
For an example, in API Manager if you send a POX message with
the text/xml, the query parameters on the URL do not get passed to the
backend server, whereas they will get passed if we use application/xml
instead
My thought is,
POX message received with text/xml context to API, then
hybrid builder get invoke, though we are receiving TEXT/XML while
building
the message
OMElement element =
applicationXMLBuilder.processDocument(new ByteArrayInputStream(bytes),
*HybridConstants.APPLICATION_XML*, messageContext); ,
we are* forcefully including the contentType as
application/xml NOTE: we are Keeping the flag in message context
with the actual received content type*, thus synapse engine will
treat this as application/xml and thus will wont be a issue with query
parameter, then at the formatter using the flag just before send to BE
setup the actual CONTENT TYPE to the outgoing message thus this will
write
to the wire
*sample code*
if
(HybridConstants.TEXT_XML.equals(contentType)) {
SOAPBuilder builder = new SOAPBuilder();
try {
return builder.processDocument(new ByteArrayInputStream(bytes),
contentType, messageContext);
} catch (Exception e) {
// assumption if a failure happens this must be check
// whether the message is
// is accepted as application XML
ApplicationXMLBuilder applicationXMLBuilder = new
ApplicationXMLBuilder();
OMElement element = applicationXMLBuilder.processDocument(new
ByteArrayInputStream(bytes), HybridConstants.APPLICATION_XML,
messageContext);
*messageContext.setProperty(HybridConstants.HYBRID_BUILD, true);*
return element;
}
}
Here you first try to build the message with SOAPBuilder and and if it
fail try to build with ApplicationXMLBuilder, this should work but isn't
this approach add extra cost for POX messages processing ? It can be a
very
small overhead but in context of a ESB we should not ignore such small
overheads too. Instead of above logic why don't you check SOAPAction
header together with Content-Type header. According to SOAP 1.1 spec it's
mandatory to have SOAPAction with valid SOAP 1.1 message if SOAPAction is
missing it's safe to assume message as POX.
content-type == text/xml SOAPAction present = SOAPBuilder
OW = ApplicationXMLBuilder
Thanks !
cheers
Dushan
On Thu, Jul 19, 2012 at 1:34 PM, Hiranya Jayathilaka
hira...@wso2.com wrote:
This solution will take care of the message parsing issue. But the
main problem is Synapse and Axis2 both associating text/xml with SOAP
1.1.
There's a lot of code written based on this assumption. For instance the
parsing issue can be worked around by using something like the message
relay (we do this in API Manager). But still there are certain things
that
don't work properly when you send a POX payload with the text/xml
content
type. For an example, in API Manager if you send a POX message with the
text/xml, the query parameters on the URL do not get passed to the
backend
server, whereas they will get passed if we use application/xml instead.
This is a very tricky problem to solve. I tried to solve
[Dev] [ANN] WSO2 API Manager 1.0.0-Beta2 Released
-503] - Support Oracle for API Manager database -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Hybrid Message Builder (Solution for
This solution will take care of the message parsing issue. But the main problem is Synapse and Axis2 both associating text/xml with SOAP 1.1. There's a lot of code written based on this assumption. For instance the parsing issue can be worked around by using something like the message relay (we do this in API Manager). But still there are certain things that don't work properly when you send a POX payload with the text/xml content type. For an example, in API Manager if you send a POX message with the text/xml, the query parameters on the URL do not get passed to the backend server, whereas they will get passed if we use application/xml instead. This is a very tricky problem to solve. I tried to solve this for API Manager, but had to give it up considering the time constraints and the possible stability issues it might introduce. We need to discuss this with a larger audience before we decide on the final plan. I also just noticed the other mail from Sagara, which explains a proper solution to this issue from Axis2 end. We need incorporate the same fix into Synapse where ever we are looking at the content type to differentiate between SOAP and REST. Thanks, Hiranya On Thu, Jul 19, 2012 at 1:22 PM, Dushan Abeyruwan dus...@wso2.com wrote: Hi, Recently we had a few issues [1][2] when invoking REST services via ESB REST API when client sends information with the content type TEXT/XML (and if BACK END accepts TEXT/XML) so when message receives to ESB if the content type is defined TEXT/XML by default it will try to build up SOAP envelope, but AFAIK most REST calls are based on TEXT/XML so theoretically this kind of messages should be able to handle via ESB, so for this as solution I have written a Builder formatter, basically I named this as HYBRID message builder /formatter, the idea is when client sends simple xml element with via REST (with content type TEXT/XML) , the logic is first the hybrid builder checks if the message content type defines as TEXT/XML followed by root element containing any SOAP element. if not Hybrid builder invokes the Application XML builder internally and will build the message and setting up a flag to message context thus during the HybridFormatter invocation we can determine that the original client request content type and write it to the output pipe, (did few mock testings with few use cases and worked well) any suggestions on this [1] https://wso2.org/jira/browse/ESBJAVA-1160 [2]https://wso2.org/jira/browse/ESBJAVA-1160 cheers, Dushan Abeyruwan *Senior Software Engineer* *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Commits] [Carbon-platform] svn commit r132727 - carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadm
Thanks Dushan. Any chance we can get this fix done today? We need this for
the next API Manager Beta release.
Thanks,
Hiranya
On Tue, Jul 17, 2012 at 11:18 AM, Dushan Abeyruwan dus...@wso2.com wrote:
Hi
Yes, your suggestion is correct, I will do required changers and will
introduce SequenceMediatorFactory instead of invoking
MediatorService service = MediatorStore.getInstance().
getMediatorService(sequenceElement);
cheers
Dushan
On Tue, Jul 17, 2012 at 10:58 AM, Hiranya Jayathilaka hira...@wso2.comwrote:
I don't think this fix is correct. It's introducing an unnecessary
compile time dependency between synapse-config-admin and sequence editor.
Why don't you use the SequenceMediatorFactory class from Synapse directly?
Thanks,
Hiranya
On Thu, Jul 12, 2012 at 3:52 PM, dus...@wso2.com wrote:
Author: dushan
Date: Thu Jul 12 06:22:20 2012
New Revision: 132727
URL: http://wso2.org/svn/browse/wso2?view=revrevision=132727
Log:
Properties can be created with names containing special characters. But
Such properties cannot be used in some Xpath expressions.
https://wso2.org/jira/browse/ESBJAVA-1052
Modified:
carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java
Modified:
carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java
URL:
http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java?rev=132727r1=132726r2=132727view=diff
==
---
carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java
(original)
+++
carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java
Thu Jul 12 06:22:20 2012
@@ -27,6 +27,9 @@
import org.apache.synapse.core.axis2.ProxyService;
import org.apache.synapse.endpoints.Endpoint;
import org.apache.synapse.endpoints.WSDLEndpoint;
+import org.wso2.carbon.mediator.service.MediatorService;
+import org.wso2.carbon.mediator.service.MediatorStore;
+import org.wso2.carbon.mediator.service.builtin.SequenceMediator;
import javax.xml.namespace.QName;
import java.io.IOException;
@@ -62,6 +65,8 @@
validateProxyService(child, errors);
} else if
(XMLConfigConstants.ENDPOINT_ELT.equals(child.getQName())) {
validateEndpoint(child, errors);
+}else
if(XMLConfigConstants.SEQUENCE_ELT.equals(child.getQName())){
+ validateSequence(child,errors);
}
}
}
@@ -72,6 +77,16 @@
return null;
}
+ private void validateSequence(OMElement
sequenceElement,ListValidationError errors) {
+ try{
+MediatorService service =
MediatorStore.getInstance().getMediatorService(sequenceElement);
+SequenceMediator sequence = (SequenceMediator)
service.getMediator();
+sequence.build(sequenceElement);
+ }catch (Exception e) {
+ errors.add(newValidationError(sequenceElement,
e.getMessage()));
+ }
+}
+
private void validateProxyService(OMElement proxyElement,
ListValidationError errors) {
try {
ProxyService proxy =
ProxyServiceFactory.createProxy(proxyElement, new Properties());
___
Commits mailing list
comm...@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/commits
--
Hiranya Jayathilaka
Senior Technical Lead;
WSO2 Inc.; http://wso2.org
E-mail: hira...@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
--
Dushan Abeyruwan
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/*
*Mobile:(+94)714408632*
--
Hiranya Jayathilaka
Senior Technical Lead;
WSO2 Inc.; http://wso2.org
E-mail: hira...@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB Callout mediator fails when accessing an endpoint through local transport
The server configuration of Synapse usually has the non-blocking
transports. That may have an effect on the thread model of the callout
mediator.
Thanks,
Hiranya
On Mon, Jul 16, 2012 at 2:33 PM, Amila Suriarachchi am...@wso2.com wrote:
On Fri, Jul 13, 2012 at 4:47 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:
Hi all,
On Wed, Jul 11, 2012 at 6:23 PM, Supun Kamburugamuva
supu...@gmail.comwrote:
The server config context has the nhttp transport as the http transport.
So callout mediator will pick this transport if we use the server
configuration context. We should have a proper naming for the transports in
axis2 before we can do this. i.e. At the moment axis2 thinks that the name
of the transport is equal to the protocol name of the transport.
We were able to use Callout mediator with local transport by doing some
modifications to the synapse Callout mediator. We are proposing to add an
attribute 'useServerConfig' to the callout mediator which will use server
configuration context if set as true. By default it will be false and
Client configuration context will be used.
So to use the Server Configuration in Callout mediator, the configuration
will be,
callout serviceURL=local://localhost/services/DTPSampleService
action=urn:addToAccountBalanceInBank2 useServerConfig=true
source xpath=$body/child::*[fn:position()=1]/
target xpath=$body/child::*[fn:position()=1]/
/callout
The modification done to the Callout Mediator was changing the init
method of CalloutMediator.java
public void init(SynapseEnvironment synEnv) {
try {
if (useServerConfig) {
configCtx = ((Axis2SynapseEnvironment)
synEnv).getAxis2ConfigurationContext();
} else {
configCtx =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(
clientRepository != null ? clientRepository :
DEFAULT_CLIENT_REPO,
axis2xml != null ? axis2xml : DEFAULT_AXIS2_XML);
}
} catch (AxisFault e) {
String msg = Error initializing callout mediator : +
e.getMessage();
log.error(msg, e);
throw new SynapseException(msg, e);
}
}
When *useServerConfig* is set true, the *configCtx* will be initialized
with Server Configuration Context as in Send mediator.
Shall we proceed with this solution?
+1. This allows to use the call out mediator with local transport as well.
thanks,
Amila.
Thanks,
Lakmali
Thanks,
Supun..
On Wed, Jul 11, 2012 at 4:46 AM, Lakmali Baminiwatta
lakm...@wso2.comwrote:
Hi,
How can we proceed if we are going to change the Callout mediator to
use the server config context as well?
Thanks,
Lakmali
On Tue, Jul 10, 2012 at 11:39 PM, Kasun Indrasiri ka...@wso2.comwrote:
However, following scenario seems to work fine. Seems this is not the
expected behavior.
proxy name=EchoProxy transports=https http startOnLoad=true
trace=disable
description/
target
inSequence
callout serviceURL=local://services/echo
action=urn:echoString
source xmlns:s12=
http://www.w3.org/2003/05/soap-envelope; xmlns:s11=
http://schemas.xmlsoap.org/soap/envelope/;
xpath=s11:Body/child::*[fn:position()=1] |
s12:Body/child::*[fn:position()=1]/
target xmlns:s12=
http://www.w3.org/2003/05/soap-envelope; xmlns:s11=
http://schemas.xmlsoap.org/soap/envelope/;
xpath=s11:Body/child::*[fn:position()=1] |
s12:Body/child::*[fn:position()=1]/
/callout
property name=RESPONSE value=true/
header name=To action=remove/
send/
/inSequence
outSequence
send/
/outSequence
/target
/proxy
On Tue, Jul 10, 2012 at 10:23 PM, Supun Kamburugamuva
supu...@gmail.com wrote:
For the local transport to work both the invoker and the invoking
service should be in the same configuration context. So this scenario
will
never work with the local transport + callout mediator.
Thanks,
Supun..
On Tue, Jul 10, 2012 at 12:48 PM, Hiranya Jayathilaka
hira...@wso2.com wrote:
On Tue, Jul 10, 2012 at 5:50 PM, Lakmali Baminiwatta
lakm...@wso2.com wrote:
Hi,
On Tue, Jul 10, 2012 at 5:26 PM, Hiranya Jayathilaka
hira...@wso2.com wrote:
Send mediator and callout mediator use different
ConfigurationContext instances. Former uses the server cfgctx and the
latter uses the client cfgctx. That should be the problem.
I have enabled local transport on
samples/axis2Client/client_repo/conf/axis2.xml. Does it require more
configurations to the client cfgctx ?
I think the local transport looks up the cfgctx to find the target
AxisService. So unless you somehow use the server cfgctx in the callout
mediator, this scenario will never work. Better to debug and confirm
Re: [Dev] [Commits] [Carbon-platform] svn commit r132727 - carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadm
I don't think this fix is correct. It's introducing an unnecessary compile
time dependency between synapse-config-admin and sequence editor. Why don't
you use the SequenceMediatorFactory class from Synapse directly?
Thanks,
Hiranya
On Thu, Jul 12, 2012 at 3:52 PM, dus...@wso2.com wrote:
Author: dushan
Date: Thu Jul 12 06:22:20 2012
New Revision: 132727
URL: http://wso2.org/svn/browse/wso2?view=revrevision=132727
Log:
Properties can be created with names containing special characters. But
Such properties cannot be used in some Xpath expressions.
https://wso2.org/jira/browse/ESBJAVA-1052
Modified:
carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java
Modified:
carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java
URL:
http://wso2.org/svn/browse/wso2/carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java?rev=132727r1=132726r2=132727view=diff
==
---
carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java
(original)
+++
carbon/platform/trunk/components/synapse-config-admin/org.wso2.carbon.mediation.configadmin/src/main/java/org/wso2/carbon/mediation/configadmin/ConfigurationValidator.java
Thu Jul 12 06:22:20 2012
@@ -27,6 +27,9 @@
import org.apache.synapse.core.axis2.ProxyService;
import org.apache.synapse.endpoints.Endpoint;
import org.apache.synapse.endpoints.WSDLEndpoint;
+import org.wso2.carbon.mediator.service.MediatorService;
+import org.wso2.carbon.mediator.service.MediatorStore;
+import org.wso2.carbon.mediator.service.builtin.SequenceMediator;
import javax.xml.namespace.QName;
import java.io.IOException;
@@ -62,6 +65,8 @@
validateProxyService(child, errors);
} else if
(XMLConfigConstants.ENDPOINT_ELT.equals(child.getQName())) {
validateEndpoint(child, errors);
+}else
if(XMLConfigConstants.SEQUENCE_ELT.equals(child.getQName())){
+ validateSequence(child,errors);
}
}
}
@@ -72,6 +77,16 @@
return null;
}
+ private void validateSequence(OMElement
sequenceElement,ListValidationError errors) {
+ try{
+MediatorService service =
MediatorStore.getInstance().getMediatorService(sequenceElement);
+SequenceMediator sequence = (SequenceMediator)
service.getMediator();
+sequence.build(sequenceElement);
+ }catch (Exception e) {
+ errors.add(newValidationError(sequenceElement,
e.getMessage()));
+ }
+}
+
private void validateProxyService(OMElement proxyElement,
ListValidationError errors) {
try {
ProxyService proxy =
ProxyServiceFactory.createProxy(proxyElement, new Properties());
___
Commits mailing list
comm...@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/commits
--
Hiranya Jayathilaka
Senior Technical Lead;
WSO2 Inc.; http://wso2.org
E-mail: hira...@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API manager becomes unusable due to a registry dead lock
.carbon.registry.core.jdbc.EmbeddedRegistry.executeQuery(EmbeddedRegistry.java:2271) at org.wso2.carbon.registry.core.caching.CacheBackedRegistry.executeQuery(CacheBackedRegistry.java:305) at org.wso2.carbon.registry.core.session.UserRegistry.executeQuery(UserRegistry.java:1246) at org.wso2.carbon.governance.api.util.GovernanceUtils.getResultPaths(GovernanceUtils.java:171) ... 56 more Apparently, this seems to be a known issue and reported multiple times(e.g: https://wso2.org/jira/browse/CARBON-11409), the suggested workaround is to use mysql. However, in API manager scenario, the error is very prominent. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- /sumedha +94 773017743 -- *Senaka Fernando* Member - Integration Technologies Management Committee; Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware -- /sumedha +94 773017743 -- /sumedha +94 773017743 -- /sumedha +94 773017743 -- *Senaka Fernando* Member - Integration Technologies Management Committee; Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fwd: [trunk] AM startup errors.
Clearly something is not up-to-date in your pack. We made some changes yesterday to use the data sources defined in the Carbon's master data source file. Some crucial change related to that is missing in your build. Overall the changes work well for us. We gave a pack from the Beta2 branch to the QA team yesterday which they tested for several hours. They also didn't encounter any issues. Thanks, Hiranya On Sat, Jul 14, 2012 at 12:41 PM, Ajith Vitharana aji...@wso2.com wrote: -- Forwarded message -- From: Ajith Vitharana aji...@wso2.com Date: Sat, Jul 14, 2012 at 12:40 PM Subject: [trunk] AM startup errors. To: Hiranya Jayathilaka hira...@wso2.com, Sumedha Rubasinghe sume...@wso2.com Hi all, I'm getting following error while start the AM. [2012-07-14 12:34:53,009] FATAL - APIManagerComponent Error while initializing the API manager component org.wso2.carbon.apimgt.api.APIManagementException: Required DB configuration parameters unspecified at org.wso2.carbon.apimgt.impl.utils.APIMgtDBUtil.initialize(APIMgtDBUtil.java:86) at org.wso2.carbon.apimgt.impl.internal.APIManagerComponent.activate(APIManagerComponent.java:114) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252) at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146) at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346) at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588) at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196) at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328) at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221) at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451) at org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.registerServices(DataSourceServiceComponent.java:102) at org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.initAllTenantUserDataSources(DataSourceServiceComponent.java:199) at org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.checkInitTenantUserDataSources(DataSourceServiceComponent.java:183) at org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.setRegistryService(DataSourceServiceComponent.java:133) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:367) at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:430) at org.eclipse.equinox.internal.ds.InstanceProcess.dynamicBind(InstanceProcess.java:415) at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:319) at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221) at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148
Re: [Dev] AM build error in clean repo
Hi Ajith, The correct fix here is to remove the agent feature from the AM P2 profile (we use a new data-bridge feature from BAM now). I did the change for the Beta2 branch but didn't do it in the trunk yet. I'll take a look and fix it properly for the trunk. Thanks, Hiranya On Sat, Jul 14, 2012 at 12:36 PM, Ajith Vitharana aji...@wso2.com wrote: Fixed r 132975. Thanks Ajith On Sat, Jul 14, 2012 at 12:08 PM, Ajith Vitharana aji...@wso2.com wrote: The reason is agent feature has excluded from features/data-agents/pom.xml. modules * !--moduleagent/module--* modulemediation/module moduleservice/module /modules Thanks Ajith On Sat, Jul 14, 2012 at 12:05 PM, Ajith Vitharana aji...@wso2.comwrote: Hi all, I'm getting following error. [INFO] --- carbon-p2-plugin:1.5-SNAPSHOT:p2-repo-gen (2-p2-repo-generation) @ am-p2-profile --- [ERROR] ERROR org.apache.maven.plugin.MojoExecutionException: ERROR at org.wso2.maven.p2.generate.utils.MavenUtils.getResolvedArtifact(MavenUtils.java:43) at org.wso2.maven.p2.RepositoryGenMojo.getProcessedFeatureArtifacts(RepositoryGenMojo.java:318) at org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:197) at org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:191) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Failure to find org.wso2.carbon:org.wso2.carbon.bam.agent.feature:zip:4.0.0-SNAPSHOT in http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local repository, resolution will not be reattempted until the update interval of wso2-nexus has elapsed or updates are forced Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.wso2.carbon -DartifactId=org.wso2.carbon.bam.agent.feature -Dversion=4.0.0-SNAPSHOT -Dpackaging=zip -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.wso2.carbon -DartifactId=org.wso2.carbon.bam.agent.feature -Dversion=4.0.0-SNAPSHOT -Dpackaging=zip -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.wso2.carbon:org.wso2.carbon.bam.agent.feature:zip:4.0.0-SNAPSHOT -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794 -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794 -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794 -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Logging Component Docs Issue
Tag consistency is broken in the userguide.html file of the logging component. Product builds are failing due to this. Please fix asap. Thanks -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Jaggery fails miserably
) at org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:448) at org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:202) at org.jaggeryjs.jaggery.core.manager.WebAppManager.executeScript(WebAppManager.java:149) at org.jaggeryjs.jaggery.core.manager.WebAppManager.include(WebAppManager.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:160) ... 33 more ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Ruchira Wageesha Senior Software Engineer Member, Management Committee, Development Technologies* *WSO2 Inc. - lean . enterprise . middleware | wso2.com* * email: ruch...@wso2.com, blog: ruchirawageesha.blogspot.com, mobile: +94 77 5493444* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Jaggery fails miserably
Thanks Dimuthu. It's working now.
Thanks,
Hiranya
On Thu, Jul 12, 2012 at 6:08 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:
Hi Hiranya,
On Thu, Jul 12, 2012 at 6:02 PM, Hiranya Jayathilaka hira...@wso2.comwrote:
We're also getting [1] in API Manager.
SVN up the core. It helped
thanks,
dimuthu
Thanks,
Hiranya
On Thu, Jul 12, 2012 at 4:52 PM, Dimuthu Leelarathne
dimut...@wso2.comwrote:
Hi,
On Thu, Jul 12, 2012 at 4:33 PM, Ruchira Wageesha ruch...@wso2.comwrote:
This has been fixed already. Please update/build features/jaggery and
the product.
Updating fixed the issue [2]. I will look at issue [1]
Thank you for the quick help.
thanks,
dimuthu
On Thu, Jul 12, 2012 at 4:15 PM, Dimuthu Leelarathne dimut...@wso2.com
wrote:
Hi all,
Jaggery fails miserably on trunk build today. First it has this error
which I fixed. Then I am haivng [2], even if I copy the modules folder to
the application.
We are suppose to do a M2 of App Factory today. We might go with an
older revision.
thanks,
dimuthu
[1]
[2012-07-12 15:54:24,704] INFO
{org.wso2.carbon.core.ServerManagement} - Waiting for request service
completion...
[2012-07-12 15:54:31,462] ERROR
{org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve} - Could not
handle request: /appmgt/
java.lang.NullPointerException
at java.io.File.init(File.java:222)
at
org.wso2.carbon.context.ApplicationContext.getApplicationNameFromRequest(ApplicationContext.java:85)
at
org.wso2.carbon.tomcat.ext.internal.Utils.getAppNameFromRequest(Utils.java:92)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.initCarbonContext(CarbonContextCreatorValve.java:68)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:48)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
[2]
[2012-07-12 16:08:59,352] ERROR
{org.jaggeryjs.jaggery.core.manager.CommonManager} - A module cannot be
found with the specified name : appFactory
[2012-07-12 16:08:59,354] ERROR
{org.jaggeryjs.scriptengine.engine.RhinoEngine} -
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException: A module cannot be
found with the specified name : appFactory (/appmgt/config_reader.jag#3)
[2012-07-12 16:08:59,354] ERROR
{org.jaggeryjs.scriptengine.engine.RhinoEngine} -
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException: A module cannot be
found with the specified name : appFactory (/appmgt/config_reader.jag#3)
(/appmgt/sso/jaggery_sso.jag#4)
[2012-07-12 16:08:59,355] ERROR
{org.jaggeryjs.scriptengine.engine.RhinoEngine} -
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException: A module cannot be
found with the specified name : appFactory (/appmgt/config_reader.jag#3)
(/appmgt/sso/jaggery_sso.jag#4) (/appmgt/includes/template_header.jag#3)
[2012-07-12 16:08:59,355] ERROR
{org.jaggeryjs.scriptengine.engine.RhinoEngine} -
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException: A module cannot be
found with the specified name : appFactory (/appmgt/config_reader.jag#3)
(/appmgt/sso/jaggery_sso.jag#4) (/appmgt/includes/template_header.jag#3)
(/appmgt/index.jag#2)
[2012-07-12 16:08:59,355] ERROR
{org.jaggeryjs.jaggery.core.manager.WebAppManager} -
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException:
org.mozilla.javascript.WrappedException
[Dev] API Manager Start Up Fails with Amber CNF Error
) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) ... 50 more -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager Start Up Fails with Amber CNF Error
Got this issue resolved. Needed to add the OAuth common feature. Thanks Thilina for the help. Thanks, Hiranya On Wed, Jul 11, 2012 at 2:48 PM, Hiranya Jayathilaka hira...@wso2.comwrote: [2012-07-11 14:47:57,394] FATAL - CarbonServerManager WSO2 Carbon initialization Failed java.lang.NoClassDefFoundError: org/apache/amber/oauth2/as/issuer/ValueGenerator at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.init(DefaultSchemaGenerator.java:140) at org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453) at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397) at org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101) at org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217) at org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102) at org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89) at org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:471) at org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:217) at org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:64) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252) at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146) at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346) at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588) at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196) at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328) at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221) at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451) at org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:78) at org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:57) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:39) at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:27) at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5026) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5313) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1595) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1585) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.ClassNotFoundException: org.apache.amber.oauth2.as.issuer.ValueGenerator
Re: [Dev] ESB Callout mediator fails when accessing an endpoint through local transport
Send mediator and callout mediator use different ConfigurationContext instances. Former uses the server cfgctx and the latter uses the client cfgctx. That should be the problem. If you're using the local transport, it doesn't matter which mediator you use performance wise. So why not just use the send mediator? Thanks, Hiranya On Tue, Jul 10, 2012 at 1:44 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi, On Tue, Jul 10, 2012 at 1:09 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi, I am trying to configure ESB Callout mediator to access a dataservice endpoint through local transport. I have enabled local transport on samples/axis2Client/client_repo/conf/axis2.xml. I configured the callout mediator serviceURL and action as follows, * callout serviceURL=http://localhost:8282/services/updateNonxaTrans action=urn:UpdateXATransOp * The callout mediator configuration I used was, * callout serviceURL=local://localhost/services/updateNonxaTrans** action=urn:UpdateXATransOp* I have mistakenly mentioned a wrong URL above. * *I am getting the following error while invoking the service. ERROR - AxisEngine The service cannot be found for the endpoint reference (EPR) local://localhost/services/updateNonxaTrans org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) local://localhost/services/updateNonxaTrans at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:78) at org.apache.axis2.engine.Phase.invoke(Phase.java:329) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168) But the endpoint works when configured with send mediator. How can we use callout mediator to access endpoints through local transport? Thanks, Lakmali -- Lakmali Baminiwatta* * Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware * * -- Lakmali Baminiwatta* * Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 * * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB Callout mediator fails when accessing an endpoint through local transport
On Tue, Jul 10, 2012 at 5:50 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:
Hi,
On Tue, Jul 10, 2012 at 5:26 PM, Hiranya Jayathilaka hira...@wso2.comwrote:
Send mediator and callout mediator use different ConfigurationContext
instances. Former uses the server cfgctx and the latter uses the client
cfgctx. That should be the problem.
I have enabled local transport on
samples/axis2Client/client_repo/conf/axis2.xml. Does it require more
configurations to the client cfgctx ?
I think the local transport looks up the cfgctx to find the target
AxisService. So unless you somehow use the server cfgctx in the callout
mediator, this scenario will never work. Better to debug and confirm - I'm
not 100% certain.
If you're using the local transport, it doesn't matter which mediator you
use performance wise. So why not just use the send mediator?
The requirement is to get the response from the endpoint in the same
sequence. For instance with send mediator , when the operation at the
endpoint is failed and soap fault is returned, it will go to the
outSequence. Is there a way to jump to the fault sequence once a soap fault
has returned from the endpoint?
Use a simple filter in the out-sequence to check the message and jump to
the fault sequence. It will be something like this:
filter xpath=get-property('FAULT')
sequence key=my_fault_seq/
drop/
/filter
Thanks,
Hiranya
I am trying to do a distributed transaction between dataservice endpoints,
using ESB transport mediator. When an operation in one of the data service
endpoint has failed, the soap fault message will be received in the out
sequence. As a result we are facing a problem of where to call rollback
action on transport mediator.
Thanks,
Lakmali
Thanks,
Hiranya
On Tue, Jul 10, 2012 at 1:44 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:
Hi,
On Tue, Jul 10, 2012 at 1:09 PM, Lakmali Baminiwatta
lakm...@wso2.comwrote:
Hi,
I am trying to configure ESB Callout mediator to access a dataservice
endpoint through local transport. I have enabled local transport on
samples/axis2Client/client_repo/conf/axis2.xml.
I configured the callout mediator serviceURL and action as follows,
* callout serviceURL=http://localhost:8282/services/updateNonxaTrans;
action=urn:UpdateXATransOp
*
The callout mediator configuration I used was,
*
callout serviceURL=local://localhost/services/updateNonxaTrans**
action=urn:UpdateXATransOp*
I have mistakenly mentioned a wrong URL above.
*
*I am getting the following error while invoking the service.
ERROR - AxisEngine The service cannot be found for the endpoint
reference (EPR) local://localhost/services/updateNonxaTrans
org.apache.axis2.AxisFault: The service cannot be found for the
endpoint reference (EPR) local://localhost/services/updateNonxaTrans
at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:78)
at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168)
But the endpoint works when configured with send mediator.
How can we use callout mediator to access endpoints through local
transport?
Thanks,
Lakmali
--
Lakmali Baminiwatta*
*
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
*
*
--
Lakmali Baminiwatta*
*
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile: +94 71 2335936
*
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Hiranya Jayathilaka
Senior Technical Lead;
WSO2 Inc.; http://wso2.org
E-mail: hira...@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
--
Lakmali Baminiwatta*
*
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile: +94 71 2335936
*
*
--
Hiranya Jayathilaka
Senior Technical Lead;
WSO2 Inc.; http://wso2.org
E-mail: hira...@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Test failures in API Management component
Can you try now please? I noticed that some changes have been done to the org.wso2.carbon.apimgt.impl component recently, but the relevant test cases haven't been updated. I just did the necessary changes in the tests. Thanks, Hiranya On Tue, Jul 10, 2012 at 6:54 PM, Kishanthan Thangarajah kishant...@wso2.com wrote: Hi, The following tests failed in bamboo build in apimgt/org.wso2.carbon.apimgt.impl component. Please refer [1] build 10-Jul-2012 02:57:32Failed tests: testBasicAPI(org.wso2.carbon.apimgt.impl.template.TemplateBuilderTest): expected:...=GETinSequence[]filter source=$ctx:... but was:...=GETinSequence[class name=org.wso2.carbon.apimgt.mediators.TokenPasser/]filter source=$ctx:... build 10-Jul-2012 02:57:32 testURLEncode(org.wso2.carbon.apimgt.impl.template.TemplateBuilderTest): expected:...=GETinSequence[]filter source=$ctx:... but was:...=GETinSequence[class name=org.wso2.carbon.apimgt.mediators.TokenPasser/]filter source=$ctx:... build 10-Jul-2012 02:57:32 testAdvancedAPI(org.wso2.carbon.apimgt.impl.template.TemplateBuilderTest): expected:...=GETinSequence[]filter source=$ctx:... but was:...=GETinSequence[class name=org.wso2.carbon.apimgt.mediators.TokenPasser/]filter source=$ctx:... Can we fix these ASAP? Thanks, Kishanthan. [1] http://wso2.org/bamboo/download/WSO2CARBON-PLATFORM-JOB1/build_logs/WSO2CARBON-PLATFORM-JOB1-447.log -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Do we support IBM JDK in latest trunk?
on this release of WSO2 BAM. The WSO2 BAM Team ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Fernando Troya* fernando.tr...@fluxit.com.ar www.fluxit.com.ar 9 n° 865 (planta alta) / La Plata / Buenos Aires / Argentina (+54)-221-5532980 - Interno 315 ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Have we tested JMX monitoring in trunk
Hi Amila, Can you please explain which part of JMX monitoring is not working? Thanks, Hiranya On Thu, Jul 5, 2012 at 10:54 AM, Charitha Kankanamge chari...@wso2.comwrote: Noted. On Thu, Jul 5, 2012 at 10:40 AM, Amila Maha Arachchi ami...@wso2.comwrote: Hi all, $subject? I tried to follow some articles on how to remotely monitor WSO2 products via JMX (with 3.2.3 packs) and it seems the instructions mentioned in those articles are not working. One such article is [1]. But there is a workaround which can be found at [2]. Charitha et al, please pay attention to this during your testing cycles. If this is broken, we'll have to fix this before we release the kernel. [1] http://wso2.org/library/knowledge-base/2011/04/monitoring-wso2-esb-using-jconsole [2] http://maharachchi.blogspot.com/2011/02/monitoring-your-java-application-with.html Regards, AmilaM. -- *Amila Maharachchi* Technical Lead Member, Management Committee - Cloud Platform TG WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Storing duplicate data in AM DB and governance registry
At one point Sumedha suggested that we should use a single API_ID everywhere in AM DB. That's how the AM_API table came into existence. Thanks, Hiranya On Tue, Jul 3, 2012 at 11:52 PM, Denis Weerasiri de...@wso2.com wrote: Hi Hiranya, Some of the meta data related to API is store in both AM DB (AM_API table) and governance registry at org.wso2.carbon.apimgt.impl.APIProviderImpl#addAPI. Is there a reason to persist those data in AM DB rather just manage them only inside the registry? https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/apimgt/org.wso2.carbon.apimgt.impl/src/main/java/org/wso2/carbon/apimgt/impl/APIProviderImpl.java -- Thanks, Denis -- *Denis Weerasiri* Senior Software Engineer Integration Technologies Team, WSO2 Inc.; http://wso2.com, *email: denis http://goog_277208233/** [AT] wso2.com http://wso2.com/* *phone: +94117639629 * *site: **https://sites.google.com/site/ddweerasiri/*https://sites.google.com/site/ddweerasiri/ *blog: **http://ddweerasiri.blogspot.com*http://ddweerasiri.blogspot.com/ * twitter: **http://twitter.com/ddweerasiri*http://twitter.com/ddweerasiri * linked-in: **http://lk.linkedin.com/in/ddweerasiri*http://lk.linkedin.com/in/ddweerasiri -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Storing duplicate data in AM DB and governance registry
If you go thru the DB schema you will notice how the API_ID is bring referenced by other tables. Thanks, Hiranya On Wed, Jul 4, 2012 at 2:13 PM, Hiranya Jayathilaka hira...@wso2.comwrote: At one point Sumedha suggested that we should use a single API_ID everywhere in AM DB. That's how the AM_API table came into existence. Thanks, Hiranya On Tue, Jul 3, 2012 at 11:52 PM, Denis Weerasiri de...@wso2.com wrote: Hi Hiranya, Some of the meta data related to API is store in both AM DB (AM_API table) and governance registry at org.wso2.carbon.apimgt.impl.APIProviderImpl#addAPI. Is there a reason to persist those data in AM DB rather just manage them only inside the registry? https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/apimgt/org.wso2.carbon.apimgt.impl/src/main/java/org/wso2/carbon/apimgt/impl/APIProviderImpl.java -- Thanks, Denis -- *Denis Weerasiri* Senior Software Engineer Integration Technologies Team, WSO2 Inc.; http://wso2.com, *email: denis http://goog_277208233/** [AT] wso2.com http://wso2.com/ * *phone: +94117639629 * *site: **https://sites.google.com/site/ddweerasiri/*https://sites.google.com/site/ddweerasiri/ *blog: **http://ddweerasiri.blogspot.com*http://ddweerasiri.blogspot.com/ * twitter: **http://twitter.com/ddweerasiri*http://twitter.com/ddweerasiri * linked-in: **http://lk.linkedin.com/in/ddweerasiri*http://lk.linkedin.com/in/ddweerasiri -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] New API methods in SuperTenantCarbonContext to get hold of OSGi service references
On Sat, Jun 30, 2012 at 8:00 AM, Afkham Azeez az...@wso2.com wrote: Scr annotations cannot be used from pure Axis2 (non-OSGi bundle), pure webapps, pure JAXWS/JAXRS apps and so on. These methods will allow any of these non-OSGi artifacts to access OSGi services. This feature is immediately needed by BAM has been committed to the trunk, and will be available with C4. Great. This will also hopefully encourage component authors to expose their functionality as OSGi services more often. Thanks, Hiranya On Sat, Jun 30, 2012 at 1:02 AM, Senaka Fernando sen...@wso2.com wrote: Hi Azeez, Is this different to how @scr annotations work? What are the implementations of these methods supposed to be doing? Also, when would these make to the API? C4 or later? Thanks, Senaka. On Fri, Jun 29, 2012 at 9:10 PM, Afkham Azeez az...@wso2.com wrote: I just tested this with the attached webapp and the OSGi service call from the webapp works as well. On Thu, Jun 28, 2012 at 6:31 PM, Afkham Azeez az...@wso2.com wrote: After a discussion during today'd BAM REST API review, we came up with this idea of allowing webapps, services etc. to obtain references to OSGi services deployed in the platform using the Carbon APIs. As a result of this, I have added the following methods to the SuperTenantCarbonContext. /** * Obtain the first OSGi service found for interface or class codeclazz/code * @param clazz The type of the OSGi service * @return The OSGi service */ public Object getOSGiService(Class clazz) /** * Obtain the OSGi services found for interface or class codeclazz/code * @param clazz The type of the OSGi service * @return The List of OSGi services */ public ListObject getOSGiServices(Class clazz) Usage example; ListenerManager listenerManager = (ListenerManager) * SuperTenantCarbonContext.getCurrentContext().getOSGiService(ListenerManager.class) *; System.out.println(Is listener running: + !listenerManager.isStopped()); I have added tested the above call in one of the Carbon kernel integration tests. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Senaka Fernando* Member - Integration Technologies Management Committee; Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando * Lean . Enterprise . Middleware -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Properties file issue
Have we found a reasonable solution to this problem? ESB still cannot load certain important config files like nhttp.properties and datasources.properties due to this problem. The same limitation should be there for all other Axis2 transports since all of them attempt to load properties files from class path. Thanks, Hiranya On Thu, Jun 21, 2012 at 11:29 PM, Dushan Abeyruwan dus...@wso2.com wrote: Hi I think we have come to a solution like setting up the external config location as system property and load respective property files from their, and we have agreed to* reject the fragment bundle property file loading mechanism since its a close to kind of a hack and not the best practice among to load properties*, currently the config location is specified at wso2server(.sh/bat) as -Dconf.location=$CARBON_HOME/repository/conf\ ,/ -Dconf.location =%CARBON_HOME% \repository\conf thus respective components first looking in to the system property define path if not followed by its classloader context , any other ideas? , cheers Dushan On Thu, Jun 21, 2012 at 9:21 AM, Afkham Azeez az...@wso2.com wrote: Have we found a proper solution to this issue? I'm sure users will have custom libraries that they use which will require loading of properties files from the classpath. So we need to sort this out, if it has not already been sorted out. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- Dushan Abeyruwan *Senior Software Engineer* *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Does the XSLT mediator in ESB support XPath 2.0
___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Achala Aponso Software Engineer; WSO2 Inc.; http://wso2.com, Email: ach...@wso2.com Mobile: +94 (77) 5234925 Blog: http://achala11.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Build failure Apache Synapse - Core
/ConfigurationFactoryAndSerializerFinder.java:[117,22] sun.misc.Service is Sun proprietary API and may be removed in a future release [ERROR] [ERROR] /home/malinga/work/repo/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/core/src/main/java/org/apache/synapse/config/xml/StartupFinder.java:[115,25] sun.misc.Service is Sun proprietary API and may be removed in a future release [ERROR] - [Help 1] -- -Malinga ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Using DBReport mediator with a stored procedure
Dblookup will probably work. There was a sample. Sent from my iPhone On Jun 20, 2012, at 7:36 AM, Prabath Abeysekera praba...@wso2.com wrote: Hi Buddhika, On Wed, Jun 20, 2012 at 5:12 AM, Buddhika Chamith buddhi...@wso2.com wrote: Hi, Is it possible to use DBReport mediator to call a stored procedure having both IN and OUT parameters? So basically we want to get some return value from the procedure by invoking it with a set of parameters. AFAIR, you cannot handle any returning result using DBReport mediator. You should only be able to use it with IN parameters. Regards Buddhika ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Prabath Abeysekara Software Engineer WSO2 Inc. Email: praba...@wso2.com Mobile: +94774171471 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [ANN] WSO2 API Manager 1.0.0-ALPHA Released
] - Add Secure Vault Support to the api-manager.xml New Feature - [APISTORE-270 https://wso2.org/jira/browse/APISTORE-270] - Provision to make API keys foward compatible when a new version of API is available - [APISTORE-272 https://wso2.org/jira/browse/APISTORE-272] - Provide deprecate all older API versions option - [APISTORE-275 https://wso2.org/jira/browse/APISTORE-275] - Self registration functionality for API subscriber - [APISTORE-317 https://wso2.org/jira/browse/APISTORE-317] - Support a Master/Super Key Concept at the Application Level - [APISTORE-319 https://wso2.org/jira/browse/APISTORE-319] - Option to Deprecate Older Versions of an API, When a New Version is Published - [APISTORE-320 https://wso2.org/jira/browse/APISTORE-320] - Option to Make API Keys Forward Compatible Task - [APISTORE-164 https://wso2.org/jira/browse/APISTORE-164] - Review the package name - [APISTORE-304 https://wso2.org/jira/browse/APISTORE-304] - Implement View/Read Documentation Feature in API Store *Feel Like Contributing?* We highly appreciate your feedback on this release. Please report any issues at https://wso2.org/jira/browse/APISTORE. If you want to see a particular feature changed or improved, drop us a mail at dev@wso2.org or architect...@wso2.org. Full source code of this release can be checked out from https://svn.wso2.org/repos/wso2/tags/apimgt/1.0.0-alpha/ Thanks, - WSO2 API Manager Team - -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 ESB API problem
) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:143) at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927) at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:48) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:999) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:565) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1620) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 ESB API problem
Can you debug into Synapse and see why the API context does not get removed
from the path in the first case? That's how it's supposed to work. From the
API class:
if (restURLPostfix.startsWith(context)) {
restURLPostfix = restURLPostfix.substring(context.length());
if (versionStrategy instanceof URLBasedVersionStrategy) {
String version = versionStrategy.getVersion();
if (restURLPostfix.startsWith(version)) {
restURLPostfix =
restURLPostfix.substring(version.length());
} else if (restURLPostfix.startsWith(/ + version)) {
restURLPostfix =
restURLPostfix.substring(version.length() + 1);
}
}
((Axis2MessageContext)
synCtx).getAxis2MessageContext().setProperty(
NhttpConstants.REST_URL_POSTFIX, restURLPostfix);
}
Thanks,
Hiranya
On Wed, Jun 13, 2012 at 2:35 PM, Rajika Kumarasiri raj...@wso2.com wrote:
I changed the configuration with following and it completely removed
everything after the context /stockquote and back end complains that the
operation can't be found because now there is no operation for dispatching
in the url.
property name=REST_URL_POSTFIX action=remove scope=axis2/
The trace from ESB to service:
GET /services/MobileDirectoryService HTTP/1.1
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Accept: */*
Host: 127.0.0.1:9768
Connection: Keep-Alive
User-Agent: Synapse-HttpComponents-NIO
On Wed, Jun 13, 2012 at 2:06 PM, Hiranya Jayathilaka hira...@wso2.comwrote:
Remove the rest url postfix property.
On Wed, Jun 13, 2012 at 12:52 PM, Rajika Kumarasiri raj...@wso2.comwrote:
Same work for following proxy definition for the curl request, curl -X
GET http://localhost:8283/services/StockQuoteProxy/mobile/bbb
proxy name=StockQuoteProxy
target
endpoint
address uri=
http://localhost:9768/services/MobileDirectoryService; format=rest/
/endpoint
outSequence
send/
/outSequence
/target
/proxy
The trace is now,
client to ESB:
GET /services/StockQuoteProxy/mobile/bbb HTTP/1.1
User-Agent: curl/7.21.7 (x86_64-redhat-linux-gnu) libcurl/7.21.7 NSS/
3.12.10.0 zlib/1.2.5 libidn/1.22 libssh2/1.2.7
Host: 127.0.0.1:8283
Accept: */*
ESB to service:
GET /services/MobileDirectoryService/mobile/bbb HTTP/1.1
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Accept: */*
Host: 127.0.0.1:9768
Connection: Keep-Alive
User-Agent: Synapse-HttpComponents-NIO
Rajika
On Wed, Jun 13, 2012 at 12:27 PM, Rajika Kumarasiri raj...@wso2.comwrote:
I am trying to use an API to proxy a back end REST service. My
API deceleration is given below. I have avoided using any url-pattern or
template in order to define a pass thru API.
api name=StockQuoteAPI context=/stockquote
resource methods=POST GET
inSequence
send
endpoint
address uri=
http://localhost:9768/services/MobileDirectoryService;
format=rest/
/endpoint
/send
/inSequence
outSequence
send/
/outSequence
/resource
/api
I invoked the API using the curl option, curl -X GET
http://localhost:8283/stockquote/mobile/bbb but ended up with the
error[1] in the back end. The request message trace is given below.
client to ESB:
GET /stockquote/mobile/bbb HTTP/1.1
User-Agent: curl/7.21.7 (x86_64-redhat-linux-gnu) libcurl/7.21.7 NSS/
3.12.10.0 zlib/1.2.5 libidn/1.22 libssh2/1.2.7
Host: 127.0.0.1:8283
Accept: */*
ESB to back end rest service:
POST /services/MobileDirectoryService/stockquote/mobile/bbb HTTP/1.1
Content-Type: application/xml; charset=UTF-8
Accept: */*
Transfer-Encoding: chunked
Host: 127.0.0.1:9768
Connection: Keep-Alive
User-Agent: Synapse-HttpComponents-NIO
It seems problem occurs due to dispatching error of the context
/stockquote. Any idea to fix the problem ?
Rajika
[1] -
2012-06-13 12:17:35,441] ERROR {org.apache.axis2.engine.AxisEngine} -
The endpoint reference (EPR) for the Operation not found is
/services/MobileDirectoryService/stockquote/mobile/bbb and the WSA Action =
null. If this EPR was previously reachable, please contact the server
administrator.
org.apache.axis2.AxisFault: The endpoint reference (EPR) for the
Operation not found is
/services/MobileDirectoryService/stockquote/mobile/bbb and the WSA Action =
null. If this EPR was previously reachable, please contact the server
administrator.
at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:102)
at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
at org.apache.axis2.engine.AxisEngine.invoke
Re: [Dev] Performance testing/load testing with Cassandra appender
On Mon, Jun 11, 2012 at 5:38 PM, Buddhika Chamith buddhi...@wso2.comwrote: On Mon, Jun 11, 2012 at 6:03 PM, Paul Fremantle p...@wso2.com wrote: Does the BAM event sender implement and in-memory queueing model and async? Yes. Event publishing happen via a queue in an async manner. Based on what I have seen in the API Manager + BAM load tests, things can still fail badly when running with a single BAM node and an embedded Cassandra instance. So whatever we do, we should load test it beforehand and scale them up accordingly. Thanks, Hiranya Regards Buddhika Paul On 11 June 2012 11:40, Afkham Azeez az...@wso2.com wrote: Regardless of the appender, such appenders that publish events could have an effect on performance. On Mon, Jun 11, 2012 at 12:21 PM, Amani am...@wso2.com wrote: Actually we are not using the Cassandra appender. Instead of that we are using LogEventAppender which sends logs to BAM. Cassandra appender was something we implemented earlier before we decided to send logs to BAM. We will test LogEventAppender and send the result once we complete it. Right now we are having issues publishing log events to BAM. Sent from my iPhone On Jun 11, 2012, at 12:01 PM, Afkham Azeez az...@wso2.com wrote: I have a major concern about this appender with regards to performance. If it leads to major performance issues, we cannot use it. Amani, can you do some tests which do logging with without the Cassandra appender send the results? -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: ** http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB_HOME/lib/core/WEB-INF/classes Property files are not loading
Pradeep,
any feedback on this?
Thanks,
Hiranya
On Thu, Jun 7, 2012 at 1:55 PM, Hiranya Jayathilaka hira...@wso2.comwrote:
A quick follow up question on this. The Axis2 transports also load all
properties files using the classloader:
ClassLoader cl = Thread.currentThread().getContextClassLoader();
if (log.isDebugEnabled()) {
log.debug(Loading a file ' + filePath + ' from classpath);
}
InputStream in = cl.getResourceAsStream(filePath);
How would this work in the Carbon trunk?
Thanks,
Hiranya
On Thu, May 24, 2012 at 7:14 PM, Afkham Azeez az...@wso2.com wrote:
I don't like this System property name. config.location=repository/conf
sounds better. No need to give $CARBON_HOME because the current directory
is set to CARBON_HOME. We shouldn't be putting config files into lib.
On Thu, May 24, 2012 at 5:59 PM, Dushan Abeyruwan dus...@wso2.comwrote:
Hi
Based on the discussions its agreed to go with the System property
method where at the wso2server.sh will define a new system property
* -Dproperties.hosted.location=$CARBON_HOME/lib\*
a customziable location where during the property initialization at the
synapse_common (MiscellaneousUtil.java) will first looking to the
externally defined location and if exists the properties will be loading
from the given location rather than looking in to its class path location
(if not it will proceed with the old way like looking in to the classpath
resources)
public static Properties loadProperties(String filePath) {
InputStream in = null;
//if we reach to this assume that the we may have to looking to
the customer provided external location for the
* //given properties*
* if (System.getProperty(PROPERTIES_HOSTED_LOCATION) != null) {*
* try {*
* in = new
FileInputStream(System.getProperty(PROPERTIES_HOSTED_LOCATION) +
File.separator + filePath);*
* } catch (FileNotFoundException e) {*
* String msg = Error loading properties from a file at from the System
defined location: + filePath;*
* log.warn(msg);*
* }*
* }*
if (in == null) {
in = cl.getResourceAsStream(filePath);
if (log.isDebugEnabled()) {
log.debug(Unable to load file ' + filePath + ');
}
filePath = conf +
File.separatorChar + filePath;
if (log.isDebugEnabled()) {
log.debug(Loading a file ' + filePath + ' from
classpath);
}
.
.
thus chagers will be effected
1.MiscellaneousUtil.java synapse-commons
2.
wso2svntrunk/carbon/platform/trunk/build/setup/esb/bin/wso2server.sh
Will initiate separate synapse jira issue for
the changers introduced
cheers
Dushan
On Thu, May 24, 2012 at 1:40 PM, Dushan Abeyruwan dus...@wso2.comwrote:
Hi
Based on the discussion ,
1. I just placed all properties to
CARBON_HOME/repository/conf/tomcat/carbon/WEB-INF/classes (i just create
classes folder) there , and seems like the property files are not visible
in the class path,
2. As Pradeep told fragment bundle concept just like log4j its and
its working properly
3. define *Dsysnapse.nhtt**p.property.file = .. i *am
not sure this if we gonna load properties like this because we may have to
do some synapse code modification in order to load these property file (but
synapse is 3rd party lib do we need to change synapse because of this ???
but this option i am not a great fan..
cheers
Dushan
On Tue, May 22, 2012 at 5:15 PM, Afkham Azeez az...@wso2.com wrote:
In previous releases we have been placing all properties files in
CARBON_HOME/lib/core/WEB-INF/classes, and they became visible to bundles
through the Carbon webapp's WebappClassloader
See
http://web.archiveorange.com/archive/v/bdAOJ2bORkxfNxgxjKUb
On Tue, May 22, 2012 at 2:25 PM, Hiranya Jayathilaka hira...@wso2.com
wrote:
On Tue, May 22, 2012 at 2:01 PM, Pradeep Fernando
prad...@wso2.comwrote:
On Tue, May 22, 2012 at 2:01 PM, Pradeep Fernando prad...@wso2.com
wrote:
Hi,
On Tue, May 22, 2012 at 1:41 PM, Hiranya Jayathilaka
hira...@wso2.com wrote:
So Synapse looks for the config files in appClassPath. How do we
include a
config file in appClassPath with the current model?
yes, correct. I was just explaining the config file search order
convention. Getting configs from appClassPath is not possible with
OSGi technology. That is where system property comes in to picture.
May I know how it uses to work in previous releases?
Thanks,
Hiranya
thanks,
--pradeep
--
Pradeep Fernando
Senior Software Engineer
Member, Management Committee - Platform Cloud Technologies
WSO2 Inc; http://wso2.com/
blog: http://pradeepfernando.blogspot.com/
m: +94776603662
--
Hiranya Jayathilaka
Senior Technical Lead;
WSO2 Inc
Re: [Dev] Nio and pass through transports are blocker to access virtual host in LB
Synapse doesn't have much control over this. Host header is set by HTTP Core protocol handlers, as it's a HTTP protocol requirement. We should debug into the equestTargetHost ( http://hc.apache.org/httpcomponents-core-ga/httpcore/apidocs/org/apache/http/protocol/RequestTargetHost.html) and see what's going on there. Thanks, Hiranya On Tue, Jun 12, 2012 at 10:01 AM, Kasun Indrasiri ka...@wso2.com wrote: I did the fix from synapse level, but still the value written as the host is overridden from http-core. I'm investigating on this and will provide a solution today, On Mon, Jun 11, 2012 at 11:34 AM, Reka Thirunavukkarasu r...@wso2.comwrote: Hi Kasun, Can we get some update regarding the issue, since we are highly depending on the virtual host in AS? Does it require more underlying change? Thanks, Reka On Fri, Jun 1, 2012 at 10:34 AM, Sanjeewa Malalgoda sanje...@wso2.com wrote: Any way we cant use passthrogh transport for LB because it has other bug which was discussed on a separate thread. And dushan is currently looking onto it. so we have to focus on nhttp at the moment. Thanks. On Fri, Jun 1, 2012 at 10:27 AM, Kasun Indrasiri ka...@wso2.com wrote: Hi Reka, I'm working on a fix for this issue. On Fri, Jun 1, 2012 at 10:25 AM, Reka Thirunavukkarasu r...@wso2.com wrote: Hi, We have configured LB with AS in order to check the context mapping to webapps. Since the context mapping is done through virtual host in AS, we should be able to access virtual host (say testapp.wso2.com) from browser with the url: https://testapp.wso2.com:9443/ where 9443 is the AS-https port. So, when we have LB in front of AS, let's say 8280 is LB-https port, then we can access the virtual host from LB like https://testapp.wso2.com:8280/. But this falis, and redirecting to carbon management consloe, since the Host header is overwritten with host name from url (Eg: loacalhost) instead of actual host information. But when we checked this with LB, after few modification in synapse, Http host header is properly added. Even after that also, AS didn't receive the actual host. Also, we experienced the same issue with Nio and pass through transport as well. Since the host header is available at LB level, this needs further invstigation in tranport level. We need to resolve it, since it is a blocker for accessing virtual host. So, the jira has been created: https://wso2.org/jira/browse/CARBON-13377 Thanks, Reka -- Kasun Indrasiri Associate Technical Lead WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 71 536 4128 Blog : http://kasunpanorama.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sanjeewa Malalgoda mobile : +94 713068779 blog :http://sanjeewamalalgoda.blogspot.com/ -- Kasun Indrasiri Associate Technical Lead WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 71 536 4128 Blog : http://kasunpanorama.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] sending an email on exceptions.
There's a SMTP appender - http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/net/SMTPAppender.html Thanks, Hiranya On Sat, Jun 9, 2012 at 4:03 PM, Senaka Fernando sen...@wso2.com wrote: Hi Zana, Yes. We use log4j and you should be able to Google and find some log4j to e-mail appenders AFAIU. Please also be kind to share anything found that you think useful for the dev@ community as well. Regards, Senaka. On Fri, Jun 8, 2012 at 3:09 PM, zana ilhan zanail...@gmail.com wrote: Hi All, Is there a functionality of Carbon/Stratos based server like that, When a error log created on a server's log(e.g. wso2carbon.log) file then the server will send a mail. -- Best Regards Zana İlhan ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Senaka Fernando* Member - Integration Technologies Management Committee; Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Governance Error in API Manager
Hi Folks, We can no longer publish APIs in API Manager due to a governance error: [2012-06-08 19:21:30,763] ERROR - GovernanceArtifactManager An identical resource already exists in the defined path To make sure that I haven't missed anything, I built both kernel and the platform from a latest revision (r129598). So it can't be due to a partial update in the distribution. This error started to happen without us doing any notable changes in the code. So it has to be regression in the governance/registry components. Appreciate some help to get this resolved asap. Thanks -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Governance Error in API Manager
Hi, On Sat, Jun 9, 2012 at 7:49 AM, Ajith Vitharana aji...@wso2.com wrote: On Fri, Jun 8, 2012 at 7:25 PM, Hiranya Jayathilaka hira...@wso2.comwrote: Hi Folks, We can no longer publish APIs in API Manager due to a governance error: [2012-06-08 19:21:30,763] ERROR - GovernanceArtifactManager An identical resource already exists in the defined path To make sure that I haven't missed anything, I built both kernel and the platform from a latest revision (r129598). So it can't be due to a partial update in the distribution. This error started to happen without us doing any notable changes in the code. So it has to be regression in the governance/registry components. Appreciate some help to get this resolved asap. Hi Hiranya, This is a regression issue of a fix made by IsuruW. I revet that commits to fix this issue. Please take a svn update of governance and apimgt component and build. I checked the latest API Manager pack locally, now it is working fine. Thanks for the prompt action guys. I'll take an update and try. Thanks, Hiranya Thanks Ajith Thanks -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794 -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB_HOME/lib/core/WEB-INF/classes Property files are not loading
A quick follow up question on this. The Axis2 transports also load all
properties files using the classloader:
ClassLoader cl = Thread.currentThread().getContextClassLoader();
if (log.isDebugEnabled()) {
log.debug(Loading a file ' + filePath + ' from classpath);
}
InputStream in = cl.getResourceAsStream(filePath);
How would this work in the Carbon trunk?
Thanks,
Hiranya
On Thu, May 24, 2012 at 7:14 PM, Afkham Azeez az...@wso2.com wrote:
I don't like this System property name. config.location=repository/conf
sounds better. No need to give $CARBON_HOME because the current directory
is set to CARBON_HOME. We shouldn't be putting config files into lib.
On Thu, May 24, 2012 at 5:59 PM, Dushan Abeyruwan dus...@wso2.com wrote:
Hi
Based on the discussions its agreed to go with the System property
method where at the wso2server.sh will define a new system property
* -Dproperties.hosted.location=$CARBON_HOME/lib\*
a customziable location where during the property initialization at the
synapse_common (MiscellaneousUtil.java) will first looking to the
externally defined location and if exists the properties will be loading
from the given location rather than looking in to its class path location
(if not it will proceed with the old way like looking in to the classpath
resources)
public static Properties loadProperties(String filePath) {
InputStream in = null;
//if we reach to this assume that the we may have to looking to
the customer provided external location for the
* //given properties*
* if (System.getProperty(PROPERTIES_HOSTED_LOCATION) != null) {*
* try {*
* in = new
FileInputStream(System.getProperty(PROPERTIES_HOSTED_LOCATION) +
File.separator + filePath);*
* } catch (FileNotFoundException e) {*
* String msg = Error loading properties from a file at from the System
defined location: + filePath;*
* log.warn(msg);*
* }*
* }*
if (in == null) {
in = cl.getResourceAsStream(filePath);
if (log.isDebugEnabled()) {
log.debug(Unable to load file ' + filePath + ');
}
filePath = conf +
File.separatorChar + filePath;
if (log.isDebugEnabled()) {
log.debug(Loading a file ' + filePath + ' from
classpath);
}
.
.
thus chagers will be effected
1.MiscellaneousUtil.java synapse-commons
2.
wso2svntrunk/carbon/platform/trunk/build/setup/esb/bin/wso2server.sh
Will initiate separate synapse jira issue for
the changers introduced
cheers
Dushan
On Thu, May 24, 2012 at 1:40 PM, Dushan Abeyruwan dus...@wso2.comwrote:
Hi
Based on the discussion ,
1. I just placed all properties to
CARBON_HOME/repository/conf/tomcat/carbon/WEB-INF/classes (i just create
classes folder) there , and seems like the property files are not visible
in the class path,
2. As Pradeep told fragment bundle concept just like log4j its and
its working properly
3. define *Dsysnapse.nhtt**p.property.file = .. i *am not
sure this if we gonna load properties like this because we may have to do
some synapse code modification in order to load these property file (but
synapse is 3rd party lib do we need to change synapse because of this ???
but this option i am not a great fan..
cheers
Dushan
On Tue, May 22, 2012 at 5:15 PM, Afkham Azeez az...@wso2.com wrote:
In previous releases we have been placing all properties files in
CARBON_HOME/lib/core/WEB-INF/classes, and they became visible to bundles
through the Carbon webapp's WebappClassloader
See
http://web.archiveorange.com/archive/v/bdAOJ2bORkxfNxgxjKUb
On Tue, May 22, 2012 at 2:25 PM, Hiranya Jayathilaka
hira...@wso2.comwrote:
On Tue, May 22, 2012 at 2:01 PM, Pradeep Fernando prad...@wso2.comwrote:
On Tue, May 22, 2012 at 2:01 PM, Pradeep Fernando prad...@wso2.com
wrote:
Hi,
On Tue, May 22, 2012 at 1:41 PM, Hiranya Jayathilaka
hira...@wso2.com wrote:
So Synapse looks for the config files in appClassPath. How do we
include a
config file in appClassPath with the current model?
yes, correct. I was just explaining the config file search order
convention. Getting configs from appClassPath is not possible with
OSGi technology. That is where system property comes in to picture.
May I know how it uses to work in previous releases?
Thanks,
Hiranya
thanks,
--pradeep
--
Pradeep Fernando
Senior Software Engineer
Member, Management Committee - Platform Cloud Technologies
WSO2 Inc; http://wso2.com/
blog: http://pradeepfernando.blogspot.com/
m: +94776603662
--
Hiranya Jayathilaka
Senior Technical Lead;
WSO2 Inc.; http://wso2.org
E-mail: hira...@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
Re: [Dev] Is API Manager in Bamboo?
On Wed, Jun 6, 2012 at 6:10 PM, Paul Fremantle p...@wso2.com wrote: $subject? No, it's not a part of the default build profile yet. We'll add it once the alpha is out. Thanks, Hiranya Paul -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Java OOM Error due to ActivationHandler class logging the Incoming Message
On Thu, Jun 7, 2012 at 10:33 AM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi, I encountered Java OutOfMemoryError while testing ESB Smooks Mediator with big messages. at org.wso2.carbon.activation.module.ActivationHandler.invoke(ActivationHandler.java:51) at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340) at org.apache.axis2.engine.Phase.invoke(Phase.java:313) This occurs because ActivationHandler class of stratos org.wso2.carbon.activation component logs the message as follows. log.debug(Staring Activation Handler invocation. Incoming Message: + messageContext.getEnvelope().toString()); It's not optional :) Please fix this asap. This causes all messages to get built in memory unconditionally. Wonder if SLive is also vulnerable to this. A few large messages will bring the whole thing down. Thanks. Hiranya Shall we change this to log only when debug mode is enabled? Thanks, Lakmali -- Lakmali Baminiwatta* * Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware * * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Cannot create a proxy service with a JMX target endpoint using the Proxy Service creation UI
) at org.apache.jsp.admin.layout.template_jsp._jspService(template_jsp.java:282) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:161) at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:471) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:402) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:329) at org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.forward(RequestDispatcherAdaptor.java:30) at org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.forward(ContextPathServletAdaptor.java:258) at org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(ServletTilesRequestContext.java:198) at org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(ServletTilesRequestContext.java:185) at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:419) at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:370) at org.wso2.carbon.ui.action.ActionHelper.render(ActionHelper.java:52) at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:101) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet. The Endpoint was: jms:/HelloService?transport.jms.DestinationType=queuetransport.jms.ContentTypeProperty=Content-Typejava.naming.provider.url=tcp://localhost:61616java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactorytransport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory There is no error shown to the user on the UI! -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] More issues with statistics persistence!
) at org.wso2.carbon.registry.core.session.UserRegistry.get(UserRegistry.java:516) at org.wso2.carbon.statistics.persistance.StatisticsPersistenceScheduler.persistServiceStatistics(StatisticsPersistenceScheduler.java:101) at org.wso2.carbon.statistics.persistance.StatisticsPersistenceScheduler.invoke(StatisticsPersistenceScheduler.java:38) at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.invokeCarbonDeploymentSchedulerExtenders(CarbonDeploymentSchedulerTask.java:101) -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB sample configurations
On Thu, May 31, 2012 at 8:37 PM, Amila Suriarachchi am...@wso2.com wrote: hi, is this sample configuration given here[1] correct? I think we can not write switch mediator directly under definition. We used to support this syntax. Not sure whether it works any more. In any case it's not a recommended style. Thanks, Hiranya But esb samples contains the correct code. thanks, Amila. [1] http://wso2.org/project/esb/java/4.0.3/docs/samples/message_mediation_samples.html#Sample2 -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [ANN] WSO2 API Manager 1.0.0-M6 Released
WSO2 API Manager 1.0.0-M6 can be downloaded from http://people.wso2.com/~hiranya/wso2am-1.0.0-M6.zip This milestone release comes with the new and improved API provider and API store webapps, BAM support and much more. Please refer the road map summary below for more information. *How to run samples?* * * Following steps explain how to get samples up and running: 1. Download extract wso2am-1.0.0-M6.zip 2. Go to 'samples' folder. 3. There are 3 samples, namely: - TwitterSearch - YahooPlaceFinder - YoutubeFeeds 4. README.txt inside each of the sample folder provides complete instructions on deploying testing sample scenarios. 5. To learn how to configure statistics monitoring, read WSO2AM-HOME/StatClient/README.txt You need to have Apache Ant 1.8 or higher to run the samples. *New Features, Bug Fixes and Improvements (Road Map Summary)* Bug - [APISTORE-63 https://wso2.org/jira/browse/APISTORE-63] - API Manager login should be over HTTPS - [APISTORE-102 https://wso2.org/jira/browse/APISTORE-102] - Cannot login to API Provider - when the default ports of the API Manager being changed - [APISTORE-215 https://wso2.org/jira/browse/APISTORE-215] - Cancel Button in API Edit Page Doesn't Work - [APISTORE-232 https://wso2.org/jira/browse/APISTORE-232] - UI let's me create two applications with same name, which leads to all kind of issues. - [APISTORE-255 https://wso2.org/jira/browse/APISTORE-255] - API Usage Handler Fails When Invoked without an Authorization (OAuth) Header - [APISTORE-284 https://wso2.org/jira/browse/APISTORE-284] - API Status assignment being confused Improvement - [APISTORE-3 https://wso2.org/jira/browse/APISTORE-3] - Role based security for edit/view of API meta-data categories - [APISTORE-213 https://wso2.org/jira/browse/APISTORE-213] - Tier Availability Should be Optional for an API - [APISTORE-223 https://wso2.org/jira/browse/APISTORE-223] - Improvements in the My Applications Page - [APISTORE-293 https://wso2.org/jira/browse/APISTORE-293] - User Management Changes Agreed on April 25th - Roles and API visibility - [APISTORE-294 https://wso2.org/jira/browse/APISTORE-294] - Ownership Information : As Agreed on April 25th Meeting - [APISTORE-311 https://wso2.org/jira/browse/APISTORE-311] - Show a Popup Dialog When Making a Subscription - [APISTORE-312 https://wso2.org/jira/browse/APISTORE-312] - Need a Loading Screen for the Charts/Stats - [APISTORE-313 https://wso2.org/jira/browse/APISTORE-313] - Need a nicer No Data Found screen New Feature - [APISTORE-292 https://wso2.org/jira/browse/APISTORE-292] - Add check box to disable publication of APIs to API Gateway Task - [APISTORE-198 https://wso2.org/jira/browse/APISTORE-198] - Need to select the tier when adding a subscription - [APISTORE-211 https://wso2.org/jira/browse/APISTORE-211] - Add apimgt/config/throttle-policies/src to product build - [APISTORE-236 https://wso2.org/jira/browse/APISTORE-236] - Application name should be unique for a given subscriber - [APISTORE-291 https://wso2.org/jira/browse/APISTORE-291] - Support Multiple HTTP Methods in Resources - [APISTORE-305 https://wso2.org/jira/browse/APISTORE-305] - Implement Delete Feature for Applications Thanks, WSO2 API Manager Team -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] CHECKOUT_BEFORE_CHECK_IN error in Deployment Synchronizer Write Only mode
In the initial implementation I did, the synchronizer would run one checkout/update at the startup regardless of the configuration. Is this not the case anymore? Sent from my iPhone On May 29, 2012, at 9:41 PM, Nuwan Dias nuw...@wso2.com wrote: On Tue, May 29, 2012 at 5:49 PM, Afkham Azeez az...@wso2.com wrote: On Tue, May 29, 2012 at 5:36 PM, Nuwan Dias nuw...@wso2.com wrote: Hi, Resolved the issue stating that this is not a bug. Will enhance the UI so that autoCheckOut will automatically be enabled if autoCheckIn is enabled. Rather, what you should do is, if autoCheckin is on, regardless of the autoCheckout parameter, you must do the checking out. i.e. autoCheckout is ignored if autoCheckin is ON. It is not a UI only thing. Please improve the depsync code to handle this. We must minimize user errors. Understood, will do the necessary changes. Thanks, NuwanD. Thanks, On Tue, May 29, 2012 at 5:28 PM, Charitha Kankanamge chari...@wso2.com wrote: On Tue, May 29, 2012 at 5:26 PM, Afkham Azeez az...@wso2.com wrote: On Tue, May 29, 2012 at 5:02 PM, Charitha Kankanamge chari...@wso2.com wrote: Hi Nuwan, I raised the same question in [Dev] WSO2 Carbon Beta Packs for QA thread sometime back but did not get a reply hence reported the jira. Should the admin node be started with both auto-commit and auto-checkout set to true? Yes, obviously. Think of SVN. Is it possible to commit to an SVN repo if you have not checked out first? :) correct. On Tue, May 29, 2012 at 4:24 PM, Nuwan Dias nuw...@wso2.com wrote: Hi, In the issue at https://wso2.org/jira/browse/CARBON-13108, it has been reported that a CHECKOUT_BEFORE_CHECK_IN error occurs when using the Registry based deployment synchronization in WRITE_ONLY mode (autoCheckOut=false, autoCheckIn=true). This error is caused due to the CheckInCommand failing to find the meta files directory which is normally created during the first registry checkout. Is running a node in WRITE_ONLY mode logical? If so, how should we address this issue? Thanks, -- Nuwan Dias Software Engineer - WSO2, Inc. Integration Technologies Team email : nuw...@wso2.com Phone : +94 777 775 729 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Afkham Azeez Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ email: az...@wso2.com cell: +94 77 3320919 blog: http://blog.afkham.org twitter: http://twitter.com/afkham_azeez linked-in: http://lk.linkedin.com/in/afkhamazeez Lean . Enterprise . Middleware -- Nuwan Dias Software Engineer - WSO2, Inc. Integration Technologies Team email : nuw...@wso2.com Phone : +94 777 775 729 -- Afkham Azeez Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ email: az...@wso2.com cell: +94 77 3320919 blog: http://blog.afkham.org twitter: http://twitter.com/afkham_azeez linked-in: http://lk.linkedin.com/in/afkhamazeez Lean . Enterprise . Middleware -- Nuwan Dias Software Engineer - WSO2, Inc. Integration Technologies Team email : nuw...@wso2.com Phone : +94 777 775 729 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] CHECKOUT_BEFORE_CHECK_IN error in Deployment Synchronizer Write Only mode
On Wed, May 30, 2012 at 7:55 AM, Kasun Gajasinghe kas...@wso2.com wrote: On Wed, May 30, 2012 at 7:57 AM, Hiranya Jayathilaka hira...@wso2.comwrote: In the initial implementation I did, the synchronizer would run one checkout/update at the startup regardless of the configuration. Is this not the case anymore? This *is* the case when the server start-up. I believe Nuwan is talking about enabling the depsync via ui. It was implemented in a way so that the checkout/update will be executed once at the initialization of the synchronizer. So at least in the past releases it would run once regardless of how you enable the synchronizer or what your configuration is. Looks like that's not the case anymore. Thanks, Hiranya Regards, --KasunG Sent from my iPhone On May 29, 2012, at 9:41 PM, Nuwan Dias nuw...@wso2.com wrote: On Tue, May 29, 2012 at 5:49 PM, Afkham Azeez az...@wso2.com az...@wso2.com wrote: On Tue, May 29, 2012 at 5:36 PM, Nuwan Dias nuw...@wso2.com nuw...@wso2.com wrote: Hi, Resolved the issue stating that this is not a bug. Will enhance the UI so that autoCheckOut will automatically be enabled if autoCheckIn is enabled. Rather, what you should do is, if autoCheckin is on, regardless of the autoCheckout parameter, you must do the checking out. i.e. autoCheckout is ignored if autoCheckin is ON. It is not a UI only thing. Please improve the depsync code to handle this. We must minimize user errors. Understood, will do the necessary changes. Thanks, NuwanD. Thanks, On Tue, May 29, 2012 at 5:28 PM, Charitha Kankanamge chari...@wso2.com chari...@wso2.com wrote: On Tue, May 29, 2012 at 5:26 PM, Afkham Azeez az...@wso2.com az...@wso2.com wrote: On Tue, May 29, 2012 at 5:02 PM, Charitha Kankanamge chari...@wso2.com chari...@wso2.com wrote: Hi Nuwan, I raised the same question in [Dev] WSO2 Carbon Beta Packs for QA thread sometime back but did not get a reply hence reported the jira. Should the admin node be started with both auto-commit and auto-checkout set to true? Yes, obviously. Think of SVN. Is it possible to commit to an SVN repo if you have not checked out first? :) correct. On Tue, May 29, 2012 at 4:24 PM, Nuwan Dias nuw...@wso2.com nuw...@wso2.com wrote: Hi, In the issue at https://wso2.org/jira/browse/CARBON-13108 https://wso2.org/jira/browse/CARBON-13108, it has been reported that a CHECKOUT_BEFORE_CHECK_IN error occurs when using the Registry based deployment synchronization in WRITE_ONLY mode (autoCheckOut=false, autoCheckIn=true). This error is caused due to the CheckInCommand failing to find the meta files directory which is normally created during the first registry checkout. Is running a node in WRITE_ONLY mode logical? If so, how should we address this issue? Thanks, -- Nuwan Dias Software Engineer - WSO2, Inc. Integration Technologies Team email : nuw...@wso2.comnuw...@wso2.com Phone : +94 777 775 729 ___ Dev mailing list Dev@wso2.orgDev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: ** http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- Nuwan Dias Software Engineer - WSO2, Inc. Integration Technologies Team email : nuw...@wso2.comnuw...@wso2.com Phone : +94 777 775 729 -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: ** http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- Nuwan Dias Software Engineer - WSO2, Inc. Integration Technologies Team email : nuw...@wso2.comnuw...@wso2.com Phone : +94 777 775 729 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kasun Gajasinghe* Software Engineer; Development Technologies Team, WSO2 Inc.; http://wso2.com , *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* *linked-in: *http
Re: [Dev] Create a Role Programmatically in Carbon
Thank you all. Great feedback. Thanks, Hiranya On Wed, May 30, 2012 at 8:19 AM, Dimuthu Leelarathne dimut...@wso2.comwrote: Hi Hiranya, On Tue, May 29, 2012 at 9:03 PM, Rajika Kumarasiri raj...@wso2.comwrote: See towards line 75 below. https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/csg/org.wso2.carbon.cloud.csg.agent/src/main/java/org/wso2/carbon/cloud/csg/agent/internal/CSGAgentServiceComponent.java This is the correct way of doing it if you are calling within the server itself. thanks, dimuthu Rajika On Tue, May 29, 2012 at 6:33 PM, Hiranya Jayathilaka hira...@wso2.comwrote: I want to $subject. What API/Admin service should I use? Can somebody please point me to some sample code? Thanks -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dimuthu Leelarathne Technical Lead WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Lean . Enterprise . Middleware -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Impact of C-App deployer changes on ESB artifacts
On Mon, May 21, 2012 at 4:26 PM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: One more thing we discussed was, ESB checks the dependency at the deployment time. For example, if a proxy service depends on a sequence, it validates whether the sequence exist when trying to deploy proxy service. (e.g proxy service in one car file and sequence in another car file.. now we have to order the car file deployment). There is no such validation mechanism in ESB. A proxy service deployment will fail only if the publish WSDL (or the WSDL referenced by a WSDL endpoint) cannot be loaded at deployment time. Thanks, Hiranya We discussed this with Paul and the decision is, we should change this behavior so that the validation happens with first message arrived, not at the time of deployment. Hiranya, how hard is it to do that? Regards, Shankar On Mon, May 21, 2012 at 4:10 PM, Isuru Suriarachchi is...@wso2.comwrote: Hi all, As per few discussions we did on C-App deployment, we identified that the current C-App deployment process causes problems in cluster with deployment synchronizer. Currently the C-App deployer reads different artifacts and copy those into relevant hot directories in the Axis2 repository (repository/deployment/server/xxx). When these artifacts and the original C-App are synchronized to a different node, there are conflicts. So as a solution, I've already implemented a way in which the C-App extracts the individual artifacts into a temp directory and directly call the relevant deployer for the artifact. This works well for aar services etc. which won't get changed after first deployment. However, I wonder ESB artifacts will have a different impact on this because the user can edit the ESB configuration through the UI and then it internally get serialized to the original xml file in the repository. But in this new approach, original artifact will be in the temp directory. So will that be a problem from the ESB side? And also please let me know if there are any other possible downsides of this approach which you can think of. Thanks, ~Isuru -- Isuru Suriarachchi Technical Lead WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware -- S.Uthaiyashankar Senior Software Architect Chair, Management Committee – Cloud Technologies WSO2 Inc. http://wso2.com/ - lean . enterprise . middleware Phone: +94 714897591 -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [User] Problem with API in ESB
, and all it´s fine. curl http://127.0.0.1:9765/services/DatosUsuariosREST.HTTPEndpoint/datosusuario/1 Saludos, Ing. Jorge Infante Osorio. J´Dpto Soluciones SOA. CDAE. Fac. 5. UCI. 10mo. ANIVERSARIO DE LA CREACION DE LA UNIVERSIDAD DE LAS CIENCIAS INFORMATICAS... CONECTADOS AL FUTURO, CONECTADOS A LA REVOLUCION http://www.uci.cu http://www.facebook.com/universidad.uci http://www.flickr.com/photos/universidad_uci ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [ANN] WSO2 API Manager 1.0.0-M5 Released
I think we should wait till we get the alpha out to host the packs in OT.
These are basically developer releases.
Thanks,
Hiranya
On Thu, May 24, 2012 at 6:11 AM, Dasunpriya Anuradha anura...@wso2.comwrote:
Should we provide this download from .com API manager page? Or should we
announce it in our web site? Please advice.
Thanks.
On Wed, May 23, 2012 at 8:28 PM, Hiranya Jayathilaka hira...@wso2.comwrote:
WSO2 API Manager 1.0.0-M5 can be downloaded from
http://people.wso2.com/~hiranya/wso2am-1.0.0-M5.zip
This milestone release comes with the new and improved API provider and
API store webapps, BAM support and much more. Please refer the road map
summary below for more information. Some screenshots from the BAM
integration effort are attached herewith for your reference.
*How to run samples?*
*
*
Following steps explain how to get samples up and running:
1. Download extract wso2am-1.0.0-M5.zip
2. Go to 'samples' folder.
3. There are 3 samples, namely:
- TwitterSearch
- YahooPlaceFinder
- YoutubeFeeds
4. README.txt inside each of the sample folder provides complete
instructions on deploying testing sample scenarios.
5. To learn how to configure statistics monitoring, read
WSO2AM-HOME/StatClient/README.txt
You need to have Apache Ant 1.8 or higher to run the samples.
*New Features, Bug Fixes and Improvements (Road Map Summary)*
*
*
Bug
- [APISTORE-101 https://wso2.org/jira/browse/APISTORE-101] - Only
the users belong to the API_PROVIDER role should be able to add APIs from
the API Provider
- [APISTORE-240 https://wso2.org/jira/browse/APISTORE-240] - When
Creating APIs with Multiple Resources, The Default Resource Does Not Get
Added
- [APISTORE-241 https://wso2.org/jira/browse/APISTORE-241] - The
Default Resource is Restricted to GET Requests
- [APISTORE-281 https://wso2.org/jira/browse/APISTORE-281] - API
Provider JS resources not delivered in distribution
- [APISTORE-282 https://wso2.org/jira/browse/APISTORE-282] - API
Provider login authentication state not holding external reference to
github.com
- [APISTORE-283 https://wso2.org/jira/browse/APISTORE-283] - When
Editing API in APIProvider, JSON message displayed after 'Save': {data :
{}, message : {}, error : false}
- [APISTORE-287 https://wso2.org/jira/browse/APISTORE-287] -
Documentation Feature is Broken in the Latest API Provider App -
Intermittent Issues
- [APISTORE-289 https://wso2.org/jira/browse/APISTORE-289] - Add
Icon Option Does Not Work
- [APISTORE-290 https://wso2.org/jira/browse/APISTORE-290] - Icon
in the API Overview Tab is Not Properly Size-Controlled
- [APISTORE-303 https://wso2.org/jira/browse/APISTORE-303] - API
icon (thumbnail) issues
- [APISTORE-309 https://wso2.org/jira/browse/APISTORE-309] - All
Comments are Added as admin
- [APISTORE-310 https://wso2.org/jira/browse/APISTORE-310] - New
Line Characters in Documentation Content Messes up the Documentation Edit
Page
Improvement
- [APISTORE-8 https://wso2.org/jira/browse/APISTORE-8] - Standard
roles
- [APISTORE-220 https://wso2.org/jira/browse/APISTORE-220] - The
APi Rating Widget in the API Store is Not User Friendly
New Feature
- [APISTORE-222 https://wso2.org/jira/browse/APISTORE-222] -
Provide a New Application Button Near the Applications Drop Down in
the
API Overview Page
Task
- [APISTORE-193 https://wso2.org/jira/browse/APISTORE-193] - Check
all pom.xml for Maven3 compatibility
- [APISTORE-288 https://wso2.org/jira/browse/APISTORE-288] - Add
Statistics Monitoring Gadgets to the API Provider
- [APISTORE-306 https://wso2.org/jira/browse/APISTORE-306] - Test
and Verify SOAP Support
- [APISTORE-308 https://wso2.org/jira/browse/APISTORE-308] -
Introduce new themes to API Provider
Sub-task
- [APISTORE-296 https://wso2.org/jira/browse/APISTORE-296] -
Refactor and Cleanup the API Statistics Client Component
- [APISTORE-297 https://wso2.org/jira/browse/APISTORE-297] - Add
Gadgets for Monitoring API Subscription Counts
- [APISTORE-298 https://wso2.org/jira/browse/APISTORE-298] -
Configure BAM Analyzers to Retain API Context Information in the Result
Sets
- [APISTORE-299 https://wso2.org/jira/browse/APISTORE-299] - API
Last Access Time Gadget Does Not Show API Names
- [APISTORE-300 https://wso2.org/jira/browse/APISTORE-300] -
Users/Keys Page in API Provider Does Not List All API Subscribers
- [APISTORE-301 https://wso2.org/jira/browse/APISTORE-301] - The
User Count Displayed in API Provider for Each API is Wrong - Multiple
Subscriptions from the Same User are Counted as Multiple Users
- [APISTORE-302 https://wso2.org/jira/browse/APISTORE-302] -
Gadgets that Display Usage by Subscribers Should Display a Limited View
-WSO2 API Manager Team-
--
Hiranya Jayathilaka
Senior Technical Lead;
WSO2
Re: [Dev] ESB_HOME/lib/core/WEB-INF/classes Property files are not loading
So Synapse looks for the config files in appClassPath. How do we include a config file in appClassPath with the current model? On Tue, May 22, 2012 at 10:55 AM, Pradeep Fernando prad...@wso2.com wrote: Hi, Any properly written library allow their users to feed-in config files using, 1. jre classPath 2. appClassPath 3. reside within the same jar - similar to appclasspath 4. system property This is the standard search order of a config file. The whole point of OSGi module layer is to have independent classPaths. So basically, if we are going to support a common place for all the config files, we have to introduce a new classsLoader as the parent classLoader of bunldeClassLoader. Normally the parent being, boot or ext. I don't think it is technically possible (not sure 100%). Even if it is possible we should not do such hacks. thanks, --Pradeep -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [ANN] WSO2 API Manager 1.0.0-M4 Available for Download
WSO2 API Manager 1.0.0-M4 can be downloaded from http://people.wso2.com/~hiranya/wso2am-1.0.0-M4.zip This milestone release comes with the new and improved API provider and API store webapps, API sandboxing support and much more. Please refer the release note in the distribution for more information as well as information on known issues. *How to run samples?* * * Following steps explain how to get samples up and running: 1. Download extract wso2am-1.0.0-M4.zip 2. Go to 'samples' folder. 3. There are 3 samples, namely: - TwitterSearch - YahooPlaceFinder - YoutubeFeeds 4. README.txt inside each of the sample folder provides complete instructions on deploying testing sample scenarios. 5. To learn how to configure statistics monitoring, read WSO2AM-HOME/StatClient/README.txt You need to have Apache Ant 1.8 or higher to run the samples. *New Features, Bug Fixes and Improvements* Bug - [APISTORE-205 https://wso2.org/jira/browse/APISTORE-205] - Please log CarbonTopLevel messages in DEBUG level instead of INFO - [APISTORE-219 https://wso2.org/jira/browse/APISTORE-219] - Error When Generating an API Key - [APISTORE-227 https://wso2.org/jira/browse/APISTORE-227] - Same Key got generate for two subscriptions - [APISTORE-237 https://wso2.org/jira/browse/APISTORE-237] - NetworkError: 404 Not Found - http://localhost:9763/apistore/js/layout-service-detail.js; - when loading API listing page in Store - [APISTORE-261 https://wso2.org/jira/browse/APISTORE-261] - If you're not logged into the Carbon admin console, trying to access Twitter sample API gives authentication error - [APISTORE-277 https://wso2.org/jira/browse/APISTORE-277] - URL Exact Matches Does Not Work with Query Parameters - [APISTORE-278 https://wso2.org/jira/browse/APISTORE-278] - Login/Logout Link Works Only on the Homepage - [APISTORE-279 https://wso2.org/jira/browse/APISTORE-279] - The Recently Added and More from Same Provider Sections List Older Versions of the APIs Improvement - [APISTORE-180 https://wso2.org/jira/browse/APISTORE-180] - Provide a mouse over tip as to what APIs and Applications mean on apistore - [APISTORE-185 https://wso2.org/jira/browse/APISTORE-185] - Remove source view from API manager management console - [APISTORE-243 https://wso2.org/jira/browse/APISTORE-243] - The Overview Tab Should Display the API URL - [APISTORE-254 https://wso2.org/jira/browse/APISTORE-254] - If BAM Server is not configured, do not attempt to publish statistics - [APISTORE-260 https://wso2.org/jira/browse/APISTORE-260] - [Code Review] Improvements for Governance implementation in AM. - [APISTORE-262 https://wso2.org/jira/browse/APISTORE-262] - Remove tag cloud top rating links from application listing page - [APISTORE-263 https://wso2.org/jira/browse/APISTORE-263] - Refactor API Store Provider portal with more structured UI development patterns - [APISTORE-264 https://wso2.org/jira/browse/APISTORE-264] - Make the API Gateway Location Configurable - [APISTORE-285 https://wso2.org/jira/browse/APISTORE-285] - Make it Possible to Update/Edit Applications - [APISTORE-286 https://wso2.org/jira/browse/APISTORE-286] - Sort the Entries Listed in My Subscriptions Page New Feature - [APISTORE-27 https://wso2.org/jira/browse/APISTORE-27] - pre-defined/pre-populated approval group - [APISTORE-259 https://wso2.org/jira/browse/APISTORE-259] - Make it Possible to Disable the BAM Usage Handler from the amConfig.xml - [APISTORE-266 https://wso2.org/jira/browse/APISTORE-266] - Should have the provision to enter Sanbox URL when publishing an API - [APISTORE-267 https://wso2.org/jira/browse/APISTORE-267] - Need to have a default application created by the system. - [APISTORE-268 https://wso2.org/jira/browse/APISTORE-268] - Provide application creation link alongside the drop down in subscription Task - [APISTORE-167 https://wso2.org/jira/browse/APISTORE-167] - Fix LICENSE file - [APISTORE-265 https://wso2.org/jira/browse/APISTORE-265] - API key should not be displayed alongside application (My Subscription) by default - [APISTORE-271 https://wso2.org/jira/browse/APISTORE-271] - Do not allow subscriptions to older versions - [APISTORE-273 https://wso2.org/jira/browse/APISTORE-273] - Rename permission labels to actions Thanks, -WSO2 API Manager Team- -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Ship svn-based deployment synchronizer with products by default?
+1 Thanks, Hiranya On Mon, May 14, 2012 at 5:39 PM, Afkham Azeez az...@wso2.com wrote: +1. Please go ahead. On Mon, May 14, 2012 at 4:06 PM, Kasun Gajasinghe kas...@wso2.com wrote: Hi, Currently the svn-based deployment synchronizer feature (org.wso2.carbon.deployment.synchronizer.feature) is not installed by default for any product except ESB. Isuru and I had a quick discussion, and we think that it's better to include this into the deployment synchronizer feature zip rather than maintaining it separately (platform/features/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.feature/). This is needed for all the products which has depsync feature. Is there any objections for this? If not, I'll proceed with this. Thanks, --KasunG -- *Kasun Gajasinghe* Software Engineer; Development Technologies Team, WSO2 Inc.; http://wso2.com , *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe* * *blog: **http://blog.kasunbg.org* http://blog.kasunbg.org* twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg* * -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] SVNKit isn't get picked by Deployment Synchronizer
I believe this is a classic package conflict issue for which we don't have a solution yet in the platform. We run into the same issue when deploying other third party bundles, and up until now our solution has been to merge the jars using some tool (generally a Maven script). Thanks, Hiranya On Mon, May 14, 2012 at 2:38 PM, Kasun Gajasinghe kas...@wso2.com wrote: Hi, The recommended subversion implementation for svn-based deployment synchronizer is the svnkit. If svnkit is not available, the svn adapter svnclient uses the default mechanism which contain lot of issues. But the provided solution doesn't work. As seen in [1], svnkit should be picked up by svnclient if the said jars are copied to the relevant locations. But as said in a later comment in this issue, it doesn't work. *Seems there are issues when making a orbit bundle from plain jars. *Though the provided solution works, it's kind of a hack. Is there a proper solution for this? [1] https://wso2.org/jira/browse/ESBJAVA-950?focusedCommentId=51602page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_51602 Thanks, --KasunG -- *Kasun Gajasinghe* Software Engineer; Development Technologies Team, WSO2 Inc.; http://wso2.com , *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe* * *blog: **http://blog.kasunbg.org* http://blog.kasunbg.org* twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg* * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configuration sync issue in an ESB cluster for proxy services
On Thu, May 10, 2012 at 11:33 AM, Isuru Suriarachchi is...@wso2.com wrote: On Thu, May 10, 2012 at 11:29 AM, Hiranya Jayathilaka hira...@wso2.comwrote: Do we sync meta files across the cluster? Yes we do.. That is because for other service types, there's no way of replicating the configurations without syncing meta files. Is not synchronizing proxy service meta files an option here? In a SVN setup that should be pretty easy. But on a registry based setup we need to think it through. Thanks, Hiranya Thanks, ~Isuru Thanks, Hiranya On Wed, May 9, 2012 at 12:49 PM, Isuru Suriarachchi is...@wso2.comwrote: Hi Hiranya, Charitha found this issue [1] which is related to syncing proxy service configurations. Here's the root cause for this.. * When security is applied for the proxy service in the RW node, it updates the proxy.xml file and also the meta file * Deployment Synchronizer syncs the proxy.xml to RO node * RO node hot-updates the proxy.xml and in the process it touches the meta file * When DS tries to sync the meta file, a conflict occurs because node2 has already touched it This doesn't happen for AAR services because the original .aar file never get changed when configurations are changed through the UI. So only the meta file will be updated and synced. We have to come up with a proper solution for this. Thanks, ~Isuru [1] https://wso2.org/jira/browse/CARBON-13070 -- Isuru Suriarachchi Technical Lead WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com -- Isuru Suriarachchi Technical Lead WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Some API Changes to the API Manager
Hi Ajith, On Mon, May 7, 2012 at 11:53 PM, Ajith Vitharana aji...@wso2.com wrote: On Mon, May 7, 2012 at 11:21 PM, Hiranya Jayathilaka hira...@wso2.comwrote: Sumedha and the API Manager team, In order to improve the internal design I'd like to propose following API changes to the API manager implementation: 1. Add following 2 new methods to the APIManager interface (Some variants of these method are already available in the APIManagerImpl class, but they are not part of the API. I think we should make the following generalized methods part of the core API and use them from the host objects as required) InputStream getIcon(APIIdentifier id) void addIcon(APIIdentifier id, InputStream in, String contentType) +1 .After that we can remove the addApiThumb() method from APIManagerImpl. 2. Move the getSubscriberAPIs method from APIConsumer to APIManager (This method is already used by the API provider host object. Clearly it's required by API consumers as well as API providers). +1. The functions which are commonly used should be inside the APIManager. 3. Introduce a new username argument (String) to the addComment and rateAPI methods. We need to perform these operations using the governance user registry of the corresponding users. Otherwise the system will not properly keep track of the comment authors. To make the core API more generic I think we should introduce the username argument to the above methods. Shall we pass UserRegistry instead of user name? Currently the API manager interfaces do not expose any registry specific things. It's better to keep it like that. Thanks, Hiranya If you don't see any issues with these changes, I'll get started with refactoring. In order to handle authorization what I thought was to implement a new wrapper for the existing impl classes. The wrapper will imply extend the classes providing the necessary authorization logic (permission checking) where necessary. I've spawned a new thread regarding this on the mailing list. If we don't get any better ideas we can implement that. Thanks -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794 -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Checking Permissions in a Java API
Hi, I want to check whether a given user has a particular permission. Is there some API in Carbon to do this? Our requirement is that we have a Java API and we want to make sure that some of the methods in this API can only be invoked by users with particular permissions. What is the best way to implement something like this? Thanks, Hirana -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Adding proxy services using the UI
Hi, On Mon, May 7, 2012 at 6:08 PM, Afkham Azeez az...@wso2.com wrote: On Mon, May 7, 2012 at 6:03 PM, Afkham Azeez az...@wso2.com wrote: On Mon, May 7, 2012 at 5:11 PM, Hiranya Jayathilaka hira...@wso2.comwrote: On Mon, May 7, 2012 at 3:09 PM, Afkham Azeez az...@wso2.com wrote: Folks., Any feedback on this? Does this make sense? I don't think so. We have a very clear separation between named sequences/endpoints and anonymous sequences/endpoints. Anonymous objects are local to a particular proxy service or an API and they are not visible to other services. Sort of like a private method. Named objects on the other hand are visible to everybody, can be shared/reused extensively and do show up in the Synape global namespace. Both have specific, well-defined use cases and I don't see a strong use case for having named sequences inside a proxy or an API. What about the service chaining scenario? We unnecessarily have to define sequences in the global space even though those will be needed only by one particular proxy service. Take a look at the example at http://blog.afkham.org/2012/05/wso2-esb-service-chaining.html. I had to define personInfoSeq creditSeq at the global level even though I needed them only within the proxy service. Is there a way to achieve the same thing while keeping everything local (without following the old state property based case handling)? In other words, is there a way to set the receive attribute of the send mediator to an anonymous (local to proxy service) sequence? Send mediator can only lookup named sequences. And in the current Synapse registry implementation, all named objects are kept in a global scope. So what you're suggesting is to implement a new service/API scope for Synapse language. This should be possible, but I'm not sure how much effort it's going to take. However the question is, how badly do we want to do this? What are the other use cases we might have? Thanks, Hiranya -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Registry based Deployment Synchronizer does not work [was Fwd: https://wso2.org/jira/browse/CARBON-12801]
On Mon, May 7, 2012 at 10:06 PM, Charitha Kankanamge chari...@wso2.comwrote: Why should we enable axis2 clustering in order to get registry based deployment synchronizer working? This might be due to the improvements Azeez implemented recently. Basically we use the clustering group comm mechanism to pass events among the nodes and these events fire the synchronizer activities. Thanks, Hiranya On Monday, May 7, 2012, Subash Chaturanga wrote: On Mon, May 7, 2012 at 2:19 PM, Charitha Kankanamge chari...@wso2.comwrote: Has anyone got registry based deployment working with C4 alpha packs? I tried with setting up a 2 node ESB cluster with registry based synchronizer but it does not seem to work. The artifacts are synchronized across cluster nodes only if the nodes are restarted. Hi Charitha, I was able to get this working on C4 alpha packs. I also setup a two node master slave ESB cluster with a shared registry which runs on mysql (*without using the admin console). But with the given instructions to reproduce this in the CARBON-13044https://wso2.org/jira/browse/CARBON-13044, I also could not get this working. Because the clustering should be enabled in the axis2 level. With that I got deployment sync working. (The UI seems to be broken and gives me exceptions (and thus I did it from xml configs), but still it shows that the deployment sync created). Did you enabled clustering in axis2.xml ? [1]https://wso2.org/jira/browse/CARBON-13044 Please have a look at this and resolve if there is a bug. This is very important for us to proceed with production test setups. /Charitha -- Forwarded message -- From: *Kasun Gajasinghe* kas...@wso2.com Date: Wed, Apr 25, 2012 at 8:34 PM Subject: Re: https://wso2.org/jira/browse/CARBON-12801 To: Hiranya Jayathilaka hira...@wso2.com Cc: Charitha Kankanamge chari...@wso2.com, Dimuthu Leelarathne dimut...@wso2.com, Afkham Azeez az...@wso2.com, support-dev-group support-dev-gr...@wso2.com On Wed, Apr 25, 2012 at 12:23 AM, Hiranya Jayathilaka hira...@wso2.comwrote: On Tue, Apr 24, 2012 at 6:13 PM, Kasun Gajasinghe kas...@wso2.comwrote: We should find a way to resolve the conflicts. Current implementation doesn't support conflict resolving. As I found out, for svn-based depsync, the svn conflict resolver is not implemented in Svnclient. It is implemented. Let me clarify what I meant to say. Yes, 'resolved' subcommand is implemented. Though it's deprecated in favor of 'resolve' subcommand, the functionality is there. What's not there is a way to resolve conflicts *the moment it happens in commandline adapter*. There's a callback functionality implemented (DefaultConflictResolver), but this callback isn't used because the underlying methods are marked as TODO. I think this should be implemented, or bring in a new underlying dependency for Svnclient like svnkit instead of current CommandLine adapter that already has the needed implementation. We can't take a dependency on SVN Kit and redistribute it due to licensing matters. But SVN client adapter allows you to use SVN Kit as a drop-in. That's what we do in SLive. Yes, the license is a problem. Seems they are using a custom license called TMate license. In this case, the ideal path is to implement the needed implementation for commandline adapter. The code seems to be easy to understand as well. I believe there must be a way to automatically resolve conflicts because when that happens, that node can no longer commit. And, when there's xml files, the structure is broken because svn adds content like the following to conflicted xml files. .mine --- --- Thanks, --KasunG Thanks, Hiranya ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Subash Chaturanga Software Engineer WSO2 Inc. http://wso2.com email - sub...@wso2.com phone - 077 2225922 -- Charitha Kankanamge cell: +94 718 359 265 blog: http://charithaka.blogspot.com http://wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Some API Changes to the API Manager
Sumedha and the API Manager team, In order to improve the internal design I'd like to propose following API changes to the API manager implementation: 1. Add following 2 new methods to the APIManager interface (Some variants of these method are already available in the APIManagerImpl class, but they are not part of the API. I think we should make the following generalized methods part of the core API and use them from the host objects as required) InputStream getIcon(APIIdentifier id) void addIcon(APIIdentifier id, InputStream in, String contentType) 2. Move the getSubscriberAPIs method from APIConsumer to APIManager (This method is already used by the API provider host object. Clearly it's required by API consumers as well as API providers) 3. Introduce a new username argument (String) to the addComment and rateAPI methods. We need to perform these operations using the governance user registry of the corresponding users. Otherwise the system will not properly keep track of the comment authors. To make the core API more generic I think we should introduce the username argument to the above methods. If you don't see any issues with these changes, I'll get started with refactoring. In order to handle authorization what I thought was to implement a new wrapper for the existing impl classes. The wrapper will imply extend the classes providing the necessary authorization logic (permission checking) where necessary. I've spawned a new thread regarding this on the mailing list. If we don't get any better ideas we can implement that. Thanks -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fwd: [ANNOUNCEMENT] HttpComponents HttpCore 4.2 GA Released
It's a new API. Upgrading won't be straight forward. Thanks, Hiranya On Mon, May 7, 2012 at 8:58 AM, Rajika Kumarasiri raj...@wso2.com wrote: FYI. hc version can be upgraded in ESB. Rajika -- Forwarded message -- From: Oleg Kalnichevski ol...@apache.org Date: Sat, May 5, 2012 at 11:02 PM Subject: [ANNOUNCEMENT] HttpComponents HttpCore 4.2 GA Released To: annou...@apache.org, priv...@hc.apache.org, d...@hc.apache.org, httpclient-us...@hc.apache.org The Apache HttpComponents project is pleased to announce the first stable (GA) release of HttpComponents HttpCore 4.2. The most notable features included in this release are connection pool components for blocking and non-blocking HTTP connections and new asynchronous client and server side protocol handlers. New protocol handling API used in conjunction with connection pooling components is expected to make development of asynchronous HTTP client agents and HTTP proxies easier and less error prone. Connection pool components are based on mature code migrated from HttpClient and HttpAsyncClient modules but have a slightly different API that makes a better use of Java standard concurrent primitives. Sample application shipped with the release include an example of an HTTP file server capable of direct channel (zero copy) data transfer and an example of a non-blocking, fully streaming reverse proxy. Download - http://hc.apache.org/downloads.cgi Release notes - http://www.apache.org/dist/httpcomponents/httpcore/RELEASE_NOTES.txt HttpComponents site - http://hc.apache.org/ About HttpComponents Core - HttpCore is a set of low level HTTP transport components that can be used to build custom client and server side HTTP services with a minimal footprint. HttpCore supports two I/O models: a blocking I/O model based on the classic Java I/O and a non-blocking, event driven I/O model based on Java NIO. The blocking I/O model may be more appropriate for data intensive, low latency scenarios, whereas the non-blocking model may be more appropriate for high latency scenarios where raw data throughput is less important than the ability to handle thousands of simultaneous HTTP connections in a resource efficient manner. - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Invitation: [Integration TG] Weekly Code Review - Governance Implemen... @ Wed Apr 25 2:30pm - 3:30pm (dev@wso2.org)
JIRA issue: https://wso2.org/jira/browse/APISTORE-260 On Fri, Apr 27, 2012 at 3:20 PM, Denis Weerasiri de...@wso2.com wrote: Hi all, Here are the meeting notes of the session. 1. Seperating out the API manager based on its publisher / subscriber functionalities 2. Creating an artifactMnager - Check whether it's required to have a checked exception on can have a runtimeexception 3. write a util method to generate the provider path etc. (In APIUtil class) 4. UpdateAPI method - avoid from null check 5. When (Adding/Updating) a (Document/API) provide a helper method to clients, as underneath, they do the same task 6. Refactor the method createNewAPIVersion (as it got similar functionality with AddAPI method) 7. when creating the API/Document, there are some properties get set inside the AddAPI and AddDocument menthods. We can move those property settings to a util method. 8. In addRXTConfig method - move resourceExist() check further up 9. In addRXTConfig method - move for loop inside to the try block 10. Use Apache commons IO to handle file name, extensions 11. Get rid of getRegistry(), see APIManagerImpl.getRegistryService() 12. Use a singleton to maintain OSGi service dependencies 13. Use a file filter to get rid of rxt type extensions, addRxtConfigs() 14. avoid getThumbAsString() method 15. move Pattern.compile like expensive operations out of the for loop in SearchAPI() 16. get rid of keepAliveRegistry() as ws-api is no longer in use On Wed, Apr 25, 2012 at 10:24 AM, Hiranya Jayathilaka hira...@wso2.comwrote: more details »https://www.google.com/calendar/event?action=VIEWeid=Nm5uaXJhcGNwZHQyNjRqN3AwbTUyaXI0MWcgZGV2QHdzbzIub3Jntok=MTYjaGlyYW55YUB3c28yLmNvbTIzNmQyNGNhNTg0NjZiYzQ5OTdkZWExNjFjZTY4Y2ZhMDI1ZjY4MzEctz=Asia/Colombohl=en [Integration TG] Weekly Code Review - Governance Implementation in API Manager We are pushing the code review which was scheduled to be held on in the morning to afternoon. Please be there at 2.30. *When* Wed Apr 25 2:30pm – 3:30pm Colombo *Where* LK #58 5th Floor - Meeting room (maphttp://maps.google.lk/maps?q=LK+%2358+5th+Floor+-+Meeting+roomhl=en ) *Calendar* dev@wso2.org *Who* • hira...@wso2.com - organizer • Ajith Vitharana • dev@wso2.org • Sumedha Rubasinghe Going? ***Yeshttps://www.google.com/calendar/event?action=RESPONDeid=Nm5uaXJhcGNwZHQyNjRqN3AwbTUyaXI0MWcgZGV2QHdzbzIub3Jnrst=1tok=MTYjaGlyYW55YUB3c28yLmNvbTIzNmQyNGNhNTg0NjZiYzQ5OTdkZWExNjFjZTY4Y2ZhMDI1ZjY4MzEctz=Asia/Colombohl=en- Maybehttps://www.google.com/calendar/event?action=RESPONDeid=Nm5uaXJhcGNwZHQyNjRqN3AwbTUyaXI0MWcgZGV2QHdzbzIub3Jnrst=3tok=MTYjaGlyYW55YUB3c28yLmNvbTIzNmQyNGNhNTg0NjZiYzQ5OTdkZWExNjFjZTY4Y2ZhMDI1ZjY4MzEctz=Asia/Colombohl=en- Nohttps://www.google.com/calendar/event?action=RESPONDeid=Nm5uaXJhcGNwZHQyNjRqN3AwbTUyaXI0MWcgZGV2QHdzbzIub3Jnrst=2tok=MTYjaGlyYW55YUB3c28yLmNvbTIzNmQyNGNhNTg0NjZiYzQ5OTdkZWExNjFjZTY4Y2ZhMDI1ZjY4MzEctz=Asia/Colombohl=en ***more options »https://www.google.com/calendar/event?action=VIEWeid=Nm5uaXJhcGNwZHQyNjRqN3AwbTUyaXI0MWcgZGV2QHdzbzIub3Jntok=MTYjaGlyYW55YUB3c28yLmNvbTIzNmQyNGNhNTg0NjZiYzQ5OTdkZWExNjFjZTY4Y2ZhMDI1ZjY4MzEctz=Asia/Colombohl=en Invitation from Google Calendar https://www.google.com/calendar/ You are receiving this courtesy email at the account dev@wso2.orgbecause you are an attendee of this event. To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks, Denis -- *Denis Weerasiri* Senior Software Engineer Integration Technologies Team, WSO2 Inc.; http://wso2.com, *email: denis http://goog_277208233/** [AT] wso2.com http://wso2.com/* *phone: +94117639629 * *site: **https://sites.google.com/site/ddweerasiri/*https://sites.google.com/site/ddweerasiri/ *blog: **http://ddweerasiri.blogspot.com*http://ddweerasiri.blogspot.com/ * twitter: **http://twitter.com/ddweerasiri*http://twitter.com/ddweerasiri * linked-in: **http://lk.linkedin.com/in/ddweerasiri*http://lk.linkedin.com/in/ddweerasiri -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Invitation: [Integration TG] Weekly Code Review - Governance Implemen... @ Wed Apr 25 2:30pm - 3:30pm (dev@wso2.org)
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20120425T09Z DTEND:20120425T10Z DTSTAMP:20120425T045407Z ORGANIZER;CN=hira...@wso2.com:mailto:hira...@wso2.com UID:6nnirapcpdt264j7p0m52ir...@google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Ajith Vitharana;X-NUM-GUESTS=0:mailto:aji...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=Hiranya Jayathilaka;X-NUM-GUESTS=0:mailto:hira...@wso2.com ATTENDEE;CUTYPE=RESOURCE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TR UE;CN=LK #58 5th Floor - Meeting room;X-NUM-GUESTS=0:mailto:wso2.com_323831 3439343838343...@resource.calendar.google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=dev@wso2.org;X-NUM-GUESTS=0:mailto:dev@wso2.org ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Sumedha Rubasinghe;X-NUM-GUESTS=0:mailto:sume...@wso2.com CREATED:20120425T045407Z DESCRIPTION:We are pushing the code review which was scheduled to be held o n in the morning to afternoon. Please be there at 2.30.\nView your event at http://www.google.com/calendar/event?action=VIEWeid=Nm5uaXJhcGNwZHQyNjRqN 3AwbTUyaXI0MWcgZGV2QHdzbzIub3Jntok=MTYjaGlyYW55YUB3c28yLmNvbTIzNmQyNGNhNTg 0NjZiYzQ5OTdkZWExNjFjZTY4Y2ZhMDI1ZjY4MzEctz=Asia/Colombohl=en. LAST-MODIFIED:20120425T045407Z LOCATION:LK #58 5th Floor - Meeting room SEQUENCE:0 STATUS:CONFIRMED SUMMARY:[Integration TG] Weekly Code Review - Governance Implementation in API Manager TRANSP:OPAQUE END:VEVENT END:VCALENDAR invite.ics Description: application/ics ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Lots of WS Registry Client Exceptions
Sumedha and I have been doing minor improvements to the code at various levels. Over the weekend I fixed some suspicious code in the API templating logic (which may have been inserting invalid characters to the XML document). Sumedha also did some crucial fixes at DAO level. Things seem to be quite stable after that. Haven't seen any of these errors so far in a pack built today morning. Will update the thread if the situation changes. Thanks everyone for the inputs. Thanks, Hiranya On Sun, Apr 22, 2012 at 11:47 AM, Eranda Sooriyabandara era...@wso2.comwrote: Hi Hiranya, On Sat, Apr 21, 2012 at 12:06 PM, Hiranya Jayathilaka hira...@wso2.comwrote: On Fri, Apr 20, 2012 at 6:04 PM, Sumedha Rubasinghe sume...@wso2.comwrote: Hiranya, Looks like you experiencing subject: Facing an Intermittent issue when getting the api list from the registry. There is a corresponding JIRA item as well (now Resolved) after Eranda added a back ground thread to keep the Registry connection alive. I'm still getting it every now and then. My build was taken sometime late this week so it should contain the fix. Most of the errors I'm seeing are not really related to timeouts or invalid sessions. But due to parser exceptions. I'll debug and see if anything can be revealed. I'll take a look into this. thanks Eranda ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API Mananger] Removing the REST URL Postfix
This has been implemented. Samples like the Twitter sample needs to be updated accordingly. In case of Twitter sample the path section in the endpoint (/search.atom) needs to be removed and appended to the Curl commands. Thanks, Hiranya On Fri, Apr 20, 2012 at 5:04 PM, Sumedha Rubasinghe sume...@wso2.comwrote: +1 On Fri, Apr 20, 2012 at 12:00 PM, Hiranya Jayathilaka hira...@wso2.comwrote: Hi Folks, The APIs created by the API manager has the following mediator setting to remove the URL postfix section: property name=REST_URL_POSTFIX scope=axis2 action=remove/ In the last review we had we decided to get rid of it. Shall I go ahead and make the necessary changes? Thanks -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com -- /sumedha +94 773017743 -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [API Manager] Rename amConfig.xml
Shall we rename amConfig.xml to api-manager.xml to be consistent with our config file naming conventions? -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Does DepSync commit happens even if AutoCommit is set to false?
It looks like this task impl does not take the autoCommit flag into
account. This task is generally used in SLive where all the nodes are in
autoCommit mode. So not a problem in that environment. Azeez should be able
to explain more.
Thanks,
Hiranya
On Sun, Apr 22, 2012 at 10:39 PM, Kasun Gajasinghe kas...@wso2.com wrote:
Hi folks,
$subject. I've set AutoCommit to false in slave nodes, and AutoCheckout
true in master node. While I was debugging the code, it turned out that
even the slave node executes commit command. Yes, the sync task respects
the AutoCommit tag, but I'm seeing following code segment
in CarbonDeploymentSchedulerTask in org.wso2.carbon.core package, which
does a *commit **to determine whether the repo is changed or not.*
I'm probably seeing a bug, but I'm not sure why this hasn't been detected
all these months. But I'm seeing some issues because of this with the new
metadata files. Svnclient can determine the status can without doing a
commit.
Is there a reason for this?
private boolean doDeploymentSynchronization() {
if (log.isDebugEnabled()) {
log.debug(Running deployment synchronizer...);
}
boolean status = false;
BundleContext bundleContext =
CarbonCoreDataHolder.getInstance().getBundleContext();
ServiceReference reference =
bundleContext.getServiceReference(DeploymentSynchronizer.class.getName());
if (reference != null) {
ServiceTracker serviceTracker = new
ServiceTracker(bundleContext,
DeploymentSynchronizer.class.getName(),
null);
try {
serviceTracker.open();
for (Object obj : serviceTracker.getServices()) {
DeploymentSynchronizer depsync =
(DeploymentSynchronizer) obj;
if(!isInitialUpdateDone || isRepoUpdateFailed){
depsync.update(tenantId);
isInitialUpdateDone = true;
isRepoUpdateFailed = false;
}
*status = depsync.commit(tenantId);*
}
} catch (Exception e) {
log.error(Deployment synchronization for tenant +
tenantId + failed, e);
} finally {
serviceTracker.close();
}
}
return status;
}
Thanks,
--KasunG
--
*Kasun Gajasinghe*
Software Engineer; WSO2 Inc.; http://wso2.com
,
*email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
*linked-in: *http://lk.linkedin.com/in/gajasinghe*
*
*blog: **http://blog.kasunbg.org* http://blog.kasunbg.org
*
twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.; http://wso2.org
E-mail: hira...@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Deployment synchronizer totally broken in trunk?
On Fri, Apr 20, 2012 at 7:34 PM, Afkham Azeez az...@wso2.com wrote: Some problems. 1. org.wso2.carbon.deployment.synchronizer.subversion bundle is missing 2. svnclient bundle is missing 3. If you configure once using the UI, all your subsequent changes to carbon.xml will be ignored Right. You should use one way of configuring this feature. We don't sync configurations from file system to the registry due to the 2-way sync problem.Settings in the registry have priority. 4. UI configurations are stored in local repository. So, if your cluster has several nodes, you will have to make changes to all nodes one by one.\ That's right. This is because within a single cluster some nodes will be in auto checkout mode and some nodes (usually one) will be in auto commit mode. We used to store these settings in config registry about a year ago, but with that we cannot use this component to actually configure a useful clustered setup. That way either everyone will be in auto commit mode or everyone will be in auto checkout mode. So we moved the settings to the local repo. It's a per node setting. Thanks, Hiranya On Fri, Apr 20, 2012 at 6:53 PM, Afkham Azeez az...@wso2.com wrote: Folks, Has anybody tested this with the new packs? -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Deployment synchronizer totally broken in trunk?
On Sat, Apr 21, 2012 at 12:42 PM, Hiranya Jayathilaka hira...@wso2.comwrote: On Sat, Apr 21, 2012 at 12:22 PM, Afkham Azeez az...@wso2.com wrote: On Sat, Apr 21, 2012 at 12:13 PM, Hiranya Jayathilaka hira...@wso2.comwrote: On Fri, Apr 20, 2012 at 7:34 PM, Afkham Azeez az...@wso2.com wrote: Some problems. 1. org.wso2.carbon.deployment.synchronizer.subversion bundle is missing 2. svnclient bundle is missing 3. If you configure once using the UI, all your subsequent changes to carbon.xml will be ignored Right. You should use one way of configuring this feature. We don't sync configurations from file system to the registry due to the 2-way sync problem.Settings in the registry have priority. 4. UI configurations are stored in local repository. So, if your cluster has several nodes, you will have to make changes to all nodes one by one.\ That's right. This is because within a single cluster some nodes will be in auto checkout mode and some nodes (usually one) will be in auto commit mode. We used to store these settings in config registry about a year ago, but with that we cannot use this component to actually configure a useful clustered setup. That way either everyone will be in auto commit mode or everyone will be in auto checkout mode. So we moved the settings to the local repo. It's a per node setting. Which make this configuration useless because, in a proper clustered deployment, we will not be able to control to which node the admin logs in. In addition, in the future, the plan is to have a couple of management nodes, which will have the management console, and then a set of worker nodes. The management nodes are used for configuring the worker cluster. So, if this configuration only gets saved into the local registry of the management node, things won't work as expected. Your argument is valid in case of a cloud deployment. But for a small in-house deployment that doesn't make any sense. In an in-house clustered deployment we designate one node as the master read-write node. That's where admins login and make all the config changes. The synchronizer replicates them to other slave (read-only) nodes. This is how our enterprise users use this feature. We have documentation explaining the process too - http://wso2.org/project/esb/java/4.0.3/docs/deployment_guide.html In case of a Stratos, we don't ship the UI component. It's not made to be used in a scenario like that. And in the future if we plan to change our clustering model and how registry sharing is used, then this component should be accordingly updated. Right now it's modeled after our current registry sharing and master-slave model of clustering. Thanks, Hiranya Thanks, Hiranya Thanks, Hiranya On Fri, Apr 20, 2012 at 6:53 PM, Afkham Azeez az...@wso2.com wrote: Folks, Has anybody tested this with the new packs? -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
Re: [Dev] Deployment synchronizer totally broken in trunk?
On Sat, Apr 21, 2012 at 12:48 PM, Afkham Azeez az...@wso2.com wrote: On Sat, Apr 21, 2012 at 12:42 PM, Hiranya Jayathilaka hira...@wso2.comwrote: On Sat, Apr 21, 2012 at 12:22 PM, Afkham Azeez az...@wso2.com wrote: On Sat, Apr 21, 2012 at 12:13 PM, Hiranya Jayathilaka hira...@wso2.comwrote: On Fri, Apr 20, 2012 at 7:34 PM, Afkham Azeez az...@wso2.com wrote: Some problems. 1. org.wso2.carbon.deployment.synchronizer.subversion bundle is missing 2. svnclient bundle is missing 3. If you configure once using the UI, all your subsequent changes to carbon.xml will be ignored Right. You should use one way of configuring this feature. We don't sync configurations from file system to the registry due to the 2-way sync problem.Settings in the registry have priority. 4. UI configurations are stored in local repository. So, if your cluster has several nodes, you will have to make changes to all nodes one by one.\ That's right. This is because within a single cluster some nodes will be in auto checkout mode and some nodes (usually one) will be in auto commit mode. We used to store these settings in config registry about a year ago, but with that we cannot use this component to actually configure a useful clustered setup. That way either everyone will be in auto commit mode or everyone will be in auto checkout mode. So we moved the settings to the local repo. It's a per node setting. Which make this configuration useless because, in a proper clustered deployment, we will not be able to control to which node the admin logs in. In addition, in the future, the plan is to have a couple of management nodes, which will have the management console, and then a set of worker nodes. The management nodes are used for configuring the worker cluster. So, if this configuration only gets saved into the local registry of the management node, things won't work as expected. Your argument is valid in case of a cloud deployment. But for a small in-house deployment that doesn't make any sense. In an in-house clustered deployment we designate one node as the master read-write node. We are not planning to have one solution for Stratos deployments while making different recommendations to the customer. In the future, we plan to promote having management nodes worker nodes separated, just like we plan to do in StratosLive. Also when a set of nodes is backed by an LB, and all accesses are through that LB, how do you control to which node the request is forwarded to, when you are configuring the synchronizer? On the read-write node the synchronizer has to be configured to commit, while in the read-only node it has to be configured to update only. How do you do that when the entire cluster is fronted by an LB? Azeez, our current clustering model does not say anything about fronting all the UIs from a single LB. We simply ask to setup one node as the master (read-write) and everything else as slaves (read-only). All configuration changes should be performed through the read-write node only. This has been our documented clustering model for enterprise users since Carbon 1.5 days (Charitha, correct me if I'm wrong). The deployment sync UI is modeled after that. That makes it easier for someone who's setting up a cluster according to our guidelines, to setup cluster-wide automatic replication of artifacts. Now if we change our clustering model to front all the admin consoles from a single LB then obviously the current UI component won't work. In that scenario I don't think we can use our existing documented master-slave model anymore. So the UI needs to be redesigned for that case. Thanks, Hiranya That's where admins login and make all the config changes. The synchronizer replicates them to other slave (read-only) nodes. This is how our enterprise users use this feature. We have documentation explaining the process too - http://wso2.org/project/esb/java/4.0.3/docs/deployment_guide.html In case of a Stratos, we don't ship the UI component. It's not made to be used in a scenario like that. Thanks, Hiranya Thanks, Hiranya On Fri, Apr 20, 2012 at 6:53 PM, Afkham Azeez az...@wso2.com wrote: Folks, Has anybody tested this with the new packs? -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org
Re: [Dev] Deployment synchronizer totally broken in trunk?
Charitha has written a good blog post about Carbon clustering model and how the synchronizer UI is used in that context - http://charithaka.blogspot.com/2011/11/wso2-deployment-synchronizer-sharing.html This is the use case we have modeled the UI after. UI level LB and the possibility of admin requests getting dispatched any of the available nodes are not a part of that. Thanks, Hiranya On Sat, Apr 21, 2012 at 12:56 PM, Hiranya Jayathilaka hira...@wso2.comwrote: On Sat, Apr 21, 2012 at 12:48 PM, Afkham Azeez az...@wso2.com wrote: On Sat, Apr 21, 2012 at 12:42 PM, Hiranya Jayathilaka hira...@wso2.comwrote: On Sat, Apr 21, 2012 at 12:22 PM, Afkham Azeez az...@wso2.com wrote: On Sat, Apr 21, 2012 at 12:13 PM, Hiranya Jayathilaka hira...@wso2.com wrote: On Fri, Apr 20, 2012 at 7:34 PM, Afkham Azeez az...@wso2.com wrote: Some problems. 1. org.wso2.carbon.deployment.synchronizer.subversion bundle is missing 2. svnclient bundle is missing 3. If you configure once using the UI, all your subsequent changes to carbon.xml will be ignored Right. You should use one way of configuring this feature. We don't sync configurations from file system to the registry due to the 2-way sync problem.Settings in the registry have priority. 4. UI configurations are stored in local repository. So, if your cluster has several nodes, you will have to make changes to all nodes one by one.\ That's right. This is because within a single cluster some nodes will be in auto checkout mode and some nodes (usually one) will be in auto commit mode. We used to store these settings in config registry about a year ago, but with that we cannot use this component to actually configure a useful clustered setup. That way either everyone will be in auto commit mode or everyone will be in auto checkout mode. So we moved the settings to the local repo. It's a per node setting. Which make this configuration useless because, in a proper clustered deployment, we will not be able to control to which node the admin logs in. In addition, in the future, the plan is to have a couple of management nodes, which will have the management console, and then a set of worker nodes. The management nodes are used for configuring the worker cluster. So, if this configuration only gets saved into the local registry of the management node, things won't work as expected. Your argument is valid in case of a cloud deployment. But for a small in-house deployment that doesn't make any sense. In an in-house clustered deployment we designate one node as the master read-write node. We are not planning to have one solution for Stratos deployments while making different recommendations to the customer. In the future, we plan to promote having management nodes worker nodes separated, just like we plan to do in StratosLive. Also when a set of nodes is backed by an LB, and all accesses are through that LB, how do you control to which node the request is forwarded to, when you are configuring the synchronizer? On the read-write node the synchronizer has to be configured to commit, while in the read-only node it has to be configured to update only. How do you do that when the entire cluster is fronted by an LB? Azeez, our current clustering model does not say anything about fronting all the UIs from a single LB. We simply ask to setup one node as the master (read-write) and everything else as slaves (read-only). All configuration changes should be performed through the read-write node only. This has been our documented clustering model for enterprise users since Carbon 1.5 days (Charitha, correct me if I'm wrong). The deployment sync UI is modeled after that. That makes it easier for someone who's setting up a cluster according to our guidelines, to setup cluster-wide automatic replication of artifacts. Now if we change our clustering model to front all the admin consoles from a single LB then obviously the current UI component won't work. In that scenario I don't think we can use our existing documented master-slave model anymore. So the UI needs to be redesigned for that case. Thanks, Hiranya That's where admins login and make all the config changes. The synchronizer replicates them to other slave (read-only) nodes. This is how our enterprise users use this feature. We have documentation explaining the process too - http://wso2.org/project/esb/java/4.0.3/docs/deployment_guide.html In case of a Stratos, we don't ship the UI component. It's not made to be used in a scenario like that. Thanks, Hiranya Thanks, Hiranya On Fri, Apr 20, 2012 at 6:53 PM, Afkham Azeez az...@wso2.com wrote: Folks, Has anybody tested this with the new packs? -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
Re: [Dev] Deployment synchronizer totally broken in trunk?
And the article from Senaka which serves as the almanac of registry sharing :) - http://wso2.org/library/tutorials/2010/04/sharing-registry-space-across-multiple-product-instances Setting up a cluster of same products is discussed under strategy-B. Again it speaks of the master-slave model. No mention of LB for UIs. Thanks, Hiranya On Sat, Apr 21, 2012 at 1:01 PM, Hiranya Jayathilaka hira...@wso2.comwrote: Charitha has written a good blog post about Carbon clustering model and how the synchronizer UI is used in that context - http://charithaka.blogspot.com/2011/11/wso2-deployment-synchronizer-sharing.html This is the use case we have modeled the UI after. UI level LB and the possibility of admin requests getting dispatched any of the available nodes are not a part of that. Thanks, Hiranya On Sat, Apr 21, 2012 at 12:56 PM, Hiranya Jayathilaka hira...@wso2.comwrote: On Sat, Apr 21, 2012 at 12:48 PM, Afkham Azeez az...@wso2.com wrote: On Sat, Apr 21, 2012 at 12:42 PM, Hiranya Jayathilaka hira...@wso2.comwrote: On Sat, Apr 21, 2012 at 12:22 PM, Afkham Azeez az...@wso2.com wrote: On Sat, Apr 21, 2012 at 12:13 PM, Hiranya Jayathilaka hira...@wso2.com wrote: On Fri, Apr 20, 2012 at 7:34 PM, Afkham Azeez az...@wso2.com wrote: Some problems. 1. org.wso2.carbon.deployment.synchronizer.subversion bundle is missing 2. svnclient bundle is missing 3. If you configure once using the UI, all your subsequent changes to carbon.xml will be ignored Right. You should use one way of configuring this feature. We don't sync configurations from file system to the registry due to the 2-way sync problem.Settings in the registry have priority. 4. UI configurations are stored in local repository. So, if your cluster has several nodes, you will have to make changes to all nodes one by one.\ That's right. This is because within a single cluster some nodes will be in auto checkout mode and some nodes (usually one) will be in auto commit mode. We used to store these settings in config registry about a year ago, but with that we cannot use this component to actually configure a useful clustered setup. That way either everyone will be in auto commit mode or everyone will be in auto checkout mode. So we moved the settings to the local repo. It's a per node setting. Which make this configuration useless because, in a proper clustered deployment, we will not be able to control to which node the admin logs in. In addition, in the future, the plan is to have a couple of management nodes, which will have the management console, and then a set of worker nodes. The management nodes are used for configuring the worker cluster. So, if this configuration only gets saved into the local registry of the management node, things won't work as expected. Your argument is valid in case of a cloud deployment. But for a small in-house deployment that doesn't make any sense. In an in-house clustered deployment we designate one node as the master read-write node. We are not planning to have one solution for Stratos deployments while making different recommendations to the customer. In the future, we plan to promote having management nodes worker nodes separated, just like we plan to do in StratosLive. Also when a set of nodes is backed by an LB, and all accesses are through that LB, how do you control to which node the request is forwarded to, when you are configuring the synchronizer? On the read-write node the synchronizer has to be configured to commit, while in the read-only node it has to be configured to update only. How do you do that when the entire cluster is fronted by an LB? Azeez, our current clustering model does not say anything about fronting all the UIs from a single LB. We simply ask to setup one node as the master (read-write) and everything else as slaves (read-only). All configuration changes should be performed through the read-write node only. This has been our documented clustering model for enterprise users since Carbon 1.5 days (Charitha, correct me if I'm wrong). The deployment sync UI is modeled after that. That makes it easier for someone who's setting up a cluster according to our guidelines, to setup cluster-wide automatic replication of artifacts. Now if we change our clustering model to front all the admin consoles from a single LB then obviously the current UI component won't work. In that scenario I don't think we can use our existing documented master-slave model anymore. So the UI needs to be redesigned for that case. Thanks, Hiranya That's where admins login and make all the config changes. The synchronizer replicates them to other slave (read-only) nodes. This is how our enterprise users use this feature. We have documentation explaining the process too - http://wso2.org/project/esb/java/4.0.3/docs/deployment_guide.html In case of a Stratos, we don't ship the UI component. It's not made
Re: [Dev] Deployment synchronizer totally broken in trunk?
On Sat, Apr 21, 2012 at 1:18 PM, Afkham Azeez az...@wso2.com wrote: On Sat, Apr 21, 2012 at 12:13 PM, Hiranya Jayathilaka hira...@wso2.comwrote: On Fri, Apr 20, 2012 at 7:34 PM, Afkham Azeez az...@wso2.com wrote: Some problems. 1. org.wso2.carbon.deployment.synchronizer.subversion bundle is missing 2. svnclient bundle is missing 3. If you configure once using the UI, all your subsequent changes to carbon.xml will be ignored Right. You should use one way of configuring this feature. We don't sync configurations from file system to the registry due to the 2-way sync problem.Settings in the registry have priority. 4. UI configurations are stored in local repository. So, if your cluster has several nodes, you will have to make changes to all nodes one by one.\ That's right. This is because within a single cluster some nodes will be in auto checkout mode and some nodes (usually one) will be in auto commit mode. We used to store these settings in config registry about a year ago, but with that we cannot use this component to actually configure a useful clustered setup. That way either everyone will be in auto commit mode or everyone will be in auto checkout mode. So we moved the settings to the local repo. It's a per node setting. On a related note, the way we handle service metadata is, we give precedence to the metadata stored in the metadata repository (earlier this was the config registry). But when the original artifact was changed or re-uploaded, we used to clear out all the data in the metadata repo, and give precedence to the metadata in the uploaded artifact. If the UI is going be there, we should have something similar. Yesterday, we had an issue with the UI based depsync config, then tried to change the settings in the carbon.xml, and were in for a surprise when it was not picked up. Then we had to go into the implementation, and figure out that we would need to go to the registry browser and remove the depsync configuration. This sort of thing may be too much for an average user. Ok got the point. Up until now we have been recommending users to use one of the provided ways to set this up. Trying to use a bit of this and bit of that usually leads to conflicts such as the one you have described. Implementing something like service persistence is tricky here, since there is no 'artifact' object involved with this to detect changes from. What we can do is to flip the priority order and give prominence to carbon.xml when the synchronizer seems to be enabled in both fronts. I think that should take care of the situation you have described and might even be useful when somebody first tries out a configuration through UI and then wants to move it to carbon.xml. Thanks, Hiranya Thanks, Hiranya On Fri, Apr 20, 2012 at 6:53 PM, Afkham Azeez az...@wso2.com wrote: Folks, Has anybody tested this with the new packs? -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] UI Support for the SVN Based Deployment Synchronizer
Hi Azeez, On Fri, Apr 20, 2012 at 11:31 AM, Afkham Azeez az...@wso2.com wrote: On Fri, Apr 20, 2012 at 11:23 AM, Supun Kamburugamuva supu...@gmail.comwrote: In general I think having two ways of configuration is a mistake. Having that kind of a model confuses users and make the life harder for developers as well. Also it means we haven't figured out the correct places for correct configuration as well. If there are two ways of configurations they should be synched. For example if both carbon.xml and UI are allowed, a change done in UI should be reflected in carbon.xml and vise versa. Which makes things very messy! :) We just need to keep this simple, identify the roles people play, and then decide what to have in the UI and what to have in the config files. It is a myth that UIs are more user friendly and config files are not. Depending on the situation requirement, UIs or config files should be chosen. We have gained a lot of experience in managing Carbon production deployments through running StratosLive production clusters, and now have quite a good idea where each have their uses. Clearly, our techops team will never use the UIs to configure SLive, so that gives a good indication of how other techops admin teams will configure our servers. True. And that's why we don't include the deployment sync FE components in any of the Stratos packs. Our unique architecture allows users to mix and match stuff to meet their functionality and usability requirements. So why not provide a UI where possible? Different people have different attitudes towards software and user experience. While some are quite happy to edit raw XML files, some are not. Our architecture can easily support both categories. Thanks, Hiranya Thanks, Supun.. On Fri, Apr 20, 2012 at 1:49 AM, Nuwan Dias nuw...@wso2.com wrote: Ok then, we'll have both options. If configurations are specified in carbon.xml, run the UI in read-only mode and display an Information Message. If not, allow users to configure through the UI. Thanks, NuwanD. On Fri, Apr 20, 2012 at 11:13 AM, Afkham Azeez az...@wso2.com wrote: On Fri, Apr 20, 2012 at 11:02 AM, Hiranya Jayathilaka hira...@wso2.com wrote: On Fri, Apr 20, 2012 at 11:00 AM, Afkham Azeez az...@wso2.com wrote: On Fri, Apr 20, 2012 at 10:58 AM, Hiranya Jayathilaka hira...@wso2.com wrote: On Fri, Apr 20, 2012 at 10:47 AM, Miyuru Wanninayaka miy...@wso2.com wrote: One alternative is support both registry and carbon.xml configuration and give priority to carbon.xml. So if someone configured deployment synchronizer by editing carbon.xml, UI will just run on read-only mode. UI should only allow configuring if dep-sync is not configured in carbon.xml. That is how it's presently implemented. So just leave the code as it is without removing anything, and it'll work just fine. See my previous mail. I don't believe this is useful in the Carbon console since configuring this is not part of the Carbon admin's role. That's not true. We already have users who extensively use this UI. It's great in dev and staging environments where developers can access the system over the web and try out stuff. OK. Let's leave it at it then. The UI looks great, and information like last checked out time commit now are useful. However, I don't see the configuration part of this being used in SLive like production setups. See Sanjaya's response. Thanks, Hiranya Thanks, Hiranya On Fri, Apr 20, 2012 at 10:27 AM, Sanjaya Ratnaweera sanj...@wso2.com wrote: On Thu, Apr 19, 2012 at 2:59 PM, Afkham Azeez az...@wso2.comwrote: What do you mean this will make the carbon.xml based synchronizer obsolete? You mean we won't be able to configure the server using the carbon.xml file and will be forced to use the UI to do that? If so, -1. It will be a huge usability issue for sysadmins. Talk to Sanjaya see how we do things to manage Carbon servers in production. Yes, we never touch UI when managing deployments. For example in Stratoslive we change configuration files and keep them in a separate location. At the deployment time we unzip a fresh pack and sync changed configurations with that. If we store those configurations in local registry we may have to login to each and every instance and change. This is not a one time change, because sometimes we delete the pack and unzip a fresh one when there are file corruptions, etc. Anyway keeping configurations in a XML file is much easier for production deployment. Thanks ~sanjaya On Thu, Apr 19, 2012 at 1:52 PM, Nuwan Dias nuw...@wso2.comwrote: Hi Hiranya, Thanks for the suggestions, will increase the SVN URL field length. Yes, input validations have been done. Thanks, NuwanD. On Thu, Apr 19, 2012 at 1:47 PM, Hiranya Jayathilaka hira...@wso2.com wrote: Looks pretty good. Please increase the length of the SVN URL input field. URL fields
[Dev] [API Mananger] Removing the REST URL Postfix
Hi Folks, The APIs created by the API manager has the following mediator setting to remove the URL postfix section: property name=REST_URL_POSTFIX scope=axis2 action=remove/ In the last review we had we decided to get rid of it. Shall I go ahead and make the necessary changes? Thanks -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [API Manager] HTTP Method Selector in API Provider
I think the the Resource Method selector in the API provider UI is wrong. It only supports selecting one method for any given template. But we need the ability to support multiple methods (possibly all methods) for a given resource. This is particularly important in the case of default resource. -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API Manager] HTTP Method Selector in API Provider
On Fri, Apr 20, 2012 at 12:40 PM, Hiranya Jayathilaka hira...@wso2.comwrote: I think the the Resource Method selector in the API provider UI is wrong. It only supports selecting one method for any given template. But we need the ability to support multiple methods (possibly all methods) for a given resource. This is particularly important in the case of default resource. I think this should be a set of check boxes. By default everything should be selected. -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [API Manager] Two API Store Implementations
Folks, What is the difference between api-store-web and api-store-new? Which one should we be doing fixes on? Thanks -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] UI Support for the SVN Based Deployment Synchronizer
Looks pretty good. Please increase the length of the SVN URL input field. URL fields are usually long. I hope proper input validations are all in place. Thanks, Hiranya On Thu, Apr 19, 2012 at 12:18 PM, Nuwan Dias nuw...@wso2.com wrote: Hi, I have developed a UI for the SVN based deployment synchronizer as per the task in https://wso2.org/jira/browse/ESBJAVA-893. This will make is possible to provide svn parameters for the svn based deployment synchronizer through the UI. It will however make the existing server configuration based (carbon.xml) deployment synchronizer obsolete and will be using the local registry to store and retrieve svn parameters. A screenshot of the deployment synchronizer page is attached herewith. Suggestions welcome. Thanks, -- Nuwan Dias Software Engineer - WSO2, Inc. Integration Technologies Team email : nuw...@wso2.com Phone : +94 777 775 729 -- Nuwan Dias Software Engineer - WSO2, Inc. Integration Technologies Team email : nuw...@wso2.com Phone : +94 777 775 729 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Error When Removing Transport Binding
(ServletTilesRequestContext.java:185) at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:419) at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:370) at org.wso2.carbon.ui.action.ActionHelper.render(ActionHelper.java:52) at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:101) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:61) at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:155) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1600) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Failure in ESB samples
You need to install the JCE policy files to run security samples. Thanks, Hiranya On Wed, Apr 18, 2012 at 1:29 PM, Vijitha Kumara viji...@wso2.com wrote: FYI... Encountered this while running a verify against the platform... == Results : Failed tests: testOutgoingSecurity(org.wso2.esb.samples.security.Sample100Test): Read timed out testSecurityHeadersPassThrough(org.wso2.esb.samples.security.Sample153Test): Error in encryption testSecuredProxyService(org.wso2.esb.samples.security.Sample200Test): Error in encryption Tests run: 32, Failures: 3, Errors: 0, Skipped: 0 == -- Vijitha Kumara Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: viji...@wso2.com Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Invitation: [Integration TG] Code Review @ Wed Apr 18 10am - 11am (sur...@wso2.com)
We have a process to follow up these stuff - Creating JIRAs is part of that. Please refer the code review guidelines doc I shared yesterday. Thanks, Hiranya On Wed, Apr 18, 2012 at 5:09 PM, Afkham Azeez az...@wso2.com wrote: Have these notes been added to Crucible? Also, we need to create one or more corresponding Jira issues to keep track of the improvements. In the past, we lost track of many of the comments suggestions because there was no way to follow up. If there are Jira issues linked to the relevant Crucible projects, that will not happen. On Wed, Apr 18, 2012 at 4:54 PM, Suresh Attanayaka sur...@wso2.comwrote: Hi All, Following are some of the points and suggestions brought up at the code review, please feel free to add up the missing points. - Rename the modules. The name Deployment doesn't give the correct meaning, suggestion was to rename it to SCIM Impl. - Remove the invalid annotations in the source. - Instead of using a single validator for SCIM object validation, use multiple validators for each type. Use an abstract validator and then create concrete validators for each type. - Extract a private method from the attribute encoder methods (simple, complex etc) and move all the common stuff to over there. - Write test cases for all the Parsers. - In the createUser() method, do all the sanity checkups at the beginning of the method. - At the getEncoder() method of the AbstractResourceEndpoint, the method should throw an exception if the encodeMap object is empty. - Do log the code. Use commons logging. - Warnings must be used at the removeAnyReadOnlyAttributes() method. - Try to optimize the nested if statements in the removeAnyReadOnlyAttributes() method. - Move encodeSCIMException() method to another Utill class instead of having it in an Abstract class. - Improve the Java Docs. Mention when exceptions are thrown etc. - Try to reuse HTTP constants instead of redefining them if possible. - The length check is unnecessary in the setEmails() method. - Write test cases for the basics of the SCIM protocol. Thanks regards, -Suresh On Tue, Apr 17, 2012 at 7:21 PM, Hasini Gunasinghe has...@wso2.comwrote: more details »https://www.google.com/calendar/event?action=VIEWeid=bDdsZHBlbGUwNmk0cDhsOXQ1ZDJnZDNrMTAgc3VyZXNoQHdzbzIuY29ttok=MTUjaGFzaW5pQHdzbzIuY29tZTNhZDYyZGE3ZjAyOGEwYTEyNThlNWZkZjI1Nzg4NWU0MzViODEwMQctz=Asia/Colombohl=en [Integration TG] Code Review Details: Project being reviewed: WSO2 Charon Link to crucible project:http://wso2.org/crucible/cru/WSCC001-1http://www.google.com/url?q=http%3A%2F%2Fwso2.org%2Fcrucible%2Fcru%2FWSCC001-1ust=133467789702usg=AFQjCNE5LnfBOQT6lBrlICwSfaHDdPVX4A Other info - Link to the related class diagrams: https://svn.wso2.org/repos/wso2/trunk/commons/charon/documentation/http://www.google.com/url?q=https%3A%2F%2Fsvn.wso2.org%2Frepos%2Fwso2%2Ftrunk%2Fcommons%2Fcharon%2Fdocumentation%2Fust=133467789702usg=AFQjCNG5MSVi2fM-Ho-hC3VJUN1UXUsfoQ *When* Wed Apr 18 10am – 11am Colombo *Where* LK #58 5th Floor - Meeting room (maphttp://maps.google.lk/maps?q=LK+%2358+5th+Floor+-+Meeting+roomhl=en ) *Calendar* sur...@wso2.com *Who* • has...@wso2.com - organizer • Asela Pathberiya • Johann Nallathamby • Thilina Buddhika • Hiranya Jayathilaka • dev@wso2.org • Suresh Attanayaka Going? ***Yeshttps://www.google.com/calendar/event?action=RESPONDeid=bDdsZHBlbGUwNmk0cDhsOXQ1ZDJnZDNrMTAgc3VyZXNoQHdzbzIuY29trst=1tok=MTUjaGFzaW5pQHdzbzIuY29tZTNhZDYyZGE3ZjAyOGEwYTEyNThlNWZkZjI1Nzg4NWU0MzViODEwMQctz=Asia/Colombohl=en- Maybehttps://www.google.com/calendar/event?action=RESPONDeid=bDdsZHBlbGUwNmk0cDhsOXQ1ZDJnZDNrMTAgc3VyZXNoQHdzbzIuY29trst=3tok=MTUjaGFzaW5pQHdzbzIuY29tZTNhZDYyZGE3ZjAyOGEwYTEyNThlNWZkZjI1Nzg4NWU0MzViODEwMQctz=Asia/Colombohl=en- Nohttps://www.google.com/calendar/event?action=RESPONDeid=bDdsZHBlbGUwNmk0cDhsOXQ1ZDJnZDNrMTAgc3VyZXNoQHdzbzIuY29trst=2tok=MTUjaGFzaW5pQHdzbzIuY29tZTNhZDYyZGE3ZjAyOGEwYTEyNThlNWZkZjI1Nzg4NWU0MzViODEwMQctz=Asia/Colombohl=en ***more options »https://www.google.com/calendar/event?action=VIEWeid=bDdsZHBlbGUwNmk0cDhsOXQ1ZDJnZDNrMTAgc3VyZXNoQHdzbzIuY29ttok=MTUjaGFzaW5pQHdzbzIuY29tZTNhZDYyZGE3ZjAyOGEwYTEyNThlNWZkZjI1Nzg4NWU0MzViODEwMQctz=Asia/Colombohl=en Invitation from Google Calendar https://www.google.com/calendar/ You are receiving this email at the account sur...@wso2.com because you are subscribed for invitations on calendar sur...@wso2.com. To stop receiving these notifications, please log in to https://www.google.com/calendar/ and change your notification settings for this calendar. -- Suresh Attanayake Software Engineer; WSO2 Inc. http://wso2.com/ Blog : http://sureshatt.blogspot.com/ Twitter : https://twitter.com/sureshatt LinkedIn : http://lk.linkedin.com/in/sureshatt Mobile : +94755012060,+94770419136,+94710467976
Re: [Dev] JDK 1.7 Issues
On Wed, Apr 18, 2012 at 7:20 PM, Supun Kamburugamuva supu...@gmail.comwrote: I tried the latest ESB with JDK 1.7 and it didn't even start due to a error in the startup script. This is because the wso2server.sh in released ESB versions check for JDK 1.6. You can simply comment out this check in the shell script and start the server up. Thanks, Hiranya Supun. On Wed, Apr 18, 2012 at 9:43 AM, Afkham Azeez az...@wso2.com wrote: Please open up Jiras for all JDK 7 runtime issues On Wed, Apr 18, 2012 at 7:08 PM, Isuru Suriarachchi is...@wso2.comwrote: Hi all, Have we decided to support JDK 1.7 for Carbon 4.0? There are plenty of JDK 1.7 related issues in our platform. At least carbon core doesn't get built on 1.7. In addition to build issues, there are plenty of run time issues as well which only occurs on jdk 1.7. I think It will take considerable amount of time to address all these issues and it can affect the release deadlines. Thanks, ~Isuru -- Isuru Suriarachchi Technical Lead WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Supun Kamburugamuva Member, Apache Software Foundation; http://www.apache.org E-mail: supu...@gmail.com su...@wso2.com; Mobile: +94 77 431 3585 Blog: http://supunk.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] SNMP Support for Synapse/ESB
I've implemented SNMP support for Synapse. We can release this with the next ESB release. Refer [1] and [2] for more details. [1] - http://osdir.com/ml/dev-synapse.apache.org/2012-04/msg2.html [2] - http://osdir.com/ml/dev-synapse.apache.org/2012-04/msg3.html -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Next ESB version?
The only new features we have are: 1. SAP transport with full IDocs support and experimental BAPI support 2. Mediation library support 3. API versioning support 4. Endpoint unification 5. EJB mediator 6. MSMQ support 7. Cloud connectors - LinkedIn, Twitter, SFDC (experimental) 8. XPath 2.0 support (experimental) We can hopefully squeeze in the message relay stuff too. Other than that there's a bunch of improvements and rewrites we have done, but technically they don't count as new features. Does this justify a 4.5? Thanks, Hiranya On Wed, Apr 4, 2012 at 4:46 PM, Paul Fremantle p...@wso2.com wrote: I think this sounds like a 4.5. Paul On 4 April 2012 12:02, Isabelle Mauny isabe...@wso2.com wrote: All, We are adding quite a few features to this release, as per latest plan on GDocs. Doesn't that justify a 4.5 ? Isabelle. -- Isabelle Mauny Director, Product Management; WSO2, Inc.; http://wso2.com/ email: isabe...@wso2.com isabe...@wso2.com - mobile: +34 616050684 On Apr 4, 2012, at 9:57 AM, Hiranya Jayathilaka wrote: On Wed, Apr 4, 2012 at 11:09 AM, Kasun Indrasiri ka...@wso2.com wrote: On Tue, Apr 3, 2012 at 3:06 PM, Miyuru Wanninayaka miy...@wso2.comwrote: Hi all, We still haven't decided on version for next ESB release which is based on carbon 4.0.0. Latest released ESB version is 4.0.3 and next release will not have huge changes to consider as 5.0.0. I'm thinking about 4.[1-5].0 How about 4.1.0? +1 Thanks, Hiranya WDYT? -- Thanks, Miyuru ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Kasun Indrasiri Associate Technical Lead WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 71 536 4128 Blog : http://kasunpanorama.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
