from:"Vivekananthan Sivanayagam"

Re: [Dev] Amazon Lambda connector for WSO2 Enterprise Integrator

2017-08-12 Thread Vivekananthan Sivanayagam

Hi Miyuru,

You can refer [1] to get an idea of writing connector and refer [2] to
understand how "Amazon DynamoDB Connector" connector is working, you can
find an implementation here[3].


[1] https://docs.wso2.com/display/ESBCONNECTORS/Writing+a+Connector
[2] https://docs.wso2.com/display/ESBCONNECTORS/Amazon+DynamoDB+Connector
[3] https://github.com/wso2-extensions/esb-connector-amazondynamodb

Thanks,
Vivek

Vivekananthan Sivanayagam
Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Fri, Aug 11, 2017 at 7:54 PM, Miyuru Madusanka <miyurumadusa...@yahoo.com
> wrote:

> Hello dev guys at WSO2,
> I am working with the project and need some help from you. I need to know
> what are the resources I need to know/ follow to work on the below project.
> I am not familiar with any of your products earlier. So, could you please
> suggest how should I start or what are the things I need to practice? Your
> answers are much appreciated.  Thank you.
> Amazon Lambda connector for WSO2 Enterprise Integrator
>
> ___
> 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] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0

2017-06-27 Thread Vivekananthan Sivanayagam

Hi Hasitha,

We were able to deploy the Amazon DynamoDB connector, Can you try with
fresh ESB pack?

[2017-06-28 09:31:43,065]  INFO - LibraryArtifactDeployer Synapse Library
named '{org.wso2.carbon.connector}amazondynamodb' has been deployed from
file :
/home/vive/Documents/wso2esb-4.9.0/repository/deployment/server/synapse-libs/amazondynamodb-connector-1.0.0.zip

[2017-06-28 09:32:09,536]  INFO - SynapseImportFactory Successfully created
Synapse Import: amazondynamodb

Thanks

Vivekananthan Sivanayagam
Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Wed, Jun 28, 2017 at 9:13 AM, Hasitha Jayasundara <
hasithajayasunda...@gmail.com> wrote:

> Hi Malaka,
>
> Still the error occurs. I tried to upload the 
> amazondynamodb-connector-1.0.0.zip
> from the store and same error pops up.Any ideas??
>
> On Wed, Jun 28, 2017 at 5:47 AM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Hi Hasitha,
>>
>> Maybe the connector is corrupted while uploading?
>>
>> Try manually copying the file to /repository/deployment/server/synapse-
>> libs
>>
>> On Wed, Jun 28, 2017 at 3:52 AM, Hasitha Jayasundara <
>> hasithajayasunda...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> Find the connector implementation for IBM-MQ at [1].When the zip file is
>>> deployed the to the mgt console it gives me this error.
>>>
>>> Error while extracting Synapse Library : IBMMQconnector-connector-1.0.0
>>> .zip
>>> org.apache.synapse.SynapseException: Error while extracting Synapse
>>> Library : IBMMQ-connector-1.0.0.zip
>>> at org.apache.synapse.libraries.util.LibDeployerUtils.extractSy
>>> napseLib(LibDeployerUtils.java:426)
>>> at org.apache.synapse.libraries.util.LibDeployerUtils.createSyn
>>> apseLibrary(LibDeployerUtils.java:65)
>>> at org.apache.synapse.deployers.LibraryArtifactDeployer.deploy(
>>> LibraryArtifactDeployer.java:60)
>>> at org.apache.axis2.deployment.repository.util.DeploymentFileDa
>>> ta.deploy(DeploymentFileData.java:136)
>>> at org.apache.axis2.deployment.DeploymentEngine.doDeploy(Deploy
>>> mentEngine.java:807)
>>> at org.apache.axis2.deployment.repository.util.WSInfoList.updat
>>> e(WSInfoList.java:144)
>>> at org.apache.axis2.deployment.RepositoryListener.update(Reposi
>>> toryListener.java:377)
>>> at org.apache.axis2.deployment.RepositoryListener.checkServices
>>> (RepositoryListener.java:254)
>>> at org.apache.axis2.deployment.RepositoryListener.startListener
>>> (RepositoryListener.java:371)
>>> at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRep
>>> ository(SchedulerTask.java:59)
>>> at org.apache.axis2.deployment.scheduler.SchedulerTask.run(Sche
>>> dulerTask.java:67)
>>> at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTas
>>> k.runAxisDeployment(CarbonDeploymentSchedulerTask.java:93)
>>> at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTas
>>> k.run(CarbonDeploymentSchedulerTask.java:138)
>>> at java.util.concurrent.Executors$RunnableAdapter.call(Executor
>>> s.java:511)
>>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>>> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu
>>> tureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>>> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu
>>> tureTask.run(ScheduledThreadPoolExecutor.java:294)
>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>>> Executor.java:1142)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>>> lExecutor.java:617)
>>> at java.lang.Thread.run(Thread.java:748)
>>> Caused by: java.io.FileNotFoundException: /home/hasitha/ESB%204.9.0/wso2
>>> esb-4.9.0/repository/deployment/server/synapse-libs/IBMMQconnector-connector-1.0.0.zip
>>> (No such file or directory)
>>> at java.util.zip.ZipFile.open(Native Method)
>>> at java.util.zip.ZipFile.(ZipFile.java:219)
>>> at java.util.zip.ZipFile.(ZipFile.java:149)
>>> at java.util.zip.ZipFile.(ZipFile.java:120)
>>> at org.apache.synapse.libraries.util.LibDeployerUtils.extract(L
>>> ibDeployerUtils.java:448)
>>> at org.apache.synapse.libraries.util.LibDeployerUtils.extractSy
>>> napseLib(LibDeployerUtils.java:424)
>>> ... 19 more
>>>
>>> Any comments.
>>>
>>> [1].https://github.com/hasithajayasundara/IBM-MQ-connector
>>>
>>> On Tue, Jun 20, 2017 at 7:25 AM, Hasitha Jayasundara <
>>> hasi

Re: [Dev] Find a way to get file name while reading a file using WSO2 ESB File Connector 2

2017-06-10 Thread Vivekananthan Sivanayagam

Hi Malaka,

Thanks for the suggestion and Yes, we can add to a synapse property and
then we can get that property whenever it needs.

Thanks,
Vivek

Vivekananthan Sivanayagam
Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Fri, Jun 9, 2017 at 9:03 AM, Malaka Silva <mal...@wso2.com> wrote:

> Why Soap header (Or even HTTP header)? Can't you add to a synapse property?
>
> On Thu, Jun 8, 2017 at 7:46 PM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> Hi All,
>>
>> I am in the process of resolving JIRA [1], here we have to show the
>> reading file name.To overcome this, I've added the file name in the
>> header[2] and get the value[3] in the proxy. I referred[4] to implement
>> that.
>>
>> [2]
>>
>>  public static void buildHeader(MessageContext messageContext,String
>> fileName) {
>> SOAPEnvelope env = messageContext.getEnvelope();
>> if (env == null) {
>> return;
>> }
>> SOAPFactory fac = (SOAPFactory) env.getOMFactory();
>> SOAPHeader header = env.getHeader();
>> if (header == null) {
>> header = fac.createSOAPHeader(env);
>> }
>> SOAPHeaderBlock hb = header.addHeaderBlock("File_Name",
>> fac.createOMNamespace(FileConstants.FILECON,
>> FileConstants.FILE_READ));
>> hb.setText(fileName);
>> }
>> }
>>
>> [3]
>>
>> 
>> http://ws.apache.org/ns/synapse;
>>name="File_Read"
>>transports="https http"
>>startOnLoad="true">
>>
>>
>>   
>>  
>>  
>>  
>>  http://localhost:9000"/>
>>  
>> {$ctx:source}
>> {$ctx:contentType}
>> {$ctx:filePattern}
>>  
>>  > scope="default"/>
>>  
>> > expression="get-property('fileName')"/>
>>  
>>      
>>   
>>
>> 
>>
>>
>> Is this a correct way to achieve this functionality in File Read
>> operation? Give me a suggestion on above approach?
>>
>>
>> [1] https://wso2.org/jira/projects/ESBCONNECT/issues/ESBCONNECT-192
>>
>> [4] https://github.com/wso2/wso2-synapse/blob/master/modules
>> /core/src/main/java/org/apache/synapse/mediators/trans
>> form/HeaderMediator.java
>>
>> Thanks,
>>
>> Vivekananthan Sivanayagam
>> Software Engineer | WSO2
>> E:vivekanant...@wso2.com
>> M:+94752786138 <+94%2075%20278%206138>
>>
>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Associate Director / Architect
> M: +94 777 219 791 <+94%2077%20721%209791>
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> https://wso2.com/signature
> http://www.wso2.com/about/team/malaka-silva/
> <http://wso2.com/about/team/malaka-silva/>
> https://store.wso2.com/store/
>
> Don't make Trees rare, we should keep them with care
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Find a way to get file name while reading a file using WSO2 ESB File Connector 2

2017-06-08 Thread Vivekananthan Sivanayagam

Hi All,

I am in the process of resolving JIRA [1], here we have to show the reading
file name.To overcome this, I've added the file name in the header[2] and
get the value[3] in the proxy. I referred[4] to implement that.

[2]

 public static void buildHeader(MessageContext messageContext,String
fileName) {
SOAPEnvelope env = messageContext.getEnvelope();
if (env == null) {
return;
}
SOAPFactory fac = (SOAPFactory) env.getOMFactory();
SOAPHeader header = env.getHeader();
if (header == null) {
header = fac.createSOAPHeader(env);
}
SOAPHeaderBlock hb = header.addHeaderBlock("File_Name",
fac.createOMNamespace(FileConstants.FILECON,
FileConstants.FILE_READ));
hb.setText(fileName);
}
}

[3]


http://ws.apache.org/ns/synapse;
   name="File_Read"
   transports="https http"
   startOnLoad="true">
   
   
  
 
 
 
 http://localhost:9000"/>
 
{$ctx:source}
{$ctx:contentType}
{$ctx:filePattern}
 
 
 

 
 
  
   



Is this a correct way to achieve this functionality in File Read operation?
Give me a suggestion on above approach?


[1] https://wso2.org/jira/projects/ESBCONNECT/issues/ESBCONNECT-192

[4]
https://github.com/wso2/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/mediators/transform/HeaderMediator.java

Thanks,

Vivekananthan Sivanayagam
Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138 <+94%2075%20278%206138>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Configure the subject claim and set a default value only if no value is configured in IdP configuration

2017-04-19 Thread Vivekananthan Sivanayagam

Hi ,

Please find the PR[1],

[1]
https://github.com/wso2-extensions/identity-outbound-auth-pinterest/pull/1/

Thanks,
Vivek

Vivekananthan Sivanayagam
Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Wed, Apr 19, 2017 at 2:53 PM, Ruwan Abeykoon <ruw...@wso2.com> wrote:

> Hi Vivek,
> Yes,
> I made a mistake, this is wrong.
> subjectFromClaims = claimMappings.get(claimMapping);
>
> and
> subjectFromClaims = claims.get(claimMapping);
> is the correct one.
>
> Cheers,
> Ruwan.
>
>
> On Wed, Apr 19, 2017 at 2:36 PM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> Hi Ruwan,
>>
>> Thaks for the suggestion and I have made changes as you suggested and it
>> is working when I changed as "subjectFromClaims =
>> claims.get(claimMapping);" instead of " subjectFromClaims =
>> claimMappings.get(claimMapping);".
>>
>> Thanks,
>> Vivek.
>>
>> Vivekananthan Sivanayagam
>> Software Engineer | WSO2
>> E:vivekanant...@wso2.com
>> M:+94752786138 <+94%2075%20278%206138>
>>
>> On Wed, Apr 19, 2017 at 11:44 AM, Vivekananthan Sivanayagam <
>> vivekanant...@wso2.com> wrote:
>>
>>> Noted.
>>>
>>> Vivekananthan Sivanayagam
>>> Software Engineer | WSO2
>>> E:vivekanant...@wso2.com
>>> M:+94752786138 <+94%2075%20278%206138>
>>>
>>> On Wed, Apr 19, 2017 at 11:23 AM, Ruwan Abeykoon <ruw...@wso2.com>
>>> wrote:
>>>
>>>> Hi All,
>>>> Thanks Vivekananthan to bring this up.
>>>>
>>>> Also any code resembling the following needs to be removed as it
>>>> performs an unwanted action against IDP config. It sets a config on IDP
>>>> within an authenticator, which is wrong practice in programming which
>>>> breaks "Abstraction" principle.
>>>> if (StringUtils.isBlank(context.getExternalIdP().getIdentityPro
>>>> vider().getClaimConfig().getUserClaimURI())) {
>>>> context.getExternalIdP().getId
>>>> entityProvider().getClaimConfig().setUserClaimURI
>>>> (FacebookAuthenticatorConstants.EMAIL);
>>>> }
>>>>
>>>> Instead we should adopt something similar to
>>>> ...
>>>> //Find the subject from the IDP claim mapping, subject Claim URI.
>>>> String subjectFromClaims = FrameworkUtils.getFederatedSub
>>>> jectFromClaims(
>>>> context.getExternalIdP().getIdentityProvider(),
>>>> claims);
>>>>
>>>> //Use preset claim URI on the Authenticator if claim mapping is not
>>>> defined by the admin
>>>>  if (StringUtils.isBlank(subjectFromClaims)) {
>>>>   ClaimMapping claimMapping = new ClaimMapping();
>>>>Claim claim = new Claim();
>>>>claim.setClaimUri(FacebookAuthenticatorConstants.EMAIL)); //Use
>>>> the appropriate claim uri
>>>>claimMapping.setRemoteClaim(claim);
>>>>claimMapping.setLocalClaim(claim);
>>>>subjectFromClaims = claimMappings.get(claimMapping);
>>>>  }
>>>>
>>>> And make the above code reusable across all connectors, either by
>>>> adding them to base class or having a util method somewhere.
>>>>
>>>> Cheers,
>>>> Ruwan
>>>>
>>>>
>>>> On Wed, Apr 19, 2017 at 10:34 AM, Nuwandi Wickramasinghe <
>>>> nuwan...@wso2.com> wrote:
>>>>
>>>>> Ideally any Federated authenticator should give the flexibility to
>>>>> configure the subject claim from IS side. If admin selects a value as 
>>>>> *User
>>>>> ID Claim URI *in the identity provider claim configuration, that
>>>>> selected value needs to be treated as subject of that authenticated user
>>>>> within the IS.
>>>>>
>>>>> By hard coding a subject without checking  *User ID Claim URI *
>>>>> configuration in the identity provider, that authenticator removes
>>>>> that flexibility and totally neglects the configuration.
>>>>>
>>>>> Following method in FrameworkUtils is used to read the configured user
>>>>> Id claim from Identity Provider configuration.
>>>>>
>>>>> FrameworkUtils.getFederatedSubjectFromClaims(IdentityProvider
>>>>> identityProvider, Map&l

Re: [Dev] Configure the subject claim and set a default value only if no value is configured in IdP configuration

2017-04-19 Thread Vivekananthan Sivanayagam

Hi Ruwan,

Thaks for the suggestion and I have made changes as you suggested and it is
working when I changed as "subjectFromClaims = claims.get(claimMapping);"
instead of " subjectFromClaims = claimMappings.get(claimMapping);".

Thanks,
Vivek.

Vivekananthan Sivanayagam
Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Wed, Apr 19, 2017 at 11:44 AM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Noted.
>
> Vivekananthan Sivanayagam
> Software Engineer | WSO2
> E:vivekanant...@wso2.com
> M:+94752786138 <+94%2075%20278%206138>
>
> On Wed, Apr 19, 2017 at 11:23 AM, Ruwan Abeykoon <ruw...@wso2.com> wrote:
>
>> Hi All,
>> Thanks Vivekananthan to bring this up.
>>
>> Also any code resembling the following needs to be removed as it performs
>> an unwanted action against IDP config. It sets a config on IDP within an
>> authenticator, which is wrong practice in programming which breaks
>> "Abstraction" principle.
>> if (StringUtils.isBlank(context.getExternalIdP().getIdentityPro
>> vider().getClaimConfig().getUserClaimURI())) {
>> context.getExternalIdP().getId
>> entityProvider().getClaimConfig().setUserClaimURI
>> (FacebookAuthenticatorConstants.EMAIL);
>> }
>>
>> Instead we should adopt something similar to
>> ...
>> //Find the subject from the IDP claim mapping, subject Claim URI.
>> String subjectFromClaims = FrameworkUtils.getFederatedSubjectFromClaims(
>> context.getExternalIdP().getIdentityProvider(),
>> claims);
>>
>> //Use preset claim URI on the Authenticator if claim mapping is not
>> defined by the admin
>>  if (StringUtils.isBlank(subjectFromClaims)) {
>>   ClaimMapping claimMapping = new ClaimMapping();
>>Claim claim = new Claim();
>>claim.setClaimUri(FacebookAuthenticatorConstants.EMAIL)); //Use
>> the appropriate claim uri
>>claimMapping.setRemoteClaim(claim);
>>claimMapping.setLocalClaim(claim);
>>subjectFromClaims = claimMappings.get(claimMapping);
>>  }
>>
>> And make the above code reusable across all connectors, either by adding
>> them to base class or having a util method somewhere.
>>
>> Cheers,
>> Ruwan
>>
>>
>> On Wed, Apr 19, 2017 at 10:34 AM, Nuwandi Wickramasinghe <
>> nuwan...@wso2.com> wrote:
>>
>>> Ideally any Federated authenticator should give the flexibility to
>>> configure the subject claim from IS side. If admin selects a value as *User
>>> ID Claim URI *in the identity provider claim configuration, that
>>> selected value needs to be treated as subject of that authenticated user
>>> within the IS.
>>>
>>> By hard coding a subject without checking  *User ID Claim URI *
>>> configuration in the identity provider, that authenticator removes that
>>> flexibility and totally neglects the configuration.
>>>
>>> Following method in FrameworkUtils is used to read the configured user
>>> Id claim from Identity Provider configuration.
>>>
>>> FrameworkUtils.getFederatedSubjectFromClaims(IdentityProvider
>>> identityProvider, Map<ClaimMapping, String> claimMappings);
>>>
>>> On Wed, Apr 19, 2017 at 9:43 AM, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> IS Team,
>>>>
>>>> Can you please comment on this?
>>>>
>>>> On Wed, Apr 19, 2017 at 9:40 AM, Vivekananthan Sivanayagam <
>>>> vivekanant...@wso2.com> wrote:
>>>>
>>>>> Hi ,
>>>>>
>>>>> I am working on the ticket[1] and analysed the existing
>>>>> authenticators. As mentioned on the ticket, default subject identifier
>>>>> claim is hard coded[2] and have to modify the existing authenticators as
>>>>> implemented in Facebook authenticator
>>>>> [3][4].
>>>>>
>>>>> @Malaka,
>>>>> If we have to improve the authenticator as mentioned above, it would
>>>>> be better if we include this improvement in Pinterest Authenticator before
>>>>> getting released. can you confirm it?
>>>>>
>>>> IMHO better to add this any new federated authenticator before
>>> releasing it.
>>>
>>>>
>>>>> [1] https://wso2.org/jira/projects/ISCONNECT/issues/ISCONNEC
>>>>> T-49?filter=allopenissues
>&

Re: [Dev] Configure the subject claim and set a default value only if no value is configured in IdP configuration

2017-04-19 Thread Vivekananthan Sivanayagam

Noted.

Vivekananthan Sivanayagam
Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Wed, Apr 19, 2017 at 11:23 AM, Ruwan Abeykoon <ruw...@wso2.com> wrote:

> Hi All,
> Thanks Vivekananthan to bring this up.
>
> Also any code resembling the following needs to be removed as it performs
> an unwanted action against IDP config. It sets a config on IDP within an
> authenticator, which is wrong practice in programming which breaks
> "Abstraction" principle.
> if (StringUtils.isBlank(context.getExternalIdP().getIdentityPro
> vider().getClaimConfig().getUserClaimURI())) {
> context.getExternalIdP().getId
> entityProvider().getClaimConfig().setUserClaimURI
> (FacebookAuthenticatorConstants.EMAIL);
> }
>
> Instead we should adopt something similar to
> ...
> //Find the subject from the IDP claim mapping, subject Claim URI.
> String subjectFromClaims = FrameworkUtils.getFederatedSubjectFromClaims(
> context.getExternalIdP().getIdentityProvider(),
> claims);
>
> //Use preset claim URI on the Authenticator if claim mapping is not
> defined by the admin
>  if (StringUtils.isBlank(subjectFromClaims)) {
>   ClaimMapping claimMapping = new ClaimMapping();
>Claim claim = new Claim();
>claim.setClaimUri(FacebookAuthenticatorConstants.EMAIL)); //Use
> the appropriate claim uri
>claimMapping.setRemoteClaim(claim);
>claimMapping.setLocalClaim(claim);
>subjectFromClaims = claimMappings.get(claimMapping);
>  }
>
> And make the above code reusable across all connectors, either by adding
> them to base class or having a util method somewhere.
>
> Cheers,
> Ruwan
>
>
> On Wed, Apr 19, 2017 at 10:34 AM, Nuwandi Wickramasinghe <
> nuwan...@wso2.com> wrote:
>
>> Ideally any Federated authenticator should give the flexibility to
>> configure the subject claim from IS side. If admin selects a value as *User
>> ID Claim URI *in the identity provider claim configuration, that
>> selected value needs to be treated as subject of that authenticated user
>> within the IS.
>>
>> By hard coding a subject without checking  *User ID Claim URI *
>> configuration in the identity provider, that authenticator removes that
>> flexibility and totally neglects the configuration.
>>
>> Following method in FrameworkUtils is used to read the configured user Id
>> claim from Identity Provider configuration.
>>
>> FrameworkUtils.getFederatedSubjectFromClaims(IdentityProvider
>> identityProvider, Map<ClaimMapping, String> claimMappings);
>>
>> On Wed, Apr 19, 2017 at 9:43 AM, Malaka Silva <mal...@wso2.com> wrote:
>>
>>> IS Team,
>>>
>>> Can you please comment on this?
>>>
>>> On Wed, Apr 19, 2017 at 9:40 AM, Vivekananthan Sivanayagam <
>>> vivekanant...@wso2.com> wrote:
>>>
>>>> Hi ,
>>>>
>>>> I am working on the ticket[1] and analysed the existing authenticators.
>>>> As mentioned on the ticket, default subject identifier claim is hard
>>>> coded[2] and have to modify the existing authenticators as implemented in
>>>> Facebook authenticator
>>>> [3][4].
>>>>
>>>> @Malaka,
>>>> If we have to improve the authenticator as mentioned above, it would be
>>>> better if we include this improvement in Pinterest Authenticator before
>>>> getting released. can you confirm it?
>>>>
>>> IMHO better to add this any new federated authenticator before releasing
>> it.
>>
>>>
>>>> [1] https://wso2.org/jira/projects/ISCONNECT/issues/ISCONNEC
>>>> T-49?filter=allopenissues
>>>> [2] https://github.com/wso2-extensions/identity-outbound-aut
>>>> h-linkedIn/blob/master/component/src/main/java/org/wso2/carb
>>>> on/identity/authenticator/linkedIn/LinkedInAuthenticator.java#L281
>>>> [3] https://github.com/wso2-extensions/identity-outbound-aut
>>>> h-facebook/blob/master/components/org.wso2.carbon.identity.a
>>>> pplication.authenticator.facebook/src/main/java/org/wso2/car
>>>> bon/identity/application/authenticator/facebook/FacebookAuth
>>>> enticator.java#L352
>>>> [4] https://docs.wso2.com/display/IS530/Logging+in+to+the+Id
>>>> entity+Server+using+Facebook+Credentials#LoggingintotheIdent
>>>> ityServerusingFacebookCredentials-ConfiguringclaimmappingsforFacebook
>>>>
>>>>
>>>> Thanks,
>>>>
>&

[Dev] Configure the subject claim and set a default value only if no value is configured in IdP configuration

2017-04-18 Thread Vivekananthan Sivanayagam

Hi ,

I am working on the ticket[1] and analysed the existing authenticators. As
mentioned on the ticket, default subject identifier claim is hard coded[2]
and have to modify the existing authenticators as implemented in Facebook
authenticator
[3][4].

@Malaka,
If we have to improve the authenticator as mentioned above, it would be
better if we include this improvement in Pinterest Authenticator before
getting released. can you confirm it?

[1]
https://wso2.org/jira/projects/ISCONNECT/issues/ISCONNECT-49?filter=allopenissues
[2]
https://github.com/wso2-extensions/identity-outbound-auth-linkedIn/blob/master/component/src/main/java/org/wso2/carbon/identity/authenticator/linkedIn/LinkedInAuthenticator.java#L281
[3]
https://github.com/wso2-extensions/identity-outbound-auth-facebook/blob/master/components/org.wso2.carbon.identity.application.authenticator.facebook/src/main/java/org/wso2/carbon/identity/application/authenticator/facebook/FacebookAuthenticator.java#L352
[4]
https://docs.wso2.com/display/IS530/Logging+in+to+the+Identity+Server+using+Facebook+Credentials#LoggingintotheIdentityServerusingFacebookCredentials-ConfiguringclaimmappingsforFacebook


Thanks,

Vivekananthan Sivanayagam
Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC 2017][ESB]Native inbound and connector for FTP/SFTP operations

2017-03-08 Thread Vivekananthan Sivanayagam


Hi Hasitha,

you can refer the existing file connector[1] which used the Apache
Commons VFS I/O functionalities to get an idea of the file operation
s
when implementing 
the 
connector for FTP/SFTP
.

[1]
https://docs.wso2.com/display/ESBCONNECTORS/Working+with+the+File+Connector+Version+2


Thanks,
Vivek.


Vivekananthan Sivanayagam
Associate Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Wed, Mar 8, 2017 at 8:00 PM, Malaka Silva <mal...@wso2.com> wrote:

> Hi Hasitha,
>
> Good to hear. Keep us posted.
>
> On Wed, Mar 8, 2017 at 7:18 PM, Hasitha Jayasundara <
> hasithajayasunda...@gmail.com> wrote:
>
>> Hi Malaka,
>>
>> Sorry for the late reply.
>>
>> I studied the implementation of ESB connectors[1],File Inbound protocol
>> [2] and now I have a fully understanding about the project and the
>> deliverables. As the description of the project states I'll update the
>> thread with my findings on methods to to be used for file operations via
>> ftp/sftp other than Apache-vfs.
>>
>> (I do confirm that I am a full time student and eligible to participate
>> GSoC)
>>
>> [1] https://docs.wso2.com/display/ESBCONNECTORS/WSO2+ESB+Connectors
>> [2] https://docs.wso2.com/display/ESB500/File+Inbound+Protocol
>>
>>
>> *D.M.Hasitha Nadishan Jayasundara*
>> *Department of Electronic and Telecommunication Engineering*
>> University of Moratuwa
>> *mobile:* *+94711959266 <071%20195%209266>*
>> *blogspot*: learnjavawithisla.blogspot.com/  *email:*
>> hasithajayasunda...@gmail.com
>> <https://www.facebook.com/hasitha.nadishan.3>
>> <https://twitter.com/HNadishan>
>> <https://lk.linkedin.com/in/hasithajayasundara>
>>
>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Associate Director / Architect
> M: +94 777 219 791 <+94%2077%20721%209791>
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> https://wso2.com/signature
> http://www.wso2.com/about/team/malaka-silva/
> <http://wso2.com/about/team/malaka-silva/>
> https://store.wso2.com/store/
>
> Don't make Trees rare, we should keep them with care
>
> ___
> 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] Clarification about File Connector version 2

2017-02-08 Thread Vivekananthan Sivanayagam

Hi Maduranga,

We'll consider those behavior in the future release of the connector. Please
create a Jira.

@Malaka, Can you confirm it?

Thanks,
Vivek.

Vivekananthan Sivanayagam
Associate Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Wed, Feb 8, 2017 at 6:05 PM, Maduranga Siriwardena <madura...@wso2.com>
wrote:

> Hi Vivekananthan,
>
> Comparing the linux file operations,
>
> *cp -r in/ out/*
> "in" folder is copied to the "out" folder and "in" folder will be inside
> the "out" folder.
> *cp in/* out/*
> contents of the "in" folder is copied to the "out" folder and there will
> be no "in" folder inside the "out" folder. This is similar to copy
> operation in the connector when the source is a folder.
>
> *mv in/ out/*
> "in" folder is moved to the "out" folder and "in" folder will be inside
> the "out" folder. "in" folder is removed in the operation.
> *mv in/* out/*
> contents of the "in" folder is moved to the "out" folder and there will be
> no "in" folder inside the "out" folder. After the operation "in" folder is
> also there.
> *mv in/aa.txt out/*
> "aa.txt" file will be moved to the "out" folder. We don't need to specify
> the destination file name.
> *mv in/aa.txt out/aa.txt*
> "aa.txt" file will be moved to the "out" folder. This is similar to the
> file move operation in the connector.
>
> Please do consider the above mentioned linux file copy and move operations
> and the connector behavior.
>
> Thanks,
>
> On Tue, Feb 7, 2017 at 10:39 PM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> Hi Maduranga,
>>
>> The basic behavior of the file/folder move operation is, once you move
>> the file/folder from source to destination completely, the source
>> file/folder will be deleted(Copy followed by Delete). If you want to keep
>> the file/folder after moving to destination, you have to use the copy
>> operation.
>>
>> If you want to move a file, you have to specify the destination as a
>> file(with extension). If you need to just copy the file to the destination
>> folder, here also you can use file copy operation(You don't need to mention
>> the extension in the destination path).
>>
>> Thanks,
>> Vivek
>>
>> Vivekananthan Sivanayagam
>> Associate Software Engineer | WSO2
>> E:vivekanant...@wso2.com
>> M:+94752786138 <+94%2075%20278%206138>
>>
>> On Wed, Feb 8, 2017 at 6:11 AM, Maduranga Siriwardena <madura...@wso2.com
>> > wrote:
>>
>>> Hi Malaka,
>>>
>>> I tried this with Windows local file system.
>>>
>>> Thanks,
>>>
>>> On Tue, Feb 7, 2017 at 6:34 PM, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> Hi Maduranga,
>>>>
>>>> What is the file system / Protocol you tried this with?
>>>>
>>>> On Tue, Feb 7, 2017 at 11:10 PM, Maduranga Siriwardena <
>>>> madura...@wso2.com> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Tue, Feb 7, 2017 at 10:54 AM, Maduranga Siriwardena <
>>>>> madura...@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> While working with the file connector version 2 in [1], I noticed
>>>>>> below limitations.
>>>>>>
>>>>>>1. When moving a folder there is no way to move the contents of a
>>>>>>folder without deleting the source folder.
>>>>>>2. When moving a file, if we specify a folder as a destination,
>>>>>>this folder is converted to a file with the name of the source file
>>>>>>(without the file extension). Shouldn't the file just copied to the
>>>>>>destination folder?
>>>>>>
>>>>>> Destination folder is converted to a file with the destination folder
>>>>> name (not with the name of the source file).
>>>>>
>>>>> Can these be done as improvements to the connector?
>>>>>>
>>>>>> [1] https://store.wso2.com/store/assets/esbconnector/details
>>>>>> /48bab332-c6a6-4f5a-9b79-17e29c7ad4c6
>>>>>>
>>>>>> --
>>>>>> Maduranga Siriwardena
>>>>>> Software Engineer
>>>>>> WSO2 Inc; http://wso2.com/
>

Re: [Dev] Clarification about File Connector version 2

2017-02-07 Thread Vivekananthan Sivanayagam

Hi Maduranga,

The basic behavior of the file/folder move operation is, once you move the
file/folder from source to destination completely, the source file/folder
will be deleted(Copy followed by Delete). If you want to keep the
file/folder after moving to destination, you have to use the copy operation.

If you want to move a file, you have to specify the destination as a
file(with extension). If you need to just copy the file to the destination
folder, here also you can use file copy operation(You don't need to mention
the extension in the destination path).

Thanks,
Vivek

Vivekananthan Sivanayagam
Associate Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Wed, Feb 8, 2017 at 6:11 AM, Maduranga Siriwardena <madura...@wso2.com>
wrote:

> Hi Malaka,
>
> I tried this with Windows local file system.
>
> Thanks,
>
> On Tue, Feb 7, 2017 at 6:34 PM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Hi Maduranga,
>>
>> What is the file system / Protocol you tried this with?
>>
>> On Tue, Feb 7, 2017 at 11:10 PM, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>>
>>>
>>> On Tue, Feb 7, 2017 at 10:54 AM, Maduranga Siriwardena <
>>> madura...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> While working with the file connector version 2 in [1], I noticed below
>>>> limitations.
>>>>
>>>>1. When moving a folder there is no way to move the contents of a
>>>>folder without deleting the source folder.
>>>>2. When moving a file, if we specify a folder as a destination,
>>>>this folder is converted to a file with the name of the source file
>>>>(without the file extension). Shouldn't the file just copied to the
>>>>destination folder?
>>>>
>>>> Destination folder is converted to a file with the destination folder
>>> name (not with the name of the source file).
>>>
>>> Can these be done as improvements to the connector?
>>>>
>>>> [1] https://store.wso2.com/store/assets/esbconnector/details
>>>> /48bab332-c6a6-4f5a-9b79-17e29c7ad4c6
>>>>
>>>> --
>>>> Maduranga Siriwardena
>>>> Software Engineer
>>>> WSO2 Inc; http://wso2.com/
>>>>
>>>> Email: madura...@wso2.com
>>>> Mobile: +94718990591 <+94%2071%20899%200591>
>>>> Blog: http://madurangasblogs.blogspot.com/
>>>> <http://wso2.com/signature>
>>>>
>>>
>>>
>>>
>>> --
>>> Maduranga Siriwardena
>>> Software Engineer
>>> WSO2 Inc; http://wso2.com/
>>>
>>> Email: madura...@wso2.com
>>> Mobile: +94718990591 <071%20899%200591>
>>> Blog: http://madurangasblogs.blogspot.com/
>>> <http://wso2.com/signature>
>>>
>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Associate Director / Architect
>> M: +94 777 219 791 <+94%2077%20721%209791>
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> https://wso2.com/signature
>> http://www.wso2.com/about/team/malaka-silva/
>> <http://wso2.com/about/team/malaka-silva/>
>> https://store.wso2.com/store/
>>
>> Don't make Trees rare, we should keep them with care
>>
>
>
>
> --
> Maduranga Siriwardena
> Software Engineer
> WSO2 Inc; http://wso2.com/
>
> Email: madura...@wso2.com
> Mobile: +94718990591 <+94%2071%20899%200591>
> Blog: http://madurangasblogs.blogspot.com/
> <http://wso2.com/signature>
>
> ___
> 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] File read with enabling streaming

2016-11-25 Thread Vivekananthan Sivanayagam

Hi Kathees,

 I have tried as you mentioned, it is working.

 private void findAndWrite2OutputStream(MessageContext messageContext,
   OutputStream out,
   boolean preserve) throws
AxisFault {
try {
  SOAPEnvelope envelope = messageContext.getEnvelope();
  OMElement contentEle = envelope.getBody().getFirstElement();
if (contentEle != null) {
OMNode node = contentEle.getFirstOMChild();
if (!(node instanceof OMText)) {
String msg = "Wrong Input for the Validator, " +
"the content of the first child element of the
Body " +
"should have the zip file";
log.error(msg);
throw new AxisFault(msg);
}
OMText binaryDataNode = (OMText) node;
DataHandler dh = (DataHandler)
binaryDataNode.getDataHandler();

DataSource dataSource = dh.getDataSource();
if(dataSource instanceof StreamingOnRequestDataSource) {
if (((StreamingOnRequestDataSource)
dataSource).isConsumed()) {
Object httpMethodObj =
messageContext.getProperty(Constants.Configuration.HTTP_METHOD);
if ((httpMethodObj instanceof String) &&
"POST".equals(httpMethodObj)) {
log.warn("Attempting to send an already
consumed request [" +
 messageContext.getTo().getAddress() +
" POST/Empty Message Body]");
}
}

//Ask the data source to stream, if it has not already
cached the request
if (!preserve && dataSource instanceof
StreamingOnRequestDataSource) {
((StreamingOnRequestDataSource)
dataSource).setLastUse(true);
}
}
dh.writeTo(out);
}
} catch (OMException e) {
log.error(e);
throw AxisFault.makeFault(e);
} catch (IOException e) {
    log.error(e);
throw AxisFault.makeFault(e);
}
}

Vivekananthan Sivanayagam
Associate Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Fri, Nov 25, 2016 at 10:52 AM, Kathees Rajendram <kath...@wso2.com>
wrote:

> If the datasource from your operation is not instance of
> StreamingOnRequestDataSource and you can directly write. In this case, you
> don't need to cast.
>
> On Fri, Nov 25, 2016 at 10:20 AM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> Hi Malaka,
>>
>> I am getting the casting exception in the following methods in the
>> carbon-mediation[1].
>>
>> private void findAndWrite2OutputStream(MessageContext messageContext,
>>OutputStream out,
>>boolean preserve) throws
>> AxisFault {
>> try {
>> SOAPEnvelope envelope = messageContext.getEnvelope();
>>   OMElement contentEle = envelope.getBody().getFirstElement();
>> if (contentEle != null) {
>> OMNode node = contentEle.getFirstOMChild();
>> if (!(node instanceof OMText)) {
>> String msg = "Wrong Input for the Validator, " +
>> "the content of the first child element of
>> the Body " +
>> "should have the zip file";
>> log.error(msg);
>> throw new AxisFault(msg);
>> }
>> OMText binaryDataNode = (OMText) node;
>> DataHandler dh = (DataHandler)
>> binaryDataNode.getDataHandler();
>>
>> DataSource dataSource = dh.getDataSource();
>> if (((StreamingOnRequestDataSource)
>> dataSource).isConsumed()) {
>> Object httpMethodObj =
>> messageContext.getProperty(Constants.Configuration.HTTP_METHOD);
>> if ((httpMethodObj instanceof String) &&
>> "POST".equals(httpMethodObj)) {
>> log.warn("Attempting to send an already
>> consumed request [" +
>>  messageContext.getTo().getAddress()
>> + " POST/Empty Message Body]");
>> }
>> }
>>
>> //Ask the data source to stream, if it has not
>> already cach

Re: [Dev] File read with enabling streaming

2016-11-24 Thread Vivekananthan Sivanayagam

Hi Malaka,

I am getting the casting exception in the following methods in the
carbon-mediation[1].

private void findAndWrite2OutputStream(MessageContext messageContext,
   OutputStream out,
   boolean preserve) throws
AxisFault {
try {
SOAPEnvelope envelope = messageContext.getEnvelope();
  OMElement contentEle = envelope.getBody().getFirstElement();
if (contentEle != null) {
OMNode node = contentEle.getFirstOMChild();
if (!(node instanceof OMText)) {
String msg = "Wrong Input for the Validator, " +
"the content of the first child element of the
Body " +
"should have the zip file";
log.error(msg);
throw new AxisFault(msg);
}
OMText binaryDataNode = (OMText) node;
DataHandler dh = (DataHandler)
binaryDataNode.getDataHandler();

DataSource dataSource = dh.getDataSource();
if (((StreamingOnRequestDataSource)
dataSource).isConsumed()) {
Object httpMethodObj =
messageContext.getProperty(Constants.Configuration.HTTP_METHOD);
if ((httpMethodObj instanceof String) &&
"POST".equals(httpMethodObj)) {
log.warn("Attempting to send an already
consumed request [" +
 messageContext.getTo().getAddress() +
" POST/Empty Message Body]");
}
}

//Ask the data source to stream, if it has not already
cached the request
if (!preserve && dataSource instanceof
StreamingOnRequestDataSource) {
((StreamingOnRequestDataSource)
dataSource).setLastUse(true);
}

dh.writeTo(out);
}
} catch (OMException e) {
log.error(e);
throw AxisFault.makeFault(e);
} catch (IOException e) {
log.error(e);
throw AxisFault.makeFault(e);
}
}


[1]
https://github.com/wso2/carbon-mediation/blob/master/components/mediation-monitor/message-relay/org.wso2.carbon.relay/src/main/java/org/wso2/carbon/relay/ExpandingMessageFormatter.java#L185

Vivekananthan Sivanayagam
Associate Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Thu, Nov 24, 2016 at 4:30 PM, Malaka Silva <mal...@wso2.com> wrote:

>
>
> On Thu, Nov 24, 2016 at 4:25 PM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> Hi Malaka,
>>
>> When I enable builders as I mentioned in the previous mail, It is working
>> always for the false statement[1] of streaming even enabling the streaming.
>> We have to use "> class="org.apache.axis2.format.BinaryBuilder"/>", If I use this one, I
>> am getting
>> "PassThroughHttpSender Failed to submit the response" error.
>>
> We have to dig into this and find the root cause.
>
>
>>
>> We were able to write the file content into the message context but could
>> not get this as a response, and I checked the test case and found the
>> reason why it worked, there streaming is set as true and content type is
>> as "text/plain", in this case also consider as an else statement, that is
>> why test cases are passed.
>>
> Currently latest connector read does not work. So ideally the test case
> should fail.
>
>
>>
>> [1]
>>
>> 
>> 
>> InputStream in;
>>
>> if (builder instanceof DataSourceMessageBuilder && "true".equals(streaming)) 
>> {
>> in = null;
>> dataSource = ManagedDataSourceFactory.create(new 
>> FileObjectDataSource(file, contentType));
>> } else {
>> in = new AutoCloseInputStream(file.getContent().getInputStream());
>> dataSource = null;
>> }
>>
>>
>> Vivekananthan Sivanayagam
>> Associate Software Engineer | WSO2
>> E:vivekanant...@wso2.com
>> M:+94752786138
>>
>> On Thu, Nov 24, 2016 at 10:23 AM, Vivekananthan Sivanayagam <
>> vivekanant...@wso2.com> wrote:
>>
>>> Hi Malaka,
>>>
>>> When I use ">> class="org.wso2.carbon.relay.BinaryRelayBuilder"/>" instead of
>>> ">> class="org.apache.axis2.format.BinaryBuilder"/>", it is working fine.
>>>
>>> Vivekananthan Sivanayagam
>>> Associate Software Engineer | WSO2
>>> E:vivekanant...@wso2.com
>>> M:+94752786138
>

Re: [Dev] File read with enabling streaming

2016-11-24 Thread Vivekananthan Sivanayagam

Hi Malaka,

When I enable builders as I mentioned in the previous mail, It is working
always for the false statement[1] of streaming even enabling the streaming.
We have to use "", If I use this one, I am
getting
"PassThroughHttpSender Failed to submit the response" error.

We were able to write the file content into the message context but could
not get this as a response, and I checked the test case and found the
reason why it worked, there streaming is set as true and content type is
as "text/plain", in this case also consider as an else statement, that is
why test cases are passed.

[1]



InputStream in;

if (builder instanceof DataSourceMessageBuilder && "true".equals(streaming)) {
in = null;
dataSource = ManagedDataSourceFactory.create(new
FileObjectDataSource(file, contentType));
} else {
in = new AutoCloseInputStream(file.getContent().getInputStream());
dataSource = null;
}


Vivekananthan Sivanayagam
Associate Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Thu, Nov 24, 2016 at 10:23 AM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Hi Malaka,
>
> When I use " class="org.wso2.carbon.relay.BinaryRelayBuilder"/>" instead of
> " class="org.apache.axis2.format.BinaryBuilder"/>",
> it is working fine.
>
> Vivekananthan Sivanayagam
> Associate Software Engineer | WSO2
> E:vivekanant...@wso2.com
> M:+94752786138
>
> On Wed, Nov 23, 2016 at 3:26 PM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> Hi Makala,
>>
>> I tried the given config and getting the following error.
>>
>> [2016-11-23 15:00:47,188] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> "POST /services/fileconnectorRead HTTP/1.1[\r][\n]"
>> [2016-11-23 15:00:47,189] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> "Host: vive.example.com:8280[\r][\n]"
>> [2016-11-23 15:00:47,189] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> "Connection: keep-alive[\r][\n]"
>> [2016-11-23 15:00:47,189] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> "Content-Length: 115[\r][\n]"
>> [2016-11-23 15:00:47,189] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> "Postman-Token: 1cdab400-d939-ad00-29ca-2d65a4db15fb[\r][\n]"
>> [2016-11-23 15:00:47,189] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> "Cache-Control: no-cache[\r][\n]"
>> [2016-11-23 15:00:47,189] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> "Origin: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop[\r][\n]"
>> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> "User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
>> like Gecko) Chrome/54.0.2840.100 Safari/537.36[\r][\n]"
>> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> "Content-Type: application/json[\r][\n]"
>> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> "Accept: */*[\r][\n]"
>> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> "Accept-Encoding: gzip, deflate[\r][\n]"
>> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> "Accept-Language: en-US,en;q=0.8[\r][\n]"
>> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> "Cookie: exchangecookie=3220c865f3bc4a0981edd476a839a747[\r][\n]"
>> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> "[\r][\n]"
>> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> "{[\n]"
>> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> " "source":"/home/vive/Desktop/FILE/abc.txt",[\n]"
>> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> " "contentType":"application/file",[\n]"
>> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> " "streaming":"true"[\n]"
>> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
>> "}"
>> [2016-11-23 15:00:47,195] ERROR - SynapseJsonPath #stringValueOf. Error
>> evaluating JSON Path <$.address>. Returning empty result. Error>>> invalid
>> path
>> [2016-11-23 15:00:47,199] ERROR - SynapseJsonPath #stringValueOf. Error
>> evaluating JSON Path <$.append>. Returning

Re: [Dev] File read with enabling streaming

2016-11-23 Thread Vivekananthan Sivanayagam

Hi Malaka,

When I use "" instead of
"", it is working fine.

Vivekananthan Sivanayagam
Associate Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Wed, Nov 23, 2016 at 3:26 PM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Hi Makala,
>
> I tried the given config and getting the following error.
>
> [2016-11-23 15:00:47,188] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
> "POST /services/fileconnectorRead HTTP/1.1[\r][\n]"
> [2016-11-23 15:00:47,189] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
> "Host: vive.example.com:8280[\r][\n]"
> [2016-11-23 15:00:47,189] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
> "Connection: keep-alive[\r][\n]"
> [2016-11-23 15:00:47,189] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
> "Content-Length: 115[\r][\n]"
> [2016-11-23 15:00:47,189] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
> "Postman-Token: 1cdab400-d939-ad00-29ca-2d65a4db15fb[\r][\n]"
> [2016-11-23 15:00:47,189] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
> "Cache-Control: no-cache[\r][\n]"
> [2016-11-23 15:00:47,189] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
> "Origin: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop[\r][\n]"
> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
> "User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
> like Gecko) Chrome/54.0.2840.100 Safari/537.36[\r][\n]"
> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
> "Content-Type: application/json[\r][\n]"
> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
> "Accept: */*[\r][\n]"
> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
> "Accept-Encoding: gzip, deflate[\r][\n]"
> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
> "Accept-Language: en-US,en;q=0.8[\r][\n]"
> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
> "Cookie: exchangecookie=3220c865f3bc4a0981edd476a839a747[\r][\n]"
> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
> "[\r][\n]"
> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
> "{[\n]"
> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >> "
> "source":"/home/vive/Desktop/FILE/abc.txt",[\n]"
> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >> "
> "contentType":"application/file",[\n]"
> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >> "
> "streaming":"true"[\n]"
> [2016-11-23 15:00:47,190] DEBUG - wire HTTP-Listener I/O dispatcher-6 >>
> "}"
> [2016-11-23 15:00:47,195] ERROR - SynapseJsonPath #stringValueOf. Error
> evaluating JSON Path <$.address>. Returning empty result. Error>>> invalid
> path
> [2016-11-23 15:00:47,199] ERROR - SynapseJsonPath #stringValueOf. Error
> evaluating JSON Path <$.append>. Returning empty result. Error>>> invalid
> path
> [2016-11-23 15:00:47,206] ERROR - SynapseJsonPath #stringValueOf. Error
> evaluating JSON Path <$.address>. Returning empty result. Error>>> invalid
> path
> [2016-11-23 15:00:47,207] ERROR - SynapseJsonPath #stringValueOf. Error
> evaluating JSON Path <$.append>. Returning empty result. Error>>> invalid
> path
> [2016-11-23 15:00:47,208] ERROR - SynapseJsonPath #stringValueOf. Error
> evaluating JSON Path <$.source>. Returning empty result. Error>>> invalid
> path
> [2016-11-23 15:00:47,208] ERROR - SynapseJsonPath #stringValueOf. Error
> evaluating JSON Path <$.contentType>. Returning empty result. Error>>>
> invalid path
> [2016-11-23 15:00:47,209] ERROR - SynapseJsonPath #stringValueOf. Error
> evaluating JSON Path <$.streaming>. Returning empty result. Error>>>
> invalid path
> [2016-11-23 15:00:47,214] ERROR - FileRead Could not find file with URI ""
> because it is a relative path, and no base URI was provided.
> [2016-11-23 15:00:47,228]  INFO - LogMediator To: 
> /services/001fileconnectorRead,
> MessageID: urn:uuid:f863b8d3-3a50-495c-bae1-2198715a0926, Direction:
> request, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 0,
> ERROR_MESSAGE = Error occured in the mediation of the class mediator,
> Envelope:  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/;> xmlns:axis2ns6="http://w

Re: [Dev] File read with enabling streaming

2016-11-23 Thread Vivekananthan Sivanayagam

21 cannot be cast to
org.wso2.carbon.relay.StreamingOnRequestDataSource
at
org.wso2.carbon.relay.ExpandingMessageFormatter.findAndWrite2OutputStream(ExpandingMessageFormatter.java:185)
at
org.wso2.carbon.relay.ExpandingMessageFormatter.writeTo(ExpandingMessageFormatter.java:100)
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:555)
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:264)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:222)
at
org.apache.synapse.mediators.builtin.RespondMediator.mediate(RespondMediator.java:35)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:59)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
at
org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:210)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:325)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:371)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:151)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[2016-11-23 15:00:47,230] ERROR - Axis2Sender
Accept:*/*,Accept-Encoding:gzip,
deflate,Accept-Language:en-US,en;q=0.8,Cache-Control:no-cache,Content-Type:application/json,Cookie:exchangecookie=3220c865f3bc4a0981edd476a839a747,Host:
vive.example.com:8280,Origin:chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop,Postman-Token:1cdab400-d939-ad00-29ca-2d65a4db15fb,http://schemas.xmlsoap.org/soap/envelope/;>http://ws.apache.org/commons/ns/payload;>SSBjaGVja2VkIHRoZSBmb2xsb3dpbmcgc2NlbmFyaW9bMV0gd2l0aCBzdHJlYW1pbmcgZW5hYmxlLCBJIGFtIGFibGUgc3VjY2VzcyB3aXRoIHRoZSByZXNwb25zZSBmaWxlLiBJIHRyaWVkIDRHQiBmaWxlIHRvIHNlbmQgLCBpdCBpcyB3b3JraW5nLiBXaGVuIEkgY2hlY2tlZCBvbmx5IEZpbGVSZWFkIG9wZXJhdGlvbiB3aXRoIHN0cmVhbWluZywgSSB3YXMgYWJsZSB0byByZWFkIHRoZSBjb250ZW50IGluIHRoZSBtZXNzYWdlIGNvbnRleHQgYnV0IGNvdWxkIG5vdCBidWlsZCBpdCB0aGUgdXNpbmcgRGF0YVNvdXJjZU1lc3NhZ2VCdWlsZGVyIHdpdGggY29udGVudCB0eXBlICJhcHBsaWNhdGlvbi9maWxlIiBhbmQgc2hvd2luZyB0aGUgZm9sbG93aW5nIGVycm9yLiAK
Unexpected error sending message back
org.apache.axis2.AxisFault: Failed to submit the response
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.handleException(PassThroughHttpSender.java:613)
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:266)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:222)
at
org.apache.synapse.mediators.builtin.RespondMediator.mediate(RespondMediator.java:35)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:59)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
at
org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:210)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:325)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:371)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:151)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassCastException: com.sun.proxy.$Proxy21 cannot be
cast to org.wso2.carbon.relay.StreamingOnRequestDataSource
at
org.wso2.carbon.relay.ExpandingMessageFormatter.findAndWrite2OutputStream(ExpandingMessageFormatter.java:185)
at
org.wso2.carbon.relay.ExpandingMessageFormatter.writeTo(ExpandingMessageFormatter.java:100)
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:555)
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:264)
... 15 more


Vivekananthan Sivanayagam
Associate Software Engineer | WSO2
E:vivekanant...@

Re: [Dev] Bulk deleting files with a pattern in file connector

2016-10-17 Thread Vivekananthan Sivanayagam

Hi ,

It is released and published in the store[1] and updated the doc [2] also.

[1]
https://store.wso2.com/store/assets/esbconnector/details/48bab332-c6a6-4f5a-9b79-17e29c7ad4c6
[2]
https://docs.wso2.com/display/ESBCONNECTORS/Working+with+the+File+Connector+Version+2#WorkingwiththeFileConnectorVersion2-delete

Vivekananthan Sivanayagam
Associate Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Tue, Oct 18, 2016 at 9:02 AM, Malaka Silva <mal...@wso2.com> wrote:

> IMO we may not require that at the moment. Will proceed with the one level
> for the moment.
>
> On Mon, Oct 17, 2016 at 11:09 PM, Shazni Nazeer <sha...@wso2.com> wrote:
>
>> HI Vivekanandan,
>>
>> I implemented this intentionally and had the same concern whether it
>> should be recursive. I thought it should not be. But if we need recursive
>> delete IMO it should only be optional, meaning that it shouldn't be the
>> default. May be we can include it as another parameter with 'yes/no" values.
>>
>> @Malaka - Do we need recursive delete. If needed I can implement and send
>> a PR.
>>
>> Shazni Nazeer
>> Associate Technical Lead | WSO2
>>
>> Mob : +94 37331
>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>> Blog : http://shazninazeer.blogspot.com
>>
>> <http://wso2.com/signature>
>>
>> On Mon, Oct 17, 2016 at 6:02 PM, Vivekananthan Sivanayagam <
>> vivekanant...@wso2.com> wrote:
>>
>>> Hi Malaka,
>>>
>>> I have tested and it deletes given pattern files only inside the given
>>> folder not the files inside the subfolder. If folder structure is below as
>>> described,
>>>
>>> Folder
>>>
>>>   Folder001
>>>
>>> test_001.txt
>>>
>>> test_002.txt
>>>
>>> Folder002
>>>
>>> Folder002.1
>>>
>>> test_0021.txt
>>>
>>> test_0022.txt
>>>
>>> test_003.txt
>>>
>>> test_004.txt
>>>
>>> Let's consider that the main folder is Folder and  Folder001, Folder002
>>> ,test_003.txt and test_004.txt are inside the main folder. We are using the
>>> delete operation to delete files inside the main folder(Folder) with
>>> the pattern "test_.*\.txt". It deletes only the files which are inside the
>>> main folder (test_003.txt and test_004.txt are deleted). It does not delete
>>> the files inside the subfolders(Folder001,Folder002).
>>>
>>> Do we need to consider the subfolders too? or can we release with this
>>> improvement?
>>>
>>> Vivekananthan Sivanayagam
>>> Associate Software Engineer | WSO2
>>> E:vivekanant...@wso2.com
>>> M:+94752786138
>>>
>>> On Mon, Oct 17, 2016 at 6:48 PM, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> Thx Shazni,
>>>>
>>>> @Vivekananthan - Can you please check and release.
>>>>
>>>> On Mon, Oct 17, 2016 at 6:36 PM, Shazni Nazeer <sha...@wso2.com> wrote:
>>>>
>>>>> Hi Malaka,
>>>>>
>>>>> Please find the created jiira below and the PR in [2]
>>>>>
>>>>> [1] https://wso2.org/jira/browse/ESBCONNECT-135
>>>>> [2] https://github.com/wso2-extensions/esb-connector-file/pull/14
>>>>>
>>>>> Shazni Nazeer
>>>>> Associate Technical Lead | WSO2
>>>>>
>>>>> Mob : +94 37331
>>>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>>>>> Blog : http://shazninazeer.blogspot.com
>>>>>
>>>>> <http://wso2.com/signature>
>>>>>
>>>>> On Mon, Oct 17, 2016 at 4:33 AM, Malaka Silva <mal...@wso2.com> wrote:
>>>>>
>>>>>> Hi Shazni,
>>>>>>
>>>>>> Create a jira to track this please.
>>>>>>
>>>>>> Feel free to contribute the improvement. :)
>>>>>>
>>>>>>
>>>>>> On Sun, Oct 16, 2016 at 8:11 PM, Vivekananthan Sivanayagam <
>>>>>> vivekanant...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi ,
>>>>>>>
>>>>>>> The existing connector does not have this option to delete. It
>>>>>>> deletes only a single file or given folder, can not work for the 
>>>>>>> pattern at
>>>>>>> the moment.
>>>

Re: [Dev] Bulk deleting files with a pattern in file connector

2016-10-17 Thread Vivekananthan Sivanayagam

Hi Malaka,

I have tested and it deletes given pattern files only inside the given
folder not the files inside the subfolder. If folder structure is below as
described,

Folder

  Folder001

test_001.txt

test_002.txt

Folder002

Folder002.1

test_0021.txt

test_0022.txt

test_003.txt

test_004.txt

Let's consider that the main folder is Folder and  Folder001, Folder002
,test_003.txt and test_004.txt are inside the main folder. We are using the
delete operation to delete files inside the main folder(Folder) with
the pattern "test_.*\.txt". It deletes only the files which are inside the
main folder (test_003.txt and test_004.txt are deleted). It does not delete
the files inside the subfolders(Folder001,Folder002).

Do we need to consider the subfolders too? or can we release with this
improvement?

Vivekananthan Sivanayagam
Associate Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Mon, Oct 17, 2016 at 6:48 PM, Malaka Silva <mal...@wso2.com> wrote:

> Thx Shazni,
>
> @Vivekananthan - Can you please check and release.
>
> On Mon, Oct 17, 2016 at 6:36 PM, Shazni Nazeer <sha...@wso2.com> wrote:
>
>> Hi Malaka,
>>
>> Please find the created jiira below and the PR in [2]
>>
>> [1] https://wso2.org/jira/browse/ESBCONNECT-135
>> [2] https://github.com/wso2-extensions/esb-connector-file/pull/14
>>
>> Shazni Nazeer
>> Associate Technical Lead | WSO2
>>
>> Mob : +94 37331
>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>> Blog : http://shazninazeer.blogspot.com
>>
>> <http://wso2.com/signature>
>>
>> On Mon, Oct 17, 2016 at 4:33 AM, Malaka Silva <mal...@wso2.com> wrote:
>>
>>> Hi Shazni,
>>>
>>> Create a jira to track this please.
>>>
>>> Feel free to contribute the improvement. :)
>>>
>>>
>>> On Sun, Oct 16, 2016 at 8:11 PM, Vivekananthan Sivanayagam <
>>> vivekanant...@wso2.com> wrote:
>>>
>>>> Hi ,
>>>>
>>>> The existing connector does not have this option to delete. It deletes
>>>> only a single file or given folder, can not work for the pattern at the
>>>> moment.
>>>>
>>>> Vivekananthan Sivanayagam
>>>> Associate Software Engineer | WSO2
>>>> E:vivekanant...@wso2.com
>>>> M:+94752786138
>>>>
>>>> On Sun, Oct 16, 2016 at 5:36 PM, Shazni Nazeer <sha...@wso2.com> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> Just double checking, if there's a way to bulk delete files using the
>>>>> file connector. I tried different options but wasn't able to do this.
>>>>>
>>>>> e.g: Given a pattern, Cal_*.xml, should delete Cal_1.xml, Cal_test.xml
>>>>> etc
>>>>>
>>>>> Do you guys know a way to achieve above using the file connector?
>>>>>
>>>>> If not, wouldn't this be a useful improvement for the file-connector
>>>>> [1]
>>>>>
>>>>> [1] https://docs.wso2.com/display/ESBCONNECTORS/Working+with
>>>>> +the+File+Connector+Version+2
>>>>>
>>>>> regards,
>>>>>
>>>>> Shazni Nazeer
>>>>> Associate Technical Lead | WSO2
>>>>>
>>>>> Mob : +94 37331
>>>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>>>>> Blog : http://shazninazeer.blogspot.com
>>>>>
>>>>> <http://wso2.com/signature>
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>> Malaka Silva
>>> Senior Technical Lead
>>> M: +94 777 219 791
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>> Skype : malaka.sampath.silva
>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>> Blog : http://mrmalakasilva.blogspot.com/
>>>
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> https://wso2.com/signature
>>> http://www.wso2.com/about/team/malaka-silva/
>>> <http://wso2.com/about/team/malaka-silva/>
>>> https://store.wso2.com/store/
>>>
>>> Don't make Trees rare, we should keep them with care
>>>
>>
>>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Technical Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> https://wso2.com/signature
> http://www.wso2.com/about/team/malaka-silva/
> <http://wso2.com/about/team/malaka-silva/>
> https://store.wso2.com/store/
>
> Don't make Trees rare, we should keep them with care
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Bulk deleting files with a pattern in file connector

2016-10-16 Thread Vivekananthan Sivanayagam

Hi ,

The existing connector does not have this option to delete. It deletes only
a single file or given folder, can not work for the pattern at the moment.

Vivekananthan Sivanayagam
Associate Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Sun, Oct 16, 2016 at 5:36 PM, Shazni Nazeer <sha...@wso2.com> wrote:

> Hi all,
>
> Just double checking, if there's a way to bulk delete files using the file
> connector. I tried different options but wasn't able to do this.
>
> e.g: Given a pattern, Cal_*.xml, should delete Cal_1.xml, Cal_test.xml etc
>
> Do you guys know a way to achieve above using the file connector?
>
> If not, wouldn't this be a useful improvement for the file-connector [1]
>
> [1] https://docs.wso2.com/display/ESBCONNECTORS/Working+
> with+the+File+Connector+Version+2
>
> regards,
>
> Shazni Nazeer
> Associate Technical Lead | WSO2
>
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
> Blog : http://shazninazeer.blogspot.com
>
> <http://wso2.com/signature>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Developer Studio/file connector isFileExist method doesn't allow to save the proxy

2016-09-26 Thread Vivekananthan Sivanayagam

Hi Shazni ,

I have updated the store with a fixed connector, you can find here [1].

[1]
https://storepreview.wso2.com/store/assets/esbconnector/aec1554a-29ea-4dbb-b8c5-5d529a853aa2

Vivekananthan Sivanayagam
Associate Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Mon, Sep 26, 2016 at 4:33 PM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Hi Shazni
>  
> ,
>
> I am looking on that.
>
> Thanks,
>
> Vivekananthan Sivanayagam
> Associate Software Engineer | WSO2
> E:vivekanant...@wso2.com
> M:+94752786138
>
> On Mon, Sep 26, 2016 at 3:29 PM, Shazni Nazeer <sha...@wso2.com> wrote:
>
>> Hi,
>>
>> I'm trying to import fileconnector (version 2.0.2) into developer studio.
>> I have a proxy in the ESB config project and it uses the fileconnector.
>>
>> I'm using the isFileExist call to check the whether the file being
>> requested exist and return File Not Found error to the caller.
>>
>> The proxy can't be saved in the devloper studio as it doesn't recognize
>> the is*F*ileExist. But it does recognize is*f*ileExist (Note the
>> lowercase and uppercase 'f' character). But is*f*ileExist doesn't work
>> in the connector it self. When called throwing the error [1]
>>
>> Looks like connector list also shows the method is "isfileExist" but the
>> internal implementation expects it to be isFileExist.
>>
>> [1] ERROR - InvokeMediator Sequence template
>> org.wso2.carbon.connector.fileconnector.isfileExist cannot be found
>>
>>
>> Shazni Nazeer
>> Associate Technical Lead | WSO2
>>
>> Mob : +94 37331
>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>> Blog : http://shazninazeer.blogspot.com
>>
>> <http://wso2.com/signature>
>>
>> ___
>> 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] Developer Studio/file connector isFileExist method doesn't allow to save the proxy

2016-09-26 Thread Vivekananthan Sivanayagam

Hi Shazni
 
,

I am looking on that.

Thanks,

Vivekananthan Sivanayagam
Associate Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Mon, Sep 26, 2016 at 3:29 PM, Shazni Nazeer <sha...@wso2.com> wrote:

> Hi,
>
> I'm trying to import fileconnector (version 2.0.2) into developer studio.
> I have a proxy in the ESB config project and it uses the fileconnector.
>
> I'm using the isFileExist call to check the whether the file being
> requested exist and return File Not Found error to the caller.
>
> The proxy can't be saved in the devloper studio as it doesn't recognize
> the is*F*ileExist. But it does recognize is*f*ileExist (Note the
> lowercase and uppercase 'f' character). But is*f*ileExist doesn't work in
> the connector it self. When called throwing the error [1]
>
> Looks like connector list also shows the method is "isfileExist" but the
> internal implementation expects it to be isFileExist.
>
> [1] ERROR - InvokeMediator Sequence template 
> org.wso2.carbon.connector.fileconnector.isfileExist
> cannot be found
>
>
> Shazni Nazeer
> Associate Technical Lead | WSO2
>
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
> Blog : http://shazninazeer.blogspot.com
>
> <http://wso2.com/signature>
>
> ___
> 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] wso2-extensions contribution..

2016-08-04 Thread Vivekananthan Sivanayagam

Hi Malaka,

There is another method "readResponseHTTPS" , we may need to modify that
method also as Kim has improved using the same concept.

Shall we do the improvement?




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Thu, Aug 4, 2016 at 8:42 PM, Malaka Silva <mal...@wso2.com> wrote:

> Hi Kim,
>
> Thank you for your contribution.
>
> On Thu, Aug 4, 2016 at 6:49 PM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> Hi ,
>>
>> We have reviewed and merged.
>>
>>
>>
>>
>> *Thank youVivekananthan Sivanayagam*
>>
>> *Associate Software Engineer | WSO2*
>>
>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>> *M:+94752786138 <%2B94752786138>*
>>
>> On Thu, Aug 4, 2016 at 3:12 PM, Vivekananthan Sivanayagam <
>> vivekanant...@wso2.com> wrote:
>>
>>> Hi Malaka,
>>>
>>> Noted.
>>>
>>>
>>>
>>>
>>> *Thank youVivekananthan Sivanayagam*
>>>
>>> *Associate Software Engineer | WSO2*
>>>
>>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>>> *M:+94752786138 <%2B94752786138>*
>>>
>>> On Thu, Aug 4, 2016 at 2:49 PM, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> Thx for the information Kim.
>>>>
>>>> @Vivekananthan - Can we check this and merge?
>>>>
>>>> On Thu, Aug 4, 2016 at 1:54 PM, 김대경 <dkg@gmail.com> wrote:
>>>>
>>>>> Hi Silva,
>>>>>
>>>>> I sent all information about improvement by email before...
>>>>>
>>>>> Did you mean..
>>>>> create issue in wso2 jira?
>>>>>
>>>>> Code change is about 6 line.
>>>>> I think this is so simple change..
>>>>>
>>>>> What should I do..?
>>>>>
>>>>>  sent before ===
>>>>> Hi Silva.
>>>>>
>>>>> This is about Pull request.
>>>>> https://github.com/wso2-extensions/esb-integration-base/pull/3
>>>>>
>>>>> In other language in UTF-8 like ko_KR.UTF-8, one char is not 4 byte.
>>>>>
>>>>> So, split response stream by 1024 byte may cause split one character..
>>>>>
>>>>> For example assume that '한글's bit is '010100110111'  and it is located
>>>>> on 1024th byte.
>>>>>
>>>>> Then, current code will split it into xxx~xxx01010011 and
>>>>> 0111xxx~xxx.
>>>>> And then it will be casted to string by new String(byte[]).
>>>>> In this case '한글' will be converted to similarly '한�'.
>>>>>
>>>>> I improved this case by read response stream by BufferedReader and
>>>>> char array.
>>>>>
>>>>> Please check the code, I commited.
>>>>>
>>>>> Sincerely.
>>>>>
>>>>> 2016. 8. 4. 오후 5:12에 "Malaka Silva" <mal...@wso2.com>님이 작성:
>>>>>
>>>>> Hi Kim,
>>>>>>
>>>>>> Please send us more details about the improvement and will check and
>>>>>> merge the request.
>>>>>>
>>>>>> Find more information in [1]
>>>>>>
>>>>>> [1] https://docs.wso2.com/display/ESBCONNECTORS/
>>>>>> Creating+a+Third+Party+Connector+and+Publishing+in+WSO2+Store
>>>>>>
>>>>>> -- Forwarded message --
>>>>>> From: 김대경 <dkg@gmail.com>
>>>>>> Date: Wed, Aug 3, 2016 at 1:21 PM
>>>>>> Subject: wso2-extensions contribution..
>>>>>> To: malaka.si...@gmail.com
>>>>>>
>>>>>>
>>>>>> Dear Silva.
>>>>>>
>>>>>> Thank you for read this mail.
>>>>>>
>>>>>> I'm writing to inquire about github contribution..
>>>>>>
>>>>>> I'm testing wso2 esb's functionalites.
>>>>>>
>>>>>> While.. I found a little improvement.
>>>>>>
>>>>>> So I recently created pull request to wso2-extensions/esb-
>>>>>> integration-base.
>>>>>>
>>>>>> But.. I think n

Re: [Dev] wso2-extensions contribution..

2016-08-04 Thread Vivekananthan Sivanayagam

Hi ,

We have reviewed and merged.




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Thu, Aug 4, 2016 at 3:12 PM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Hi Malaka,
>
> Noted.
>
>
>
>
> *Thank youVivekananthan Sivanayagam*
>
> *Associate Software Engineer | WSO2*
>
> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
> *M:+94752786138 <%2B94752786138>*
>
> On Thu, Aug 4, 2016 at 2:49 PM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Thx for the information Kim.
>>
>> @Vivekananthan - Can we check this and merge?
>>
>> On Thu, Aug 4, 2016 at 1:54 PM, 김대경 <dkg@gmail.com> wrote:
>>
>>> Hi Silva,
>>>
>>> I sent all information about improvement by email before...
>>>
>>> Did you mean..
>>> create issue in wso2 jira?
>>>
>>> Code change is about 6 line.
>>> I think this is so simple change..
>>>
>>> What should I do..?
>>>
>>>  sent before ===
>>> Hi Silva.
>>>
>>> This is about Pull request.
>>> https://github.com/wso2-extensions/esb-integration-base/pull/3
>>>
>>> In other language in UTF-8 like ko_KR.UTF-8, one char is not 4 byte.
>>>
>>> So, split response stream by 1024 byte may cause split one character..
>>>
>>> For example assume that '한글's bit is '010100110111'  and it is located
>>> on 1024th byte.
>>>
>>> Then, current code will split it into xxx~xxx01010011 and
>>> 0111xxx~xxx.
>>> And then it will be casted to string by new String(byte[]).
>>> In this case '한글' will be converted to similarly '한�'.
>>>
>>> I improved this case by read response stream by BufferedReader and char
>>> array.
>>>
>>> Please check the code, I commited.
>>>
>>> Sincerely.
>>>
>>> 2016. 8. 4. 오후 5:12에 "Malaka Silva" <mal...@wso2.com>님이 작성:
>>>
>>> Hi Kim,
>>>>
>>>> Please send us more details about the improvement and will check and
>>>> merge the request.
>>>>
>>>> Find more information in [1]
>>>>
>>>> [1]
>>>> https://docs.wso2.com/display/ESBCONNECTORS/Creating+a+Third+Party+Connector+and+Publishing+in+WSO2+Store
>>>>
>>>> -- Forwarded message --
>>>> From: 김대경 <dkg@gmail.com>
>>>> Date: Wed, Aug 3, 2016 at 1:21 PM
>>>> Subject: wso2-extensions contribution..
>>>> To: malaka.si...@gmail.com
>>>>
>>>>
>>>> Dear Silva.
>>>>
>>>> Thank you for read this mail.
>>>>
>>>> I'm writing to inquire about github contribution..
>>>>
>>>> I'm testing wso2 esb's functionalites.
>>>>
>>>> While.. I found a little improvement.
>>>>
>>>> So I recently created pull request to
>>>> wso2-extensions/esb-integration-base.
>>>>
>>>> But.. I think no one see this request.
>>>>
>>>> How  I can resolve this problem?
>>>>
>>>> I want this improvement could be applied next release.
>>>>
>>>> I look forward to hearing from you.
>>>>
>>>> Sincerely.
>>>> from Daekyung Kim.
>>>>
>>>> On Thu, Aug 4, 2016 at 7:04 AM, Malaka Silva <malaka.si...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Kim,
>>>>>
>>>>> Please send us more details about the imporvement and will check and
>>>>> merge the request.
>>>>>
>>>>> Find more information in [1]
>>>>>
>>>>> [1]
>>>>> https://docs.wso2.com/display/ESBCONNECTORS/Creating+a+Third+Party+Connector+and+Publishing+in+WSO2+Store
>>>>>
>>>>> -- Forwarded message --
>>>>> From: 김대경 <dkg@gmail.com>
>>>>> Date: Wed, Aug 3, 2016 at 1:21 PM
>>>>> Subject: wso2-extensions contribution..
>>>>> To: malaka.si...@gmail.com
>>>>>
>>>>>
>>>>> Dear Silva.
>>>>>
>>>>> Thank you for read this mail.
>>>>>
>>>>> I'm writing to inquire about github contribution..
>>>>>
>>>>> I'm

Re: [Dev] wso2-extensions contribution..

2016-08-04 Thread Vivekananthan Sivanayagam

Hi Malaka,

Noted.




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com *
*M:+94752786138*

On Thu, Aug 4, 2016 at 2:49 PM, Malaka Silva  wrote:

> Thx for the information Kim.
>
> @Vivekananthan - Can we check this and merge?
>
> On Thu, Aug 4, 2016 at 1:54 PM, 김대경  wrote:
>
>> Hi Silva,
>>
>> I sent all information about improvement by email before...
>>
>> Did you mean..
>> create issue in wso2 jira?
>>
>> Code change is about 6 line.
>> I think this is so simple change..
>>
>> What should I do..?
>>
>>  sent before ===
>> Hi Silva.
>>
>> This is about Pull request.
>> https://github.com/wso2-extensions/esb-integration-base/pull/3
>>
>> In other language in UTF-8 like ko_KR.UTF-8, one char is not 4 byte.
>>
>> So, split response stream by 1024 byte may cause split one character..
>>
>> For example assume that '한글's bit is '010100110111'  and it is located on
>> 1024th byte.
>>
>> Then, current code will split it into xxx~xxx01010011 and 0111xxx~xxx.
>> And then it will be casted to string by new String(byte[]).
>> In this case '한글' will be converted to similarly '한�'.
>>
>> I improved this case by read response stream by BufferedReader and char
>> array.
>>
>> Please check the code, I commited.
>>
>> Sincerely.
>>
>> 2016. 8. 4. 오후 5:12에 "Malaka Silva" 님이 작성:
>>
>> Hi Kim,
>>>
>>> Please send us more details about the improvement and will check and
>>> merge the request.
>>>
>>> Find more information in [1]
>>>
>>> [1]
>>> https://docs.wso2.com/display/ESBCONNECTORS/Creating+a+Third+Party+Connector+and+Publishing+in+WSO2+Store
>>>
>>> -- Forwarded message --
>>> From: 김대경 
>>> Date: Wed, Aug 3, 2016 at 1:21 PM
>>> Subject: wso2-extensions contribution..
>>> To: malaka.si...@gmail.com
>>>
>>>
>>> Dear Silva.
>>>
>>> Thank you for read this mail.
>>>
>>> I'm writing to inquire about github contribution..
>>>
>>> I'm testing wso2 esb's functionalites.
>>>
>>> While.. I found a little improvement.
>>>
>>> So I recently created pull request to
>>> wso2-extensions/esb-integration-base.
>>>
>>> But.. I think no one see this request.
>>>
>>> How  I can resolve this problem?
>>>
>>> I want this improvement could be applied next release.
>>>
>>> I look forward to hearing from you.
>>>
>>> Sincerely.
>>> from Daekyung Kim.
>>>
>>> On Thu, Aug 4, 2016 at 7:04 AM, Malaka Silva 
>>> wrote:
>>>
 Hi Kim,

 Please send us more details about the imporvement and will check and
 merge the request.

 Find more information in [1]

 [1]
 https://docs.wso2.com/display/ESBCONNECTORS/Creating+a+Third+Party+Connector+and+Publishing+in+WSO2+Store

 -- Forwarded message --
 From: 김대경 
 Date: Wed, Aug 3, 2016 at 1:21 PM
 Subject: wso2-extensions contribution..
 To: malaka.si...@gmail.com


 Dear Silva.

 Thank you for read this mail.

 I'm writing to inquire about github contribution..

 I'm testing wso2 esb's functionalites.

 While.. I found a little improvement.

 So I recently created pull request to
 wso2-extensions/esb-integration-base.

 But.. I think no one see this request.

 How  I can resolve this problem?

 I want this improvement could be applied next release.

 I look forward to hearing from you.

 Sincerely.
 from Daekyung Kim.


>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>> Malaka Silva
>>> Senior Technical Lead
>>> M: +94 777 219 791
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>> Skype : malaka.sampath.silva
>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>> Blog : http://mrmalakasilva.blogspot.com/
>>>
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> https://wso2.com/signature
>>> http://www.wso2.com/about/team/malaka-silva/
>>> 
>>> https://store.wso2.com/store/
>>>
>>> Don't make Trees rare, we should keep them with care
>>>
>>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Technical Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> https://wso2.com/signature
> http://www.wso2.com/about/team/malaka-silva/
> 
> https://store.wso2.com/store/
>
> Don't make Trees rare, we should keep them with care
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PET] [ESB] Empty body in response causes error with ESB 5.0.0-BETA

2016-06-22 Thread Vivekananthan Sivanayagam

Hi,

I am also getting the same error while running integration test for
outlookMail connector. please find the log in [1].

[1]

[2016-06-22 11:25:14,837]  INFO
{org.wso2.carbon.automation.core.PlatformTestManager} -  Running the test
method ---
org.wso2.carbon.connector.integration.test.outlookmail.OutLookMailConnectorIntegrationTest.testGetFolderWithNegativeCase

[2016-06-22 11:25:14,869]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,869] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
"POST /services/outlookmail HTTP/1.1[\r][\n]"
[2016-06-22 11:25:14,869]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,869] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
"Action: urn:getFolder[\r][\n]"
[2016-06-22 11:25:14,869]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,869] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
"Accept-Charset: UTF-8[\r][\n]"
[2016-06-22 11:25:14,869]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,869] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
"Accept: application/json[\r][\n]"
[2016-06-22 11:25:14,870]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,869] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
"Content-Type: application/json[\r][\n]"
[2016-06-22 11:25:14,870]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,870] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
"User-Agent: Java/1.7.0_79[\r][\n]"
[2016-06-22 11:25:14,870]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,870] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
"Host: localhost:8280[\r][\n]"
[2016-06-22 11:25:14,870]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,870] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
"Connection: keep-alive[\r][\n]"
[2016-06-22 11:25:14,870]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,870] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
"Content-Length: 1068[\r][\n]"
[2016-06-22 11:25:14,870]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,870] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
"[\r][\n]"
[2016-06-22 11:25:14,870]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,870] DEBUG - wire HTTP-Listener I/O dispatcher-1 >>
"{[\n]"
[2016-06-22 11:25:14,870]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,870] DEBUG - wire HTTP-Listener I/O dispatcher-1 >> "
 "apiUrl":"https://outlook.office.com/api",[\n];
[2016-06-22 11:25:14,871]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,871] DEBUG - wire HTTP-Listener I/O dispatcher-1 >> "
 
"refreshToken":"AAABiL9Kn2Z27UubvWFPbm0gLY_U_UGIN46r7zSSoqXcjmlZ_TjD8u_NSBxtEfBf2hya6XKqTuqMh9UO2DN72KK7wy4dUmKfOgFjJHS9Mc7drpqhfdMfdXTLs-Np_3yf0SXRzBg5m2ZA8Lx14pfq44IIugJepF5VQCrqZkA4AXqjoofIsKMI5x_yrx9STeWJDavLlErlHlFRzpJiO-JQYIVZG-z_vcuwjtZ1C4C-k42erDgeffSJA_SvFVAaTyLOgzFPnDEvYCLz5uIekaCQ9_xdsuORl76x0gVHEvQ3fyyeGDudPD6AHXiXQ3jIC3t6TPIAuszR3ut_8tf4Sn9d3eHbGKeLQe8S-oUko_aZGdtX_eDAR4o0YfLlluQr4WMKyl-6pKzplC9tZigxH1M6MXkfDubT6D8-GYDhSbfgH7oK_TGAJKkoiWcwS0gUpQ9_HpCpUJgpe6c-9nzjdaMIF_EBrZzVdKio3smKM4RMMV4T1cGR6Ev4zdvNE3PWAQzLjq8gX8D3qzm--NV97yFbA04TqENmNAg-wc4iT5P4Y06vhHrpXFHc9-zg1qzBNhUSXmFkTKhGiPhv3_QnGWerGgW1CTGdUnPAkA5KyWoGB4G5MN7EB0n5hzQ90OpNkrFxziIRs1_69poJtSETPXsd7cW0GI1TwNnAOuGD9fzEtsmW9TkgAA",[\n]"
[2016-06-22 11:25:14,871]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,871] DEBUG - wire HTTP-Listener I/O dispatcher-1 >> "
 "clientSecret":"w5BaTTc9FqpcUVvIhRhFkRQTVNN2YLWf+mwj3Mh86aI=",[\n]"
[2016-06-22 11:25:14,871]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,871] DEBUG - wire HTTP-Listener I/O dispatcher-1 >> "
 "clientId":"D42620b8-6d8a-47cb-843d-e798f193535f",[\n]"
[2016-06-22 11:25:14,871]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,871] DEBUG - wire HTTP-Listener I/O dispatcher-1 >> "
 "resource":"https://outlook.office.com/",[\n];
[2016-06-22 11:25:14,871]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,871] DEBUG - wire HTTP-Listener I/O dispatcher-1 >> "
 "redirectUri":"https://www.vive.viveSL.onmicrosoft.com",[\n];
[2016-06-22 11:25:14,871]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-22 11:25:14,871] DEBUG - wire HTTP-Listener I/O dispatcher-1 >> "
 "registryPath":"",[\n]"
[2016-06-22 11:25:14,871]  INFO

Re: [Dev] [DEV] Need to know and contribute

2016-06-18 Thread Vivekananthan Sivanayagam

Hi Mayuran,

Nice to hear that you guys like to contribute to our ESB connector store.
You can also refer Creating a Third Party Connector[1].

@Malaka
Shall we suggest a connector ?

[1]
https://docs.wso2.com/display/ESBCONNECTORS/Creating+a+Third+Party+Connector+and+Publishing+in+WSO2+Store

Refer following links for more details of creating the new connector.

[2] https://docs.wso2.com/display/ESBCONNECTORS/Writing+a+Connector
[3] http://wso2.com/library/articles/2014/02/how-to-write-a-esb-connector/







*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com *
*M:+94752786138*

On Tue, Jun 14, 2016 at 12:16 AM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:

> Hi Mayuran,
>
> Really nice to hear about your interest in WSO2. You will get some idea
> about connectors[1] and WSO2-ESB[2].  You may getting help from your
> seniors since they were already did this.
>
> [1] - https://docs.wso2.com/display/ESBCONNECTORS/WSO2+ESB+Connectors
> [2] -
> https://docs.wso2.com/display/ESB490/WSO2+Enterprise+Service+Bus+Documentation
>
> On Tue, Jun 14, 2016 at 12:08 AM, Tharmalingam Mayuran <
> tmayura...@gmail.com> wrote:
>
>> Hi All,
>>
>> I'm Mayuran doing computer science at Department of Computer Science,
>> University of Jaffna. I was participate the Jaffna meetup last month. I got
>> some idea about How to contribute to WSO2 and about WSO2 extensions and
>> their usages. I would like to contribute to WSO2(wso2-extension). Some of
>> my colleagues were already done this and some are working on this. Could
>> you please share some useful documentation to understand the basic about
>> ESB and wso2-extension. I and my friend would like to create an
>> ESB-Connector. Can anyone suggest a useful connector as well to create?
>>
>> Thanks and Regards
>> Mayuran T
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
>
> *Thank you and Regards**Hariprasath Thanarajah*
> Associate Software Engineer | WSO2
> E: haripras...@wso2.com
> M: +94752806528, 0777216903
>
>
> ___
> 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] Deprecating File Connector V1

2016-05-30 Thread Vivekananthan Sivanayagam

+ dev

File Connector V1 has been deprecated.






*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Mon, May 30, 2016 at 12:21 PM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> +1
>
>
>
>
> *Thank youVivekananthan Sivanayagam*
>
> *Associate Software Engineer | WSO2*
>
> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
> *M:+94752786138 <%2B94752786138>*
>
> On Mon, May 30, 2016 at 12:18 PM, Yashothara Shanmugarajah <
> yashoth...@wso2.com> wrote:
>
>> Yep. +1
>>
>> Best Regards,
>> Yashothara.S
>>
>> Software Engineer
>> WSO2
>>
>>
>> On Mon, May 30, 2016 at 12:16 PM, Malaka Silva <mal...@wso2.com> wrote:
>>
>>> Shall we deprecate v1 since we have released v2 with all functions?
>>>
>>> On Mon, May 23, 2016 at 8:55 AM, Yashothara Shanmugarajah <
>>> yashoth...@wso2.com> wrote:
>>>
>>>> Yep. I have profiled the memory and it is same as ESB profiling.
>>>>
>>>> Best Regards,
>>>> Yashothara.S
>>>>
>>>> Software Engineer
>>>> WSO2
>>>>
>>>>
>>>> On Mon, May 23, 2016 at 8:53 AM, Malaka Silva <mal...@wso2.com> wrote:
>>>>
>>>>> Did we profile the memory while doing this?
>>>>>
>>>>> On Mon, May 23, 2016 at 8:49 AM, Yashothara Shanmugarajah <
>>>>> yashoth...@wso2.com> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I have completed the adding streaming feature to file read method in
>>>>>> File connector version 2. It works fine until 1 Gb as ESB.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> Best Regards,
>>>>>> Yashothara.S
>>>>>>
>>>>>> Software Engineer
>>>>>> WSO2
>>>>>>
>>>>>>
>>>>>> On Wed, May 4, 2016 at 10:40 AM, Vivekananthan Sivanayagam <
>>>>>> vivekanant...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi ,
>>>>>>>
>>>>>>> The method FileRename includes in file connector version 1, but not
>>>>>>> in a version 2. We can do this using FileMove operation. We can 
>>>>>>> deprecate
>>>>>>> V1.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *Thank youVivekananthan Sivanayagam*
>>>>>>>
>>>>>>> *Associate Software Engineer | WSO2*
>>>>>>>
>>>>>>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>>>>>>> *M:+94752786138 <%2B94752786138>*
>>>>>>>
>>>>>>> On Wed, May 4, 2016 at 9:18 AM, Yashothara Shanmugarajah <
>>>>>>> yashoth...@wso2.com> wrote:
>>>>>>>
>>>>>>>> We can add streaming parameter to read operation in version 2.
>>>>>>>>
>>>>>>>> Best Regards,
>>>>>>>> Yashothara.S
>>>>>>>>
>>>>>>>> Software Engineer
>>>>>>>> WSO2
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, May 4, 2016 at 9:11 AM, Malaka Silva <mal...@wso2.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Yashothara yes you are correct. Best is we incorporate streaming
>>>>>>>>> to read operation with the new sender operation (you are already 
>>>>>>>>> writing)
>>>>>>>>> then deprecate V1.
>>>>>>>>>
>>>>>>>>> Any other use cases?
>>>>>>>>>
>>>>>>>>> On Wed, May 4, 2016 at 9:01 AM, Yashothara Shanmugarajah <
>>>>>>>>> yashoth...@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> In file connector Version 2, there is no streaming parameter in
>>>>>>>>>> file read method. But in version 1 it has. Is it ok?
>>>>>>>>>>
>>>>>>>>>> Best Regards,
>>>&g

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

2016-05-25 Thread Vivekananthan Sivanayagam

Hi Malaka,

LDAP Connector is released and published in store [1].

[1]
https://store.wso2.com/store/assets/esbconnector/6e86496f-431e-43e2-bded-caedd10c4cb9




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Wed, May 25, 2016 at 8:42 AM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Noted.
>
>
>
>
> *Thank youVivekananthan Sivanayagam*
>
> *Associate Software Engineer | WSO2*
>
> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
> *M:+94752786138 <%2B94752786138>*
>
> On Wed, May 25, 2016 at 5:37 AM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Please proceed and release.
>>
>> On Tue, May 24, 2016 at 6:21 PM, Vivekananthan Sivanayagam <
>> vivekanant...@wso2.com> wrote:
>>
>>> Hi Malaka,
>>>
>>> Yes, We can release after fixed.
>>>
>>>
>>>
>>>
>>> *Thank youVivekananthan Sivanayagam*
>>>
>>> *Associate Software Engineer | WSO2*
>>>
>>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>>> *M:+94752786138 <%2B94752786138>*
>>>
>>> On Tue, May 24, 2016 at 3:44 PM, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> Can we fix those and release please?
>>>>
>>>> On Tue, May 24, 2016 at 2:32 PM, Vivekananthan Sivanayagam <
>>>> vivekanant...@wso2.com> wrote:
>>>>
>>>>> Hi Malaka,
>>>>>
>>>>> I have tested LDAP Connector with those changes, It is working fine ,
>>>>> but there is a problem when run the test cases because all the test case
>>>>> methods are skipped but it gets build success.
>>>>>
>>>>> Error is "Caused by: java.io.FileNotFoundException:
>>>>> /home/vive/Downloads/ldap/esb-connector-ldap/target/ldap-connector-1.0.1-SNAPSHOT.zip
>>>>> (No such file or directory)".
>>>>>
>>>>> There are few changes in pom file [1] that's why test cases are
>>>>> getting skipped .
>>>>>
>>>>> [1]
>>>>> https://github.com/wso2-extensions/esb-connector-ldap/pull/3/files#diff-600376dffeb79835ede4a0b285078036R195
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *Thank youVivekananthan Sivanayagam*
>>>>>
>>>>> *Associate Software Engineer | WSO2*
>>>>>
>>>>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>>>>> *M:+94752786138 <%2B94752786138>*
>>>>>
>>>>> On Wed, May 18, 2016 at 8:36 PM, Vivekananthan Sivanayagam <
>>>>> vivekanant...@wso2.com> wrote:
>>>>>
>>>>>> Hi willian Antunes,
>>>>>>
>>>>>> Thank you for more details, I am looking on that.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> *Thank youVivekananthan Sivanayagam*
>>>>>>
>>>>>> *Associate Software Engineer | WSO2*
>>>>>>
>>>>>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>>>>>> *M:+94752786138 <%2B94752786138>*
>>>>>>
>>>>>> On Wed, May 18, 2016 at 7:53 PM, Willian Antunes <
>>>>>> willian.lima.antu...@gmail.com> wrote:
>>>>>>
>>>>>>> By the way I believe we could talk directly from the LDAP Connector
>>>>>>> JIRA issue <https://wso2.org/jira/browse/ESBCONNECT-92> instead
>>>>>>> from here or use the pull request that I requested from GitHub
>>>>>>> <https://github.com/wso2-extensions/esb-connector-ldap/pull/3>, so
>>>>>>> we can keep the history of it from one place.
>>>>>>>
>>>>>>> On Wed, May 18, 2016 at 1:41 PM, Willian Antunes <
>>>>>>> willian.lima.antu...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Vivekananthan,
>>>>>>>>
>>>>>>>> Did you see what happened during the communication process? If
>>>>>>>> didn't try to install an sniffer like Wireshark to understand which 
>>>>>>>> error
>>>>>>>> the LDAP server sent to you.
>>>>>>>>
>>>>>&g

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

2016-05-24 Thread Vivekananthan Sivanayagam

Noted.




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Wed, May 25, 2016 at 5:37 AM, Malaka Silva <mal...@wso2.com> wrote:

> Please proceed and release.
>
> On Tue, May 24, 2016 at 6:21 PM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> Hi Malaka,
>>
>> Yes, We can release after fixed.
>>
>>
>>
>>
>> *Thank youVivekananthan Sivanayagam*
>>
>> *Associate Software Engineer | WSO2*
>>
>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>> *M:+94752786138 <%2B94752786138>*
>>
>> On Tue, May 24, 2016 at 3:44 PM, Malaka Silva <mal...@wso2.com> wrote:
>>
>>> Can we fix those and release please?
>>>
>>> On Tue, May 24, 2016 at 2:32 PM, Vivekananthan Sivanayagam <
>>> vivekanant...@wso2.com> wrote:
>>>
>>>> Hi Malaka,
>>>>
>>>> I have tested LDAP Connector with those changes, It is working fine ,
>>>> but there is a problem when run the test cases because all the test case
>>>> methods are skipped but it gets build success.
>>>>
>>>> Error is "Caused by: java.io.FileNotFoundException:
>>>> /home/vive/Downloads/ldap/esb-connector-ldap/target/ldap-connector-1.0.1-SNAPSHOT.zip
>>>> (No such file or directory)".
>>>>
>>>> There are few changes in pom file [1] that's why test cases are getting
>>>> skipped .
>>>>
>>>> [1]
>>>> https://github.com/wso2-extensions/esb-connector-ldap/pull/3/files#diff-600376dffeb79835ede4a0b285078036R195
>>>>
>>>>
>>>>
>>>>
>>>> *Thank youVivekananthan Sivanayagam*
>>>>
>>>> *Associate Software Engineer | WSO2*
>>>>
>>>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>>>> *M:+94752786138 <%2B94752786138>*
>>>>
>>>> On Wed, May 18, 2016 at 8:36 PM, Vivekananthan Sivanayagam <
>>>> vivekanant...@wso2.com> wrote:
>>>>
>>>>> Hi willian Antunes,
>>>>>
>>>>> Thank you for more details, I am looking on that.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *Thank youVivekananthan Sivanayagam*
>>>>>
>>>>> *Associate Software Engineer | WSO2*
>>>>>
>>>>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>>>>> *M:+94752786138 <%2B94752786138>*
>>>>>
>>>>> On Wed, May 18, 2016 at 7:53 PM, Willian Antunes <
>>>>> willian.lima.antu...@gmail.com> wrote:
>>>>>
>>>>>> By the way I believe we could talk directly from the LDAP Connector
>>>>>> JIRA issue <https://wso2.org/jira/browse/ESBCONNECT-92> instead from
>>>>>> here or use the pull request that I requested from GitHub
>>>>>> <https://github.com/wso2-extensions/esb-connector-ldap/pull/3>, so
>>>>>> we can keep the history of it from one place.
>>>>>>
>>>>>> On Wed, May 18, 2016 at 1:41 PM, Willian Antunes <
>>>>>> willian.lima.antu...@gmail.com> wrote:
>>>>>>
>>>>>>> Vivekananthan,
>>>>>>>
>>>>>>> Did you see what happened during the communication process? If
>>>>>>> didn't try to install an sniffer like Wireshark to understand which 
>>>>>>> error
>>>>>>> the LDAP server sent to you.
>>>>>>>
>>>>>>> There are two scenarios which you can use to test:
>>>>>>>
>>>>>>> 1 - Set *secureConnection* and *disableSSLCertificateChecking both
>>>>>>> as true* in order to use a SSL port and ignore the certificate
>>>>>>> provided by the LDAP server.
>>>>>>> 2 - Set *secureConnection* *as* *true* and 
>>>>>>> *disableSSLCertificateChecking
>>>>>>> as* *false* in order to use a SSL port and to validate the
>>>>>>> certificate provided by the LDAP server. You have to make sure you have 
>>>>>>> the
>>>>>>> ROOT CA was imported in your OS which was used to sign the LDAP
>>>>>>> certificate, if you don't then the connec

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

2016-05-24 Thread Vivekananthan Sivanayagam

Hi Malaka,

Yes, We can release after fixed.




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Tue, May 24, 2016 at 3:44 PM, Malaka Silva <mal...@wso2.com> wrote:

> Can we fix those and release please?
>
> On Tue, May 24, 2016 at 2:32 PM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> Hi Malaka,
>>
>> I have tested LDAP Connector with those changes, It is working fine , but
>> there is a problem when run the test cases because all the test case
>> methods are skipped but it gets build success.
>>
>> Error is "Caused by: java.io.FileNotFoundException:
>> /home/vive/Downloads/ldap/esb-connector-ldap/target/ldap-connector-1.0.1-SNAPSHOT.zip
>> (No such file or directory)".
>>
>> There are few changes in pom file [1] that's why test cases are getting
>> skipped .
>>
>> [1]
>> https://github.com/wso2-extensions/esb-connector-ldap/pull/3/files#diff-600376dffeb79835ede4a0b285078036R195
>>
>>
>>
>>
>> *Thank youVivekananthan Sivanayagam*
>>
>> *Associate Software Engineer | WSO2*
>>
>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>> *M:+94752786138 <%2B94752786138>*
>>
>> On Wed, May 18, 2016 at 8:36 PM, Vivekananthan Sivanayagam <
>> vivekanant...@wso2.com> wrote:
>>
>>> Hi willian Antunes,
>>>
>>> Thank you for more details, I am looking on that.
>>>
>>>
>>>
>>>
>>> *Thank youVivekananthan Sivanayagam*
>>>
>>> *Associate Software Engineer | WSO2*
>>>
>>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>>> *M:+94752786138 <%2B94752786138>*
>>>
>>> On Wed, May 18, 2016 at 7:53 PM, Willian Antunes <
>>> willian.lima.antu...@gmail.com> wrote:
>>>
>>>> By the way I believe we could talk directly from the LDAP Connector
>>>> JIRA issue <https://wso2.org/jira/browse/ESBCONNECT-92> instead from
>>>> here or use the pull request that I requested from GitHub
>>>> <https://github.com/wso2-extensions/esb-connector-ldap/pull/3>, so we
>>>> can keep the history of it from one place.
>>>>
>>>> On Wed, May 18, 2016 at 1:41 PM, Willian Antunes <
>>>> willian.lima.antu...@gmail.com> wrote:
>>>>
>>>>> Vivekananthan,
>>>>>
>>>>> Did you see what happened during the communication process? If didn't
>>>>> try to install an sniffer like Wireshark to understand which error the 
>>>>> LDAP
>>>>> server sent to you.
>>>>>
>>>>> There are two scenarios which you can use to test:
>>>>>
>>>>> 1 - Set *secureConnection* and *disableSSLCertificateChecking both as
>>>>> true* in order to use a SSL port and ignore the certificate provided
>>>>> by the LDAP server.
>>>>> 2 - Set *secureConnection* *as* *true* and *disableSSLCertificateChecking
>>>>> as* *false* in order to use a SSL port and to validate the
>>>>> certificate provided by the LDAP server. You have to make sure you have 
>>>>> the
>>>>> ROOT CA was imported in your OS which was used to sign the LDAP
>>>>> certificate, if you don't then the connection will fail. Try to use an
>>>>> sniffer to understand what is happening.
>>>>>
>>>>> Important: Does not make sense to configure secureConnection as false
>>>>> and disableSSLCertificateChecking as true because you're not using a 
>>>>> secure
>>>>> port like 636.
>>>>>
>>>>> If you have any doubt please contact me!
>>>>>
>>>>> Regards,
>>>>> Antunes
>>>>>
>>>>> On Wed, May 18, 2016 at 4:05 AM, Vivekananthan Sivanayagam <
>>>>> vivekanant...@wso2.com> wrote:
>>>>>
>>>>>> Hi Malaka,
>>>>>>
>>>>>> I am working on that and still I have a problem in configure LDAP
>>>>>> with SSL connection. Without SSL connection, the connector is working and
>>>>>> according to the his changes, the SearchEntry method is working
>>>>>> with onlyOneReference parameter. I need to check in SSL connection part.
>>>>>>
>>>>>> I configured in ubuntu and I cou

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

2016-05-24 Thread Vivekananthan Sivanayagam

Hi Malaka,

I have tested LDAP Connector with those changes, It is working fine , but
there is a problem when run the test cases because all the test case
methods are skipped but it gets build success.

Error is "Caused by: java.io.FileNotFoundException:
/home/vive/Downloads/ldap/esb-connector-ldap/target/ldap-connector-1.0.1-SNAPSHOT.zip
(No such file or directory)".

There are few changes in pom file [1] that's why test cases are getting
skipped .

[1]
https://github.com/wso2-extensions/esb-connector-ldap/pull/3/files#diff-600376dffeb79835ede4a0b285078036R195




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Wed, May 18, 2016 at 8:36 PM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Hi willian Antunes,
>
> Thank you for more details, I am looking on that.
>
>
>
>
> *Thank youVivekananthan Sivanayagam*
>
> *Associate Software Engineer | WSO2*
>
> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
> *M:+94752786138 <%2B94752786138>*
>
> On Wed, May 18, 2016 at 7:53 PM, Willian Antunes <
> willian.lima.antu...@gmail.com> wrote:
>
>> By the way I believe we could talk directly from the LDAP Connector JIRA
>> issue <https://wso2.org/jira/browse/ESBCONNECT-92> instead from here or
>> use the pull request that I requested from GitHub
>> <https://github.com/wso2-extensions/esb-connector-ldap/pull/3>, so we
>> can keep the history of it from one place.
>>
>> On Wed, May 18, 2016 at 1:41 PM, Willian Antunes <
>> willian.lima.antu...@gmail.com> wrote:
>>
>>> Vivekananthan,
>>>
>>> Did you see what happened during the communication process? If didn't
>>> try to install an sniffer like Wireshark to understand which error the LDAP
>>> server sent to you.
>>>
>>> There are two scenarios which you can use to test:
>>>
>>> 1 - Set *secureConnection* and *disableSSLCertificateChecking both as
>>> true* in order to use a SSL port and ignore the certificate provided by
>>> the LDAP server.
>>> 2 - Set *secureConnection* *as* *true* and *disableSSLCertificateChecking
>>> as* *false* in order to use a SSL port and to validate the certificate
>>> provided by the LDAP server. You have to make sure you have the ROOT CA was
>>> imported in your OS which was used to sign the LDAP certificate, if you
>>> don't then the connection will fail. Try to use an sniffer to understand
>>> what is happening.
>>>
>>> Important: Does not make sense to configure secureConnection as false
>>> and disableSSLCertificateChecking as true because you're not using a secure
>>> port like 636.
>>>
>>> If you have any doubt please contact me!
>>>
>>> Regards,
>>> Antunes
>>>
>>> On Wed, May 18, 2016 at 4:05 AM, Vivekananthan Sivanayagam <
>>> vivekanant...@wso2.com> wrote:
>>>
>>>> Hi Malaka,
>>>>
>>>> I am working on that and still I have a problem in configure LDAP with
>>>> SSL connection. Without SSL connection, the connector is working and
>>>> according to the his changes, the SearchEntry method is working
>>>> with onlyOneReference parameter. I need to check in SSL connection part.
>>>>
>>>> I configured in ubuntu and I could not connect LDAP over SSL
>>>> connection. When I configure with port 636,it shows "ldap_result: Can't
>>>> contact LDAP server (-1)" error.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *Thank youVivekananthan Sivanayagam*
>>>>
>>>> *Associate Software Engineer | WSO2*
>>>>
>>>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>>>> *M:+94752786138 <%2B94752786138>*
>>>>
>>>> On Wed, May 18, 2016 at 9:22 AM, Malaka Silva <mal...@wso2.com> wrote:
>>>>
>>>>> Hi Vivekananthan,
>>>>>
>>>>> Please update the progress please?
>>>>>
>>>>> Shakila went through some of the methods in this connector. The
>>>>> description for parameters are not added in all templates. This is not the
>>>>> standard that we followed so far.
>>>>>
>>>>> On Sat, May 7, 2016 at 3:26 PM, Rajjaz Mohammed <raj...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Willian,
>>>>>>
>>>>>&

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

2016-05-18 Thread Vivekananthan Sivanayagam

Hi willian Antunes,

Thank you for more details, I am looking on that.




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Wed, May 18, 2016 at 7:53 PM, Willian Antunes <
willian.lima.antu...@gmail.com> wrote:

> By the way I believe we could talk directly from the LDAP Connector JIRA
> issue <https://wso2.org/jira/browse/ESBCONNECT-92> instead from here or
> use the pull request that I requested from GitHub
> <https://github.com/wso2-extensions/esb-connector-ldap/pull/3>, so we can
> keep the history of it from one place.
>
> On Wed, May 18, 2016 at 1:41 PM, Willian Antunes <
> willian.lima.antu...@gmail.com> wrote:
>
>> Vivekananthan,
>>
>> Did you see what happened during the communication process? If didn't try
>> to install an sniffer like Wireshark to understand which error the LDAP
>> server sent to you.
>>
>> There are two scenarios which you can use to test:
>>
>> 1 - Set *secureConnection* and *disableSSLCertificateChecking both as
>> true* in order to use a SSL port and ignore the certificate provided by
>> the LDAP server.
>> 2 - Set *secureConnection* *as* *true* and *disableSSLCertificateChecking
>> as* *false* in order to use a SSL port and to validate the certificate
>> provided by the LDAP server. You have to make sure you have the ROOT CA was
>> imported in your OS which was used to sign the LDAP certificate, if you
>> don't then the connection will fail. Try to use an sniffer to understand
>> what is happening.
>>
>> Important: Does not make sense to configure secureConnection as false
>> and disableSSLCertificateChecking as true because you're not using a secure
>> port like 636.
>>
>> If you have any doubt please contact me!
>>
>> Regards,
>> Antunes
>>
>> On Wed, May 18, 2016 at 4:05 AM, Vivekananthan Sivanayagam <
>> vivekanant...@wso2.com> wrote:
>>
>>> Hi Malaka,
>>>
>>> I am working on that and still I have a problem in configure LDAP with
>>> SSL connection. Without SSL connection, the connector is working and
>>> according to the his changes, the SearchEntry method is working
>>> with onlyOneReference parameter. I need to check in SSL connection part.
>>>
>>> I configured in ubuntu and I could not connect LDAP over SSL connection.
>>> When I configure with port 636,it shows "ldap_result: Can't contact LDAP
>>> server (-1)" error.
>>>
>>>
>>>
>>>
>>>
>>> *Thank youVivekananthan Sivanayagam*
>>>
>>> *Associate Software Engineer | WSO2*
>>>
>>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>>> *M:+94752786138 <%2B94752786138>*
>>>
>>> On Wed, May 18, 2016 at 9:22 AM, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> Hi Vivekananthan,
>>>>
>>>> Please update the progress please?
>>>>
>>>> Shakila went through some of the methods in this connector. The
>>>> description for parameters are not added in all templates. This is not the
>>>> standard that we followed so far.
>>>>
>>>> On Sat, May 7, 2016 at 3:26 PM, Rajjaz Mohammed <raj...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Willian,
>>>>>
>>>>> Sorry for the missing headers. I edited the files from Developer
>>>>>> Studio, it erases the XML file to a new one every time you open it. So 
>>>>>> even
>>>>>> when a comment is inserted, the file will be erased again in the design
>>>>>> view.
>>>>>>
>>>>>
>>>>>
>>>>> I will look on that and update.
>>>>>
>>>>> --
>>>>> Thank you
>>>>> Best Regards
>>>>>
>>>>> *Rajjaz HM*
>>>>> Associate Software Engineer
>>>>> Platform Extension Team
>>>>> WSO2 Inc. <http://wso2.com/>
>>>>> lean | enterprise | middleware
>>>>> Mobile | +94752833834|+94777226874
>>>>> Email   | raj...@wso2.com
>>>>> LinkedIn <https://lk.linkedin.com/in/hmohammedrajjaz> | Blogger
>>>>> <http://wso2experience.blogspot.com/> | WSO2 Profile
>>>>> <http://wso2.com/about/team/mohammer-rajjaz/>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Best Regards,
>>>>
>>>> Malaka Silva
>>>> Senior Tech Lead
>>>> M: +94 777 219 791
>>>> Tel : 94 11 214 5345
>>>> Fax :94 11 2145300
>>>> Skype : malaka.sampath.silva
>>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>>> Blog : http://mrmalakasilva.blogspot.com/
>>>>
>>>> WSO2, Inc.
>>>> lean . enterprise . middleware
>>>> http://www.wso2.com/
>>>> http://www.wso2.com/about/team/malaka-silva/
>>>> <http://wso2.com/about/team/malaka-silva/>
>>>> https://store.wso2.com/store/
>>>>
>>>> Save a tree -Conserve nature & Save the world for your future. Print
>>>> this email only if it is absolutely necessary.
>>>>
>>>
>>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Representing a JSON payload with null values - visual datamapper editor

2016-05-18 Thread Vivekananthan Sivanayagam

Hi Sohani,

Normally we are getting null value for optional parameter in the API
response, suppose if we get the actual value for that json object , does
this schema handle that case?





*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com *
*M:+94752786138*

On Wed, May 18, 2016 at 11:19 AM, Sohani Weerasinghe 
wrote:

> Hi All,
>
> If a json payload has null values as shown below, how are we going to
> represent this in the json schema?
>
> {
>   "root": {
> "tasklist_id": "12345",
> "test"=null
> }
> }
>
> If we are serializing that value, then the generated schema and the tree
> view will be as follows
>
> {
>   "$schema" : "http://json-schema.org/draft-04/schema#;,
>   "id" : "http://wso2jsonschema.org;,
>   "title" : "root",
>   "type" : "object",
>   "properties" : {
> *"test" : {*
> *  "id" : "http://wso2jsonschema.org/test
> ",*
> *  "type" : "null"*
> *},*
> "tasklist_id" : {
>   "id" : "http://wso2jsonschema.org/tasklist_id;,
>   "type" : "string"
> }
>   }
> }
>
>
> 
>
> Appreciate your input on this
>
> Thanks,
> Sohani
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [ESB] [LDAP Connector] SSL connection (port 636)

2016-05-17 Thread Vivekananthan Sivanayagam

Hi Malaka,

I am working on that and still I have a problem in configure LDAP with SSL
connection. Without SSL connection, the connector is working and according
to the his changes, the SearchEntry method is working with onlyOneReference
parameter. I need to check in SSL connection part.

I configured in ubuntu and I could not connect LDAP over SSL connection.
When I configure with port 636,it shows "ldap_result: Can't contact LDAP
server (-1)" error.





*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com *
*M:+94752786138*

On Wed, May 18, 2016 at 9:22 AM, Malaka Silva  wrote:

> Hi Vivekananthan,
>
> Please update the progress please?
>
> Shakila went through some of the methods in this connector. The
> description for parameters are not added in all templates. This is not the
> standard that we followed so far.
>
> On Sat, May 7, 2016 at 3:26 PM, Rajjaz Mohammed  wrote:
>
>> Hi Willian,
>>
>> Sorry for the missing headers. I edited the files from Developer Studio,
>>> it erases the XML file to a new one every time you open it. So even when a
>>> comment is inserted, the file will be erased again in the design view.
>>>
>>
>>
>> I will look on that and update.
>>
>> --
>> Thank you
>> Best Regards
>>
>> *Rajjaz HM*
>> Associate Software Engineer
>> Platform Extension Team
>> WSO2 Inc. 
>> lean | enterprise | middleware
>> Mobile | +94752833834|+94777226874
>> Email   | raj...@wso2.com
>> LinkedIn  | Blogger
>>  | WSO2 Profile
>> 
>>
>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> 
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [PET] Unable to get access token from refresh token via ESB

2016-03-30 Thread Vivekananthan Sivanayagam

Hi Malaka / Kathess,

Thank you for your suggestion . Now it is working fine.





*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Wed, Mar 30, 2016 at 5:05 PM, Malaka Silva <mal...@wso2.com> wrote:

> Have you tried disabling chunking?
>
>  
>
> On Wed, Mar 30, 2016 at 4:23 PM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> Hi all,
>>
>> I am working with outlook Mail connector, I need to get access token from
>> refresh token . When I called API through the REST Client, It is working
>> but through the ESB , I am unable to get response. Please find the wire log
>> below.
>>
>> [1] REST Client wire log
>>
>> POST http://login.microsoftonline.com/common/oauth2/token
>> Content-Type: application/x-www-form-urlencoded
>>
>> grant_type=refresh_token_id=xxx_secret=_token=AAABiL9Kn2Z27UubvWFPbm0gLSj81wVdCkSsT_rqg9I-CpL5pD0Dyru4vEg5o0nZe7YxCtM24jHbA5pSATNPyypxVyWq8WWnxNeLTMX7SFMzdaD5k0_qohsn4jqCar2U1_LTSgvFyCfvQhVKTF9ugOXE7ST9wjRe7XDAFwU75kMQ3kG1WUTI4lhhCYqoDS_KPwPFWE4_ntj8IYZ1BPkjuMAx514yuVURdjEvOluobippPQCtjWAK5X8bMIC6bLEoWj3D8x4hCDL32NVFBUYLgCKK0uaCFR8ulZKpjMc-8OMG9iS1jCPsIkF8O7-0rUBwr3mHCxycId0FDJIUuu2bqR1RRp3pzyzj3K0UfAUcWnkSZDrkeysPf4RbyQcyMhgRSZdhn7KL-8jQBcHvo2aPvvYErDpG4NnpeMrX5Iuk2amhtVzJYFUi27gTDt1XaPZQskbrYOw_GydTaRWvl0j8RBeG4xRHtv-dVnsphdSR6EkB0LKIFD6kWt0EyUmk4ZEf9OwgzjmPsTh0nxPGw-h1X02vGK58AL3CMx-Ot1TTInQEMObklysuTjZb4YjVUUiSBX4mnF0YtS1sSyQHRedgusCbMSAA=https%3A%2F%
>> 2Foutlook.office365.com
>>  -- response --
>> 200 OK
>> Cache-Control:  no-cache, no-store
>> Pragma:  no-cache
>> Content-Type:  application/json; charset=utf-8
>> Expires:  -1
>> Server:  Microsoft-IIS/8.5
>> x-ms-request-id:  cea27772-54ae-404f-95a4-4e1c870394c4
>> client-request-id:  c61330e5-36d9-421c-b611-8d9a97789157
>> x-ms-gateway-service-instanceid:  ESTSFE_IN_199
>> x-content-type-options:  nosniff
>> Strict-Transport-Security:  max-age=31536000; includeSubDomains
>> P3P:  CP="DSP CUR OTPi IND OTRi ONL FIN"
>> Set-Cookie:  x-ms-gateway-slice=productiona; path=/; secure; HttpOnly
>> stsservicecookie=ests; path=/
>> X-Powered-By:  ASP.NET
>> Date:  Wed, 30 Mar 2016 10:06:32 GMT
>> Content-Length:  2924
>>
>> [2] ESB wire log
>>
>>  [2016-03-30 16:05:24,863] DEBUG - wire >> "POST /services/outLook_Init1
>> HTTP/1.1[\r][\n]"
>> [2016-03-30 16:05:24,863] DEBUG - wire >> "Host:
>> vives-thinkpad-t540p:8280[\r][\n]"
>> [2016-03-30 16:05:24,863] DEBUG - wire >> "Connection: keep-alive[\r][\n]"
>> [2016-03-30 16:05:24,863] DEBUG - wire >> "Content-Length: 796[\r][\n]"
>> [2016-03-30 16:05:24,863] DEBUG - wire >> "Cache-Control:
>> no-cache[\r][\n]"
>> [2016-03-30 16:05:24,863] DEBUG - wire >> "Origin:
>> chrome-extension://mkhojklkhkdaghjjfdnphfphiaiohkef[\r][\n]"
>> [2016-03-30 16:05:24,863] DEBUG - wire >> "x-AnchorMailbox:
>> vi...@vivesxyz.onmicrosoft.com[\r][\n]"
>> [2016-03-30 16:05:24,863] DEBUG - wire >> "User-Agent: Mozilla/5.0 (X11;
>> Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.108
>> Safari/537.36[\r][\n]"
>> [2016-03-30 16:05:24,863] DEBUG - wire >> "Content-Type:
>> application/json[\r][\n]"
>> [2016-03-30 16:05:24,863] DEBUG - wire >> "Accept: */*[\r][\n]"
>> [2016-03-30 16:05:24,864] DEBUG - wire >> "Accept-Encoding: gzip,
>> deflate[\r][\n]"
>> [2016-03-30 16:05:24,864] DEBUG - wire >> "Accept-Language:
>> en-US,en;q=0.8[\r][\n]"
>> [2016-03-30 16:05:24,864] DEBUG - wire >> "Cookie:
>> exchangecookie=3b9aaeb9ce564f5b9852b715950fedd2[\r][\n]"
>> [2016-03-30 16:05:24,864] DEBUG - wire >> "[\r][\n]"
>> [2016-03-30 16:05:24,864] DEBUG - wire >> "{[\n]"
>> [2016-03-30 16:05:24,864] DEBUG - wire >> "
>>  
>> "refreshToken":"AAABiL9Kn2Z27UubvWFPbm0gLSj81wVdCkSsT_rqg9I-CpL5pD0Dyru4vEg5o0nZe7YxCtM24jHbA5pSATNPyypxVyWq8WWnxNeLTMX7SFMzdaD5k0_qohsn4jqCar2U1_LTSgvFyCfvQhVKTF9ugOXE7ST9wjRe7XDAFwU75kMQ3kG1WUTI4lhhCYqoDS_KPwPFWE4_ntj8IYZ1BPkjuMAx514yuVURdjEvOluobippPQCtjWAK5X8bMIC6bLEoWj3D8x4hCDL32NVFBUYLgCKK0uaCFR8ulZKpjMc-8OMG9iS1jCPsIkF8O7-0rUBwr3mHCxycId0FDJIUuu2bqR1RRp3pzyzj3K0UfAUcWnkSZDrkeysPf4RbyQcyMhgRSZdhn7KL-8jQBcHvo2aPvvYErDpG4NnpeMrX5Iuk2amhtVzJYFUi27gTDt1XaPZQskbrYOw_GydTaRWvl0j8RBeG4xRHtv-dVnsphdSR6EkB0LKIFD6kWt0EyUmk4ZEf9OwgzjmPsTh0nxPGw-h

[Dev] [DEV] [PET] Unable to get access token from refresh token via ESB

2016-03-30 Thread Vivekananthan Sivanayagam

Hi all,

I am working with outlook Mail connector, I need to get access token from
refresh token . When I called API through the REST Client, It is working
but through the ESB , I am unable to get response. Please find the wire log
below.

[1] REST Client wire log

POST http://login.microsoftonline.com/common/oauth2/token
Content-Type: application/x-www-form-urlencoded
grant_type=refresh_token_id=xxx_secret=_token=AAABiL9Kn2Z27UubvWFPbm0gLSj81wVdCkSsT_rqg9I-CpL5pD0Dyru4vEg5o0nZe7YxCtM24jHbA5pSATNPyypxVyWq8WWnxNeLTMX7SFMzdaD5k0_qohsn4jqCar2U1_LTSgvFyCfvQhVKTF9ugOXE7ST9wjRe7XDAFwU75kMQ3kG1WUTI4lhhCYqoDS_KPwPFWE4_ntj8IYZ1BPkjuMAx514yuVURdjEvOluobippPQCtjWAK5X8bMIC6bLEoWj3D8x4hCDL32NVFBUYLgCKK0uaCFR8ulZKpjMc-8OMG9iS1jCPsIkF8O7-0rUBwr3mHCxycId0FDJIUuu2bqR1RRp3pzyzj3K0UfAUcWnkSZDrkeysPf4RbyQcyMhgRSZdhn7KL-8jQBcHvo2aPvvYErDpG4NnpeMrX5Iuk2amhtVzJYFUi27gTDt1XaPZQskbrYOw_GydTaRWvl0j8RBeG4xRHtv-dVnsphdSR6EkB0LKIFD6kWt0EyUmk4ZEf9OwgzjmPsTh0nxPGw-h1X02vGK58AL3CMx-Ot1TTInQEMObklysuTjZb4YjVUUiSBX4mnF0YtS1sSyQHRedgusCbMSAA=https%3A%2F%
2Foutlook.office365.com
 -- response --
200 OK
Cache-Control:  no-cache, no-store
Pragma:  no-cache
Content-Type:  application/json; charset=utf-8
Expires:  -1
Server:  Microsoft-IIS/8.5
x-ms-request-id:  cea27772-54ae-404f-95a4-4e1c870394c4
client-request-id:  c61330e5-36d9-421c-b611-8d9a97789157
x-ms-gateway-service-instanceid:  ESTSFE_IN_199
x-content-type-options:  nosniff
Strict-Transport-Security:  max-age=31536000; includeSubDomains
P3P:  CP="DSP CUR OTPi IND OTRi ONL FIN"
Set-Cookie:  x-ms-gateway-slice=productiona; path=/; secure; HttpOnly
stsservicecookie=ests; path=/
X-Powered-By:  ASP.NET
Date:  Wed, 30 Mar 2016 10:06:32 GMT
Content-Length:  2924

[2] ESB wire log

 [2016-03-30 16:05:24,863] DEBUG - wire >> "POST /services/outLook_Init1
HTTP/1.1[\r][\n]"
[2016-03-30 16:05:24,863] DEBUG - wire >> "Host:
vives-thinkpad-t540p:8280[\r][\n]"
[2016-03-30 16:05:24,863] DEBUG - wire >> "Connection: keep-alive[\r][\n]"
[2016-03-30 16:05:24,863] DEBUG - wire >> "Content-Length: 796[\r][\n]"
[2016-03-30 16:05:24,863] DEBUG - wire >> "Cache-Control: no-cache[\r][\n]"
[2016-03-30 16:05:24,863] DEBUG - wire >> "Origin:
chrome-extension://mkhojklkhkdaghjjfdnphfphiaiohkef[\r][\n]"
[2016-03-30 16:05:24,863] DEBUG - wire >> "x-AnchorMailbox:
vi...@vivesxyz.onmicrosoft.com[\r][\n]"
[2016-03-30 16:05:24,863] DEBUG - wire >> "User-Agent: Mozilla/5.0 (X11;
Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.108
Safari/537.36[\r][\n]"
[2016-03-30 16:05:24,863] DEBUG - wire >> "Content-Type:
application/json[\r][\n]"
[2016-03-30 16:05:24,863] DEBUG - wire >> "Accept: */*[\r][\n]"
[2016-03-30 16:05:24,864] DEBUG - wire >> "Accept-Encoding: gzip,
deflate[\r][\n]"
[2016-03-30 16:05:24,864] DEBUG - wire >> "Accept-Language:
en-US,en;q=0.8[\r][\n]"
[2016-03-30 16:05:24,864] DEBUG - wire >> "Cookie:
exchangecookie=3b9aaeb9ce564f5b9852b715950fedd2[\r][\n]"
[2016-03-30 16:05:24,864] DEBUG - wire >> "[\r][\n]"
[2016-03-30 16:05:24,864] DEBUG - wire >> "{[\n]"
[2016-03-30 16:05:24,864] DEBUG - wire >> "
 
"refreshToken":"AAABiL9Kn2Z27UubvWFPbm0gLSj81wVdCkSsT_rqg9I-CpL5pD0Dyru4vEg5o0nZe7YxCtM24jHbA5pSATNPyypxVyWq8WWnxNeLTMX7SFMzdaD5k0_qohsn4jqCar2U1_LTSgvFyCfvQhVKTF9ugOXE7ST9wjRe7XDAFwU75kMQ3kG1WUTI4lhhCYqoDS_KPwPFWE4_ntj8IYZ1BPkjuMAx514yuVURdjEvOluobippPQCtjWAK5X8bMIC6bLEoWj3D8x4hCDL32NVFBUYLgCKK0uaCFR8ulZKpjMc-8OMG9iS1jCPsIkF8O7-0rUBwr3mHCxycId0FDJIUuu2bqR1RRp3pzyzj3K0UfAUcWnkSZDrkeysPf4RbyQcyMhgRSZdhn7KL-8jQBcHvo2aPvvYErDpG4NnpeMrX5Iuk2amhtVzJYFUi27gTDt1XaPZQskbrYOw_GydTaRWvl0j8RBeG4xRHtv-dVnsphdSR6EkB0LKIFD6kWt0EyUmk4ZEf9OwgzjmPsTh0nxPGw-h1X02vGK58AL3CMx-Ot1TTInQEMObklysuTjZb4YjVUUiSBX4mnF0YtS1sSyQHRedgusCbMSAA",[\n]"
[2016-03-30 16:05:24,864] DEBUG - wire >> "
 "clientSecret":"xx",[\n]"
[2016-03-30 16:05:24,864] DEBUG - wire >> "
 "clientId":"x",[\n]"
[2016-03-30 16:05:24,864] DEBUG - wire >> "
 "resource":""[\n]"
[2016-03-30 16:05:24,864] DEBUG - wire >> "}[\n]"
[2016-03-30 16:05:24,882] DEBUG - wire << "POST /common/oauth2/token
HTTP/1.1[\r][\n]"
[2016-03-30 16:05:24,883] DEBUG - wire << "Accept-Language:
en-US,en;q=0.8[\r][\n]"
[2016-03-30 16:05:24,883] DEBUG - wire << "Cookie:
exchangecookie=3b9aaeb9ce564f5b9852b715950fedd2[\r][\n]"
[2016-03-30 16:05:24,883] DEBUG - wire << "Host: login.microsoftonline.com
[\r][\n]"
[2016-03-30 16:05:24,883] DEBUG - wire << "Accept-Encoding: gzip,
deflate[\r][\n]"
[2016-03-30 16:05:24,883] DEBUG - wire << "Origin:
chrome-extension://mkhojklkhkdaghjjfdnphfphiaiohkef[\r][\n]"
[2016-03-30 16:05:24,884] DEBUG - wire << "x-AnchorMailbox:
vi...@vivesxyz.onmicrosoft.com[\r][\n]"
[2016-03-30 16:05:24,884] DEBUG - wire << "Content-Type:
application/x-www-form-urlencoded; charset=UTF-8[\r][\n]"
[2016-03-30 16:05:24,884] DEBUG - wire << "Accept: */*[\r][\n]"
[2016-03-30 16:05:24,884] DEBUG - wire << "Cache-Control: no-cache[\r][\n]"
[2016-03-30 16:05:24,884] DEBUG - wire <<

Re: [Dev] Streaming File transfer with File Inbound/File Connector

2016-03-14 Thread Vivekananthan Sivanayagam

Hi Malaka,

I have created Jira [1].

[1] https://wso2.org/jira/browse/ESBCONNECT-86




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com *
*M:+94752786138*

On Mon, Mar 14, 2016 at 10:59 AM, Malaka Silva  wrote:

> Hi Vivekananthan,
>
> Can we create a Jira and follow up on this please?
>
> On Mon, Mar 14, 2016 at 10:40 AM, Kasun Indrasiri  wrote:
>
>>
>>
>> On Mon, Mar 14, 2016 at 9:57 AM, Malaka Silva  wrote:
>>
>>> Hi Kasun,
>>>
>>> I don't think we have the same functionality of VFS sender in file
>>> connector. We have only focused on use cases not covered with VFS transport.
>>>
>>
>> Ok. I think we need to make sure things are consistent across the
>> transport and the file connector. Can we please include this as an
>> improvement for the next version of the connector.
>>
>>
>>>
>> @Vivekananthan - Please confirm this?
>>>
>>> On Sat, Mar 12, 2016 at 4:39 PM, Kasun Indrasiri  wrote:
>>>
 This is great. Thanks a lot Malaka.
 Also, if we use the file connector as the outbound channel, will it
 work in the same way?

 On Tue, Mar 1, 2016 at 12:36 PM, Malaka Silva  wrote:

> Hi All,
>
> Please ignore my previous comments. This can be done with current
> implementation.
>
> if (builder instanceof DataSourceMessageBuilder &&
> "true".equals(streaming)) {
> dataSource = ManagedDataSourceFactory.create(new
> FileObjectDataSource(file, contentType));
> in = null;
> } else {
> in = new
> AutoCloseInputStream(file.getContent().getInputStream());
> dataSource = null;
> }
> ..
> OMElement documentElement;
> if (in != null) {
> documentElement = builder.processDocument(in,
> contentType, axis2MsgCtx);
> } else {
> documentElement =
> ((DataSourceMessageBuilder)builder).processDocument(dataSource,
> contentType, axis2MsgCtx);
> }
> ...
> if(dataSource != null) {
> dataSource.destroy();
> }
>
> This is
> because 
> message builder able to build messages from
> 
> DataSource objects.
> 
> 
> DataSource
>  by definition the data from a DataSource can be read
> 
> multiple times,
> builders that implement 
> this interface
> can
>  avoid storing the message content in memory.
>  
> If a message builder implements this interface and the
> file/vfs
>  is able to provide the message payload as a data source, then the
> method defined by this interface should be preferred over the method
> defined by Builder.
>  This
>  helps optimizing
> PT
>  with
> vfs/file.
> The builder will typically expose the data source directly or
> indirectly through the returned OMElement, e.g. by adding to the tree an
> OMText or OMDataSource node referencing the data source.
>
> I have checked this with inbound but there is a fix we need to do. I
> have done it in [1]. I have done several tests with and without streaming
> from 5mb to 1gb files.
>
> Without streaming [2] and [3] will show the memory growth. With
> streaming [4]. Without streaming most of the time ESB went OOM.
>
> Find the related configs and axis2 changes in [5] and [6].
>
> [1] https://wso2.org/jira/browse/ESBJAVA-4458
>
> [2]
>
> [image: Inline image 1]
>
> [3]
>
> [image: Inline image 2]
>
> [4]
>
> [image: Inline image 3]
>
> [5]
>
> http://ws.apache.org/ns/synapse;  name="load"
>  sequence="request"  onError="fault" protocol="file" suspend="false">
>
>   1
>   true
>    name="transport.vfs.ContentType">application/file
>    name="transport.vfs.LockReleaseSameNode">false
>   false
>    name="transport.vfs.ActionAfterFailure">DELETE
>   true
>   true
>    name="transport.vfs.ActionAfterProcess">DELETE
>    name="transport.vfs.FileURI">file:///home/wso2/work/tmp/file/in
>   false
>   true
>   enable
>    name="transport.vfs.FileSortAscending">true
>    name="transport.vfs.FileSortAttribute">NONE
>   false
>
> 
>
> 
> 
> 
> 
>  value="true"/>
> 
> 
> 
> 
>
> [6]
>  class="org.apache.axis2.format.BinaryBuilder"/>
>
> 
>

Re: [Dev] Streaming File transfer with File Inbound/File Connector

2016-03-13 Thread Vivekananthan Sivanayagam

Hi,

We don't have the same functionality of VFS sender in File Connector.




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com *
*M:+94752786138*

On Mon, Mar 14, 2016 at 9:57 AM, Malaka Silva  wrote:

> Hi Kasun,
>
> I don't think we have the same functionality of VFS sender in file
> connector. We have only focused on use cases not covered with VFS transport.
>
> @Vivekananthan - Please confirm this?
>
> On Sat, Mar 12, 2016 at 4:39 PM, Kasun Indrasiri  wrote:
>
>> This is great. Thanks a lot Malaka.
>> Also, if we use the file connector as the outbound channel, will it work
>> in the same way?
>>
>> On Tue, Mar 1, 2016 at 12:36 PM, Malaka Silva  wrote:
>>
>>> Hi All,
>>>
>>> Please ignore my previous comments. This can be done with current
>>> implementation.
>>>
>>> if (builder instanceof DataSourceMessageBuilder &&
>>> "true".equals(streaming)) {
>>> dataSource = ManagedDataSourceFactory.create(new
>>> FileObjectDataSource(file, contentType));
>>> in = null;
>>> } else {
>>> in = new
>>> AutoCloseInputStream(file.getContent().getInputStream());
>>> dataSource = null;
>>> }
>>> ..
>>> OMElement documentElement;
>>> if (in != null) {
>>> documentElement = builder.processDocument(in,
>>> contentType, axis2MsgCtx);
>>> } else {
>>> documentElement =
>>> ((DataSourceMessageBuilder)builder).processDocument(dataSource,
>>> contentType, axis2MsgCtx);
>>> }
>>> ...
>>> if(dataSource != null) {
>>> dataSource.destroy();
>>> }
>>>
>>> This is
>>> because 
>>> message builder able to build messages from
>>> 
>>> DataSource objects.
>>> 
>>> 
>>> DataSource
>>>  by definition the data from a DataSource can be read
>>> 
>>> multiple times,
>>> builders that implement 
>>> this interface
>>> can
>>>  avoid storing the message content in memory.
>>>  
>>> If a message builder implements this interface and the
>>> file/vfs
>>>  is able to provide the message payload as a data source, then the
>>> method defined by this interface should be preferred over the method
>>> defined by Builder.
>>>  This
>>>  helps optimizing
>>> PT
>>>  with
>>> vfs/file.
>>> The builder will typically expose the data source directly or indirectly
>>> through the returned OMElement, e.g. by adding to the tree an OMText or
>>> OMDataSource node referencing the data source.
>>>
>>> I have checked this with inbound but there is a fix we need to do. I
>>> have done it in [1]. I have done several tests with and without streaming
>>> from 5mb to 1gb files.
>>>
>>> Without streaming [2] and [3] will show the memory growth. With
>>> streaming [4]. Without streaming most of the time ESB went OOM.
>>>
>>> Find the related configs and axis2 changes in [5] and [6].
>>>
>>> [1] https://wso2.org/jira/browse/ESBJAVA-4458
>>>
>>> [2]
>>>
>>> [image: Inline image 1]
>>>
>>> [3]
>>>
>>> [image: Inline image 2]
>>>
>>> [4]
>>>
>>> [image: Inline image 3]
>>>
>>> [5]
>>>
>>> http://ws.apache.org/ns/synapse;  name="load"
>>>  sequence="request"  onError="fault" protocol="file" suspend="false">
>>>
>>>   1
>>>   true
>>>   >> name="transport.vfs.ContentType">application/file
>>>   >> name="transport.vfs.LockReleaseSameNode">false
>>>   false
>>>   >> name="transport.vfs.ActionAfterFailure">DELETE
>>>   true
>>>   true
>>>   >> name="transport.vfs.ActionAfterProcess">DELETE
>>>   >> name="transport.vfs.FileURI">file:///home/wso2/work/tmp/file/in
>>>   false
>>>   true
>>>   enable
>>>   true
>>>   NONE
>>>   false
>>>
>>> 
>>>
>>> 
>>> 
>>> 
>>> 
>>> >> value="true"/>
>>> 
>>> 
>>> 
>>> 
>>>
>>> [6]
>>> >> class="org.apache.axis2.format.BinaryBuilder"/>
>>>
>>> >>
>>> class="org.wso2.carbon.relay.ExpandingMessageFormatter"/>
>>>
>>> On Mon, Feb 29, 2016 at 12:02 PM, Malaka Silva  wrote:
>>>
 Hi Kasun,

 Currently no OOB solution with ESB 4.9.0. File always gets build before
 mediation.

 However use case mentioned can be handled with Schedule task -> File
 connector search -> File connector copy

 +1 for OOB solution.

 We can  do this for ESB 5.0. Also there is an option to do this as a
 custom inbound. So that this can be used by previous ESB versions as well.

 So default inbound can be used, if someone needs to do a mediation on
 file content and custom inbound for PT file use case. WDYT?


 On Mon, Feb 29, 2016 at 11:49 AM, Kasun Indrasiri 
 wrote:

> Hi Malaka,
>
> Do we support

[Dev] (no subject)

2016-03-13 Thread Vivekananthan Sivanayagam

Hi ,

We don't have the same functionality of VFS sender in File Connector.





*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com *
*M:+94752786138*

On Mon, Mar 14, 2016 at 9:57 AM, Malaka Silva  wrote:

> Hi Kasun,
>
> I don't think we have the same functionality of VFS sender in file
> connector. We have only focused on use cases not covered with VFS transport.
>
> @Vivekananthan - Please confirm this?
>
> On Sat, Mar 12, 2016 at 4:39 PM, Kasun Indrasiri  wrote:
>
>> This is great. Thanks a lot Malaka.
>> Also, if we use the file connector as the outbound channel, will it work
>> in the same way?
>>
>> On Tue, Mar 1, 2016 at 12:36 PM, Malaka Silva  wrote:
>>
>>> Hi All,
>>>
>>> Please ignore my previous comments. This can be done with current
>>> implementation.
>>>
>>> if (builder instanceof DataSourceMessageBuilder &&
>>> "true".equals(streaming)) {
>>> dataSource = ManagedDataSourceFactory.create(new
>>> FileObjectDataSource(file, contentType));
>>> in = null;
>>> } else {
>>> in = new
>>> AutoCloseInputStream(file.getContent().getInputStream());
>>> dataSource = null;
>>> }
>>> ..
>>> OMElement documentElement;
>>> if (in != null) {
>>> documentElement = builder.processDocument(in,
>>> contentType, axis2MsgCtx);
>>> } else {
>>> documentElement =
>>> ((DataSourceMessageBuilder)builder).processDocument(dataSource,
>>> contentType, axis2MsgCtx);
>>> }
>>> ...
>>> if(dataSource != null) {
>>> dataSource.destroy();
>>> }
>>>
>>> This is
>>> because 
>>> message builder able to build messages from
>>> 
>>> DataSource objects.
>>> 
>>> 
>>> DataSource
>>>  by definition the data from a DataSource can be read
>>> 
>>> multiple times,
>>> builders that implement 
>>> this interface
>>> can
>>>  avoid storing the message content in memory.
>>>  
>>> If a message builder implements this interface and the
>>> file/vfs
>>>  is able to provide the message payload as a data source, then the
>>> method defined by this interface should be preferred over the method
>>> defined by Builder.
>>>  This
>>>  helps optimizing
>>> PT
>>>  with
>>> vfs/file.
>>> The builder will typically expose the data source directly or indirectly
>>> through the returned OMElement, e.g. by adding to the tree an OMText or
>>> OMDataSource node referencing the data source.
>>>
>>> I have checked this with inbound but there is a fix we need to do. I
>>> have done it in [1]. I have done several tests with and without streaming
>>> from 5mb to 1gb files.
>>>
>>> Without streaming [2] and [3] will show the memory growth. With
>>> streaming [4]. Without streaming most of the time ESB went OOM.
>>>
>>> Find the related configs and axis2 changes in [5] and [6].
>>>
>>> [1] https://wso2.org/jira/browse/ESBJAVA-4458
>>>
>>> [2]
>>>
>>> [image: Inline image 1]
>>>
>>> [3]
>>>
>>> [image: Inline image 2]
>>>
>>> [4]
>>>
>>> [image: Inline image 3]
>>>
>>> [5]
>>>
>>> http://ws.apache.org/ns/synapse;  name="load"
>>>  sequence="request"  onError="fault" protocol="file" suspend="false">
>>>
>>>   1
>>>   true
>>>   >> name="transport.vfs.ContentType">application/file
>>>   >> name="transport.vfs.LockReleaseSameNode">false
>>>   false
>>>   >> name="transport.vfs.ActionAfterFailure">DELETE
>>>   true
>>>   true
>>>   >> name="transport.vfs.ActionAfterProcess">DELETE
>>>   >> name="transport.vfs.FileURI">file:///home/wso2/work/tmp/file/in
>>>   false
>>>   true
>>>   enable
>>>   true
>>>   NONE
>>>   false
>>>
>>> 
>>>
>>> 
>>> 
>>> 
>>> 
>>> >> value="true"/>
>>> 
>>> 
>>> 
>>> 
>>>
>>> [6]
>>> >> class="org.apache.axis2.format.BinaryBuilder"/>
>>>
>>> >>
>>> class="org.wso2.carbon.relay.ExpandingMessageFormatter"/>
>>>
>>> On Mon, Feb 29, 2016 at 12:02 PM, Malaka Silva  wrote:
>>>
 Hi Kasun,

 Currently no OOB solution with ESB 4.9.0. File always gets build before
 mediation.

 However use case mentioned can be handled with Schedule task -> File
 connector search -> File connector copy

 +1 for OOB solution.

 We can  do this for ESB 5.0. Also there is an option to do this as a
 custom inbound. So that this can be used by previous ESB versions as well.

 So default inbound can be used, if someone needs to do a mediation on
 file content and custom inbound for PT file use case. WDYT?


 On Mon, Feb 29, 2016 at 11:49 AM, Kasun Indrasiri 
 wrote:

> Hi Malaka,
>
> Do we

Re: [Dev] [DEV] [PET] Could not pass ftp over http proxy.

2016-03-09 Thread Vivekananthan Sivanayagam

Hi Malaka ,

We had a screen sharing and this is solved now. It is working fine. The
problem was in a configuration of authentication part.

@Anuruddha

Thank you for helping and to solve this issue.





*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Wed, Mar 9, 2016 at 4:05 PM, Malaka Silva <mal...@wso2.com> wrote:

> Great thx Anuruddha.
>
> On Wed, Mar 9, 2016 at 3:56 PM, Anuruddha Premalal <anurud...@wso2.com>
> wrote:
>
>> Hi Malaka,
>>
>> My setup in a VM. Will join a for a screen sharing session with Vivek.
>>
>> On Wed, Mar 9, 2016 at 3:40 PM, Malaka Silva <mal...@wso2.com> wrote:
>>
>>> Hi Anuruddha,
>>>
>>> I think you already have the setup? Great if you could share it
>>> with Vivekananthan if possible?
>>>
>>> On Wed, Mar 9, 2016 at 1:38 PM, Vivekananthan Sivanayagam <
>>> vivekanant...@wso2.com> wrote:
>>>
>>>> Hi Anuruddha,
>>>>
>>>> I have tried and getting same error again.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *Thank youVivekananthan Sivanayagam*
>>>>
>>>> *Associate Software Engineer | WSO2*
>>>>
>>>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>>>> *M:+94752786138 <%2B94752786138>*
>>>>
>>>> On Wed, Mar 9, 2016 at 12:05 PM, Anuruddha Premalal <anurud...@wso2.com
>>>> > wrote:
>>>>
>>>>> Hi Vivek,
>>>>>
>>>>> As the error log mentioned, it's clearly an authentication error from
>>>>> the squid proxy. Consult[1] to configure squid proxy users, you should be
>>>>> all set once the squid users are properly confifgured.
>>>>>
>>>>> Response received from the proxy:
>>>>> HTTP/1.1 403 Forbidden
>>>>> Server: squid/3.3.8
>>>>> Mime-Version: 1.0
>>>>> Date: Wed, 09 Mar 2016 05:14:22 GMT
>>>>> Content-Type: text/html
>>>>> Content-Length: 3107
>>>>> X-Squid-Error: ERR_ACCESS_DENIED 0
>>>>> Vary: Accept-Language
>>>>> Content-Language: en
>>>>> X-Cache: MISS from squidproxy.com
>>>>> X-Cache-Lookup: NONE from squidproxy.com:3128
>>>>> Via: 1.1 squidproxy.com (squid/3.3.8)
>>>>> Connection: keep-alive
>>>>>
>>>>> [1]
>>>>> http://www.cyberciti.biz/tips/linux-unix-squid-proxy-server-authentication.html
>>>>>
>>>>>
>>>>> On Wed, Mar 9, 2016 at 10:59 AM, Vivekananthan Sivanayagam <
>>>>> vivekanant...@wso2.com> wrote:
>>>>>
>>>>>> Hi ,
>>>>>>
>>>>>> I tried as Anuruddha suggested after I made minor changes in my code,
>>>>>> when I skipped "Squid" proxy, it is working fine and we can get expected
>>>>>> output. When I tried with "Squid" proxy, I got following error[1].
>>>>>>
>>>>>> [1]
>>>>>>
>>>>>>  ERROR - FileFtpOverProxy Error occurred while
>>>>>> uploading:HTTPTunnelConnector: connection failed
>>>>>> Response received from the proxy:
>>>>>> HTTP/1.1 403 Forbidden
>>>>>> Server: squid/3.3.8
>>>>>> Mime-Version: 1.0
>>>>>> Date: Wed, 09 Mar 2016 05:14:22 GMT
>>>>>> Content-Type: text/html
>>>>>> Content-Length: 3107
>>>>>> X-Squid-Error: ERR_ACCESS_DENIED 0
>>>>>> Vary: Accept-Language
>>>>>> Content-Language: en
>>>>>> X-Cache: MISS from squidproxy.com
>>>>>> X-Cache-Lookup: NONE from squidproxy.com:3128
>>>>>> Via: 1.1 squidproxy.com (squid/3.3.8)
>>>>>> Connection: keep-alive
>>>>>>
>>>>>> java.io.IOException: HTTPTunnelConnector: connection failed
>>>>>> Response received from the proxy:
>>>>>> HTTP/1.1 403 Forbidden
>>>>>> Server: squid/3.3.8
>>>>>> Mime-Version: 1.0
>>>>>> Date: Wed, 09 Mar 2016 05:14:22 GMT
>>>>>> Content-Type: text/html
>>>>>> Content-Length: 3107
>>>>>> X-Squid-Error: ERR_ACCESS_DENIED 0
>>>>>>

Re: [Dev] [DEV] [PET] Could not pass ftp over http proxy.

2016-03-09 Thread Vivekananthan Sivanayagam

Hi Anuruddha,

I have tried and getting same error again.






*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Wed, Mar 9, 2016 at 12:05 PM, Anuruddha Premalal <anurud...@wso2.com>
wrote:

> Hi Vivek,
>
> As the error log mentioned, it's clearly an authentication error from the
> squid proxy. Consult[1] to configure squid proxy users, you should be all
> set once the squid users are properly confifgured.
>
> Response received from the proxy:
> HTTP/1.1 403 Forbidden
> Server: squid/3.3.8
> Mime-Version: 1.0
> Date: Wed, 09 Mar 2016 05:14:22 GMT
> Content-Type: text/html
> Content-Length: 3107
> X-Squid-Error: ERR_ACCESS_DENIED 0
> Vary: Accept-Language
> Content-Language: en
> X-Cache: MISS from squidproxy.com
> X-Cache-Lookup: NONE from squidproxy.com:3128
> Via: 1.1 squidproxy.com (squid/3.3.8)
> Connection: keep-alive
>
> [1]
> http://www.cyberciti.biz/tips/linux-unix-squid-proxy-server-authentication.html
>
>
> On Wed, Mar 9, 2016 at 10:59 AM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> Hi ,
>>
>> I tried as Anuruddha suggested after I made minor changes in my code,
>> when I skipped "Squid" proxy, it is working fine and we can get expected
>> output. When I tried with "Squid" proxy, I got following error[1].
>>
>> [1]
>>
>>  ERROR - FileFtpOverProxy Error occurred while
>> uploading:HTTPTunnelConnector: connection failed
>> Response received from the proxy:
>> HTTP/1.1 403 Forbidden
>> Server: squid/3.3.8
>> Mime-Version: 1.0
>> Date: Wed, 09 Mar 2016 05:14:22 GMT
>> Content-Type: text/html
>> Content-Length: 3107
>> X-Squid-Error: ERR_ACCESS_DENIED 0
>> Vary: Accept-Language
>> Content-Language: en
>> X-Cache: MISS from squidproxy.com
>> X-Cache-Lookup: NONE from squidproxy.com:3128
>> Via: 1.1 squidproxy.com (squid/3.3.8)
>> Connection: keep-alive
>>
>> java.io.IOException: HTTPTunnelConnector: connection failed
>> Response received from the proxy:
>> HTTP/1.1 403 Forbidden
>> Server: squid/3.3.8
>> Mime-Version: 1.0
>> Date: Wed, 09 Mar 2016 05:14:22 GMT
>> Content-Type: text/html
>> Content-Length: 3107
>> X-Squid-Error: ERR_ACCESS_DENIED 0
>> Vary: Accept-Language
>> Content-Language: en
>> X-Cache: MISS from squidproxy.com
>> X-Cache-Lookup: NONE from squidproxy.com:3128
>> Via: 1.1 squidproxy.com (squid/3.3.8)
>> Connection: keep-alive
>>
>> at
>> org.apache.commons.net.ftp.FTPHTTPClient.tunnelHandshake(FTPHTTPClient.java:194)
>> at
>> org.apache.commons.net.ftp.FTPHTTPClient._openDataConnection_(FTPHTTPClient.java:114)
>> at org.apache.commons.net.ftp.FTPClient._storeFile(FTPClient.java:633)
>> at org.apache.commons.net.ftp.FTPClient.__storeFile(FTPClient.java:624)
>> at org.apache.commons.net.ftp.FTPClient.storeFile(FTPClient.java:1976)
>> at
>> org.wso2.carbon.connector.FileFtpOverProxy.ftpOverHttp(FileFtpOverProxy.java:194)
>> at
>> org.wso2.carbon.connector.FileFtpOverProxy.connect(FileFtpOverProxy.java:58)
>> at
>> org.wso2.carbon.connector.core.AbstractConnector.mediate(AbstractConnector.java:32)
>> at
>> org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:78)
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
>> at
>> org.apache.synapse.mediators.template.TemplateMediator.mediate(TemplateMediator.java:97)
>> at
>> org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:129)
>> at
>> org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:78)
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
>> at
>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
>> at
>> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:185)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at
>> org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:317)
>> at
>> org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:363)
>> at
>> org.apach

Re: [Dev] [DEV] [PET] Could not pass ftp over http proxy.

2016-03-08 Thread Vivekananthan Sivanayagam

Hi ,

I tried as Anuruddha suggested after I made minor changes in my code, when
I skipped "Squid" proxy, it is working fine and we can get expected output.
When I tried with "Squid" proxy, I got following error[1].

[1]

 ERROR - FileFtpOverProxy Error occurred while
uploading:HTTPTunnelConnector: connection failed
Response received from the proxy:
HTTP/1.1 403 Forbidden
Server: squid/3.3.8
Mime-Version: 1.0
Date: Wed, 09 Mar 2016 05:14:22 GMT
Content-Type: text/html
Content-Length: 3107
X-Squid-Error: ERR_ACCESS_DENIED 0
Vary: Accept-Language
Content-Language: en
X-Cache: MISS from squidproxy.com
X-Cache-Lookup: NONE from squidproxy.com:3128
Via: 1.1 squidproxy.com (squid/3.3.8)
Connection: keep-alive

java.io.IOException: HTTPTunnelConnector: connection failed
Response received from the proxy:
HTTP/1.1 403 Forbidden
Server: squid/3.3.8
Mime-Version: 1.0
Date: Wed, 09 Mar 2016 05:14:22 GMT
Content-Type: text/html
Content-Length: 3107
X-Squid-Error: ERR_ACCESS_DENIED 0
Vary: Accept-Language
Content-Language: en
X-Cache: MISS from squidproxy.com
X-Cache-Lookup: NONE from squidproxy.com:3128
Via: 1.1 squidproxy.com (squid/3.3.8)
Connection: keep-alive

at
org.apache.commons.net.ftp.FTPHTTPClient.tunnelHandshake(FTPHTTPClient.java:194)
at
org.apache.commons.net.ftp.FTPHTTPClient._openDataConnection_(FTPHTTPClient.java:114)
at org.apache.commons.net.ftp.FTPClient._storeFile(FTPClient.java:633)
at org.apache.commons.net.ftp.FTPClient.__storeFile(FTPClient.java:624)
at org.apache.commons.net.ftp.FTPClient.storeFile(FTPClient.java:1976)
at
org.wso2.carbon.connector.FileFtpOverProxy.ftpOverHttp(FileFtpOverProxy.java:194)
at
org.wso2.carbon.connector.FileFtpOverProxy.connect(FileFtpOverProxy.java:58)
at
org.wso2.carbon.connector.core.AbstractConnector.mediate(AbstractConnector.java:32)
at
org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:78)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at
org.apache.synapse.mediators.template.TemplateMediator.mediate(TemplateMediator.java:97)
at
org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:129)
at
org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:78)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at
org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:185)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:317)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:363)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)


Please give me suggestion to solve this error.




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Fri, Mar 4, 2016 at 5:07 PM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Hi,
>
> Please ignore above error[2].
>
> This is the correct error.
>
> [2016-03-04 17:05:53,405] ERROR - FileFtpOverProxy Could not connect to
> FTP ftpServer: Could not connect to 127.0.0.1 using port 21
> java.io.IOException: Could not connect to 127.0.0.1 using port 21
>
> at org.apache.commons.net.ftp.FTPHTTPClient.connect(FTPHTTPClient.java:138)
> at
> org.wso2.carbon.connector.FileFtpOverProxy.ftpOverHttp(FileFtpOverProxy.java:135)
> at
> org.wso2.carbon.connector.FileFtpOverProxy.connect(FileFtpOverProxy.java:58)
> at
> org.wso2.carbon.connector.core.AbstractConnector.mediate(AbstractConnector.java:32)
> at
> org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:78)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
> at
> org.apache.synapse.mediators.template.TemplateMediator.mediate(TemplateMediator.java:97)
> at
> org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:129)
> at
> org.apache.synapse.mediators.template.InvokeMediator.mediat

Re: [Dev] [DEV] [PET] Could not pass ftp over http proxy.

2016-03-04 Thread Vivekananthan Sivanayagam

Hi,

Please ignore above error[2].

This is the correct error.

[2016-03-04 17:05:53,405] ERROR - FileFtpOverProxy Could not connect to FTP
ftpServer: Could not connect to 127.0.0.1 using port 21
java.io.IOException: Could not connect to 127.0.0.1 using port 21
at org.apache.commons.net.ftp.FTPHTTPClient.connect(FTPHTTPClient.java:138)
at
org.wso2.carbon.connector.FileFtpOverProxy.ftpOverHttp(FileFtpOverProxy.java:135)
at
org.wso2.carbon.connector.FileFtpOverProxy.connect(FileFtpOverProxy.java:58)
at
org.wso2.carbon.connector.core.AbstractConnector.mediate(AbstractConnector.java:32)
at
org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:78)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at
org.apache.synapse.mediators.template.TemplateMediator.mediate(TemplateMediator.java:97)
at
org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:129)
at
org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:78)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at
org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:185)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:317)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:363)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: HTTPTunnelConnector: connection failed
Response received from the proxy:
HTTP/1.1 403 Forbidden
Server: squid/3.3.8
Mime-Version: 1.0
Date: Fri, 04 Mar 2016 11:35:53 GMT
Content-Type: text/html
Content-Length: 3113
X-Squid-Error: ERR_ACCESS_DENIED 0
Vary: Accept-Language
Content-Language: en
X-Cache: MISS from vives-ThinkPad-T540p
X-Cache-Lookup: NONE from vives-ThinkPad-T540p:3128
Via: 1.1 vives-ThinkPad-T540p (squid/3.3.8)
Connection: keep-alive

at
org.apache.commons.net.ftp.FTPHTTPClient.tunnelHandshake(FTPHTTPClient.java:194)
at org.apache.commons.net.ftp.FTPHTTPClient.connect(FTPHTTPClient.java:135)





*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Fri, Mar 4, 2016 at 5:03 PM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Hi Anuruddha,
>
> When I tested with skipping Squid proxy, I got the error[1].I was getting
> the error [2], when I included Squid proxy.
>
> [1]
>
> [2016-03-04 16:46:41,101] ERROR - FileFtpOverProxy Error occurred while
> uploading:Connection timed out
> java.net.ConnectException: Connection timed out
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
> at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:579)
> at
> org.apache.commons.net.ftp.FTPClient._openDataConnection_(FTPClient.java:894)
> at org.apache.commons.net.ftp.FTPClient._storeFile(FTPClient.java:633)
> at org.apache.commons.net.ftp.FTPClient.__storeFile(FTPClient.java:624)
> at org.apache.commons.net.ftp.FTPClient.storeFile(FTPClient.java:1976)
> at
> org.wso2.carbon.connector.FileFtpOverProxy.ftpOverHttp(FileFtpOverProxy.java:194)
> at
> org.wso2.carbon.connector.FileFtpOverProxy.connect(FileFtpOverProxy.java:58)
> at
> org.wso2.carbon.connector.core.AbstractConnector.mediate(AbstractConnector.java:32)
> at
> org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:78)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
> at
> org.apache.synapse.mediators.template.TemplateMediator.mediate(TemplateMediator.java:97)
> at
> org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:129)
> at
> org.apache.

Re: [Dev] [DEV] [PET] Could not pass ftp over http proxy.

2016-03-04 Thread Vivekananthan Sivanayagam

 failed
Response received from the proxy:
HTTP/1.1 403 Forbidden
Server: squid/3.3.8
Mime-Version: 1.0
Date: Fri, 04 Mar 2016 11:25:28 GMT
Content-Type: text/html
Content-Length: 3113
X-Squid-Error: ERR_ACCESS_DENIED 0
Vary: Accept-Language
Content-Language: en
X-Cache: MISS from vives-ThinkPad-T540p
X-Cache-Lookup: NONE from vives-ThinkPad-T540p:3128
Via: 1.1 vives-ThinkPad-T540p (squid/3.3.8)
Connection: keep-alive

at
org.apache.commons.net.ftp.FTPHTTPClient.tunnelHandshake(FTPHTTPClient.java:194)
at org.apache.commons.net.ftp.FTPHTTPClient.connect(FTPHTTPClient.java:135)


Please give me suggestion to overcome those errors.




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Fri, Mar 4, 2016 at 10:54 AM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Hi Anuruddha,
>
> I tried as you mentioned to check standalone mode and skipped squid proxy
> test, but I got same error again. I followed this doc[1] to create ftp
> connection.
>
> [1] http://www.krizna.com/ubuntu/setup-ftp-server-on-ubuntu-14-04-vsftpd/
>
>
>
>
> *Thank youVivekananthan Sivanayagam*
>
> *Associate Software Engineer | WSO2*
>
> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
> *M:+94752786138 <%2B94752786138>*
>
> On Fri, Mar 4, 2016 at 8:14 AM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> Hi Anuruddha,
>>
>> Thank you. I check and update.
>>
>>
>>
>>
>> *Thank youVivekananthan Sivanayagam*
>>
>> *Associate Software Engineer | WSO2*
>>
>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>> *M:+94752786138 <%2B94752786138>*
>>
>> On Fri, Mar 4, 2016 at 7:51 AM, Anuruddha Premalal <anurud...@wso2.com>
>> wrote:
>>
>>> Hi Vivekanathan,
>>>
>>> Quick way to diagnose this is to add a main method and pass the
>>> parameters and check whether it's working in standalone mode. That way you
>>> have more power and control over debugging.
>>>
>>>  As the error states it's trying to do a FTP upload via a
>>> close/unavailable FTP connection so you can focus on the connection
>>> creation section and see what's happening there, also at the same time
>>> monitor the FTP server logs, I'd suggest to skip the squid proxy first and
>>> do the testing incrementally.
>>>
>>> Regards,
>>> Anuruddha.
>>>
>>> On Wed, Mar 2, 2016 at 11:54 AM, Vivekananthan Sivanayagam <
>>> vivekanant...@wso2.com> wrote:
>>>
>>>> Hi ,
>>>>
>>>> I have implemented a method to support FTP Over proxy in file connector
>>>> version 2, I used Java Client [1](commons-net 3.4) and configured "Squid"
>>>> proxy[2].
>>>>
>>>> I am getting the following errors when I invoke a method.
>>>>
>>>> [2016-03-02 10:56:19,535] ERROR - FileFtpOverProxy Error occurred while
>>>> uploading:Connection is not open
>>>> java.io.IOException: Connection is not open
>>>> at org.apache.commons.net.ftp.FTP.sendCommand(FTP.java:474)
>>>> at org.apache.commons.net.ftp.FTP.sendCommand(FTP.java:608)
>>>> at org.apache.commons.net.ftp.FTP.user(FTP.java:753)
>>>> at org.apache.commons.net.ftp.FTPClient.login(FTPClient.java:1034)
>>>> at
>>>> org.wso2.carbon.connector.FileFtpOverProxy.ftpOverHttp(FileFtpOverProxy.java:151)
>>>> at
>>>> org.wso2.carbon.connector.FileFtpOverProxy.connect(FileFtpOverProxy.java:47)
>>>> at
>>>> org.wso2.carbon.connector.core.AbstractConnector.mediate(AbstractConnector.java:32)
>>>> at
>>>> org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:78)
>>>> at
>>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
>>>> at
>>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
>>>> at
>>>> org.apache.synapse.mediators.template.TemplateMediator.mediate(TemplateMediator.java:97)
>>>> at
>>>> org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:129)
>>>> at
>>>> org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:78)
>>>> at
>>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
>>>> at
>>>> org.apache.synapse.mediators.AbstractL

Re: [Dev] [DEV] [PET] Could not pass ftp over http proxy.

2016-03-03 Thread Vivekananthan Sivanayagam

Hi Anuruddha,

I tried as you mentioned to check standalone mode and skipped squid proxy
test, but I got same error again. I followed this doc[1] to create ftp
connection.

[1] http://www.krizna.com/ubuntu/setup-ftp-server-on-ubuntu-14-04-vsftpd/




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Fri, Mar 4, 2016 at 8:14 AM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Hi Anuruddha,
>
> Thank you. I check and update.
>
>
>
>
> *Thank youVivekananthan Sivanayagam*
>
> *Associate Software Engineer | WSO2*
>
> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
> *M:+94752786138 <%2B94752786138>*
>
> On Fri, Mar 4, 2016 at 7:51 AM, Anuruddha Premalal <anurud...@wso2.com>
> wrote:
>
>> Hi Vivekanathan,
>>
>> Quick way to diagnose this is to add a main method and pass the
>> parameters and check whether it's working in standalone mode. That way you
>> have more power and control over debugging.
>>
>>  As the error states it's trying to do a FTP upload via a
>> close/unavailable FTP connection so you can focus on the connection
>> creation section and see what's happening there, also at the same time
>> monitor the FTP server logs, I'd suggest to skip the squid proxy first and
>> do the testing incrementally.
>>
>> Regards,
>> Anuruddha.
>>
>> On Wed, Mar 2, 2016 at 11:54 AM, Vivekananthan Sivanayagam <
>> vivekanant...@wso2.com> wrote:
>>
>>> Hi ,
>>>
>>> I have implemented a method to support FTP Over proxy in file connector
>>> version 2, I used Java Client [1](commons-net 3.4) and configured "Squid"
>>> proxy[2].
>>>
>>> I am getting the following errors when I invoke a method.
>>>
>>> [2016-03-02 10:56:19,535] ERROR - FileFtpOverProxy Error occurred while
>>> uploading:Connection is not open
>>> java.io.IOException: Connection is not open
>>> at org.apache.commons.net.ftp.FTP.sendCommand(FTP.java:474)
>>> at org.apache.commons.net.ftp.FTP.sendCommand(FTP.java:608)
>>> at org.apache.commons.net.ftp.FTP.user(FTP.java:753)
>>> at org.apache.commons.net.ftp.FTPClient.login(FTPClient.java:1034)
>>> at
>>> org.wso2.carbon.connector.FileFtpOverProxy.ftpOverHttp(FileFtpOverProxy.java:151)
>>> at
>>> org.wso2.carbon.connector.FileFtpOverProxy.connect(FileFtpOverProxy.java:47)
>>> at
>>> org.wso2.carbon.connector.core.AbstractConnector.mediate(AbstractConnector.java:32)
>>> at
>>> org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:78)
>>> at
>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
>>> at
>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
>>> at
>>> org.apache.synapse.mediators.template.TemplateMediator.mediate(TemplateMediator.java:97)
>>> at
>>> org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:129)
>>> at
>>> org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:78)
>>> at
>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
>>> at
>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
>>> at
>>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
>>> at
>>> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:185)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>> at
>>> org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:317)
>>> at
>>> org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:363)
>>> at
>>> org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
>>> at
>>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>> at java.lang.Thread.run(Thread.java:745)
>>>
>>> I have attached a FileFtpOverProxy.java here.
>>>
>>> [1] https://commons.apache.org/proper/commons-net/
>>> [2] http://www.tecmint.com/configure-squid-server-in-linux/
>>>
>>>
>>>
>>>
>>>
>>>
>>> *Thank youVivekananthan SivanayagamAssociate Software Engineer |
>>> WSO2E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>M:+94752786138
>>> <%2B94752786138>*
>>>
>>
>>
>>
>> --
>> *Anuruddha Premalal*
>> Software Eng. | WSO2 Inc.
>> Mobile : +94717213122
>> Web site : www.anuruddha.org
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [PET] Could not pass ftp over http proxy.

2016-03-03 Thread Vivekananthan Sivanayagam

Hi Anuruddha,

Thank you. I check and update.




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Fri, Mar 4, 2016 at 7:51 AM, Anuruddha Premalal <anurud...@wso2.com>
wrote:

> Hi Vivekanathan,
>
> Quick way to diagnose this is to add a main method and pass the parameters
> and check whether it's working in standalone mode. That way you have more
> power and control over debugging.
>
>  As the error states it's trying to do a FTP upload via a
> close/unavailable FTP connection so you can focus on the connection
> creation section and see what's happening there, also at the same time
> monitor the FTP server logs, I'd suggest to skip the squid proxy first and
> do the testing incrementally.
>
> Regards,
> Anuruddha.
>
> On Wed, Mar 2, 2016 at 11:54 AM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> Hi ,
>>
>> I have implemented a method to support FTP Over proxy in file connector
>> version 2, I used Java Client [1](commons-net 3.4) and configured "Squid"
>> proxy[2].
>>
>> I am getting the following errors when I invoke a method.
>>
>> [2016-03-02 10:56:19,535] ERROR - FileFtpOverProxy Error occurred while
>> uploading:Connection is not open
>> java.io.IOException: Connection is not open
>> at org.apache.commons.net.ftp.FTP.sendCommand(FTP.java:474)
>> at org.apache.commons.net.ftp.FTP.sendCommand(FTP.java:608)
>> at org.apache.commons.net.ftp.FTP.user(FTP.java:753)
>> at org.apache.commons.net.ftp.FTPClient.login(FTPClient.java:1034)
>> at
>> org.wso2.carbon.connector.FileFtpOverProxy.ftpOverHttp(FileFtpOverProxy.java:151)
>> at
>> org.wso2.carbon.connector.FileFtpOverProxy.connect(FileFtpOverProxy.java:47)
>> at
>> org.wso2.carbon.connector.core.AbstractConnector.mediate(AbstractConnector.java:32)
>> at
>> org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:78)
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
>> at
>> org.apache.synapse.mediators.template.TemplateMediator.mediate(TemplateMediator.java:97)
>> at
>> org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:129)
>> at
>> org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:78)
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
>> at
>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
>> at
>> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:185)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at
>> org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:317)
>> at
>> org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:363)
>> at
>> org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
>> at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:745)
>>
>> I have attached a FileFtpOverProxy.java here.
>>
>> [1] https://commons.apache.org/proper/commons-net/
>> [2] http://www.tecmint.com/configure-squid-server-in-linux/
>>
>>
>>
>>
>>
>>
>> *Thank youVivekananthan SivanayagamAssociate Software Engineer |
>> WSO2E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>M:+94752786138
>> <%2B94752786138>*
>>
>
>
>
> --
> *Anuruddha Premalal*
> Software Eng. | WSO2 Inc.
> Mobile : +94717213122
> Web site : www.anuruddha.org
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] [PET] Could not pass ftp over http proxy.

2016-03-01 Thread Vivekananthan Sivanayagam

Hi ,

I have implemented a method to support FTP Over proxy in file connector
version 2, I used Java Client [1](commons-net 3.4) and configured "Squid"
proxy[2].

I am getting the following errors when I invoke a method.

[2016-03-02 10:56:19,535] ERROR - FileFtpOverProxy Error occurred while
uploading:Connection is not open
java.io.IOException: Connection is not open
at org.apache.commons.net.ftp.FTP.sendCommand(FTP.java:474)
at org.apache.commons.net.ftp.FTP.sendCommand(FTP.java:608)
at org.apache.commons.net.ftp.FTP.user(FTP.java:753)
at org.apache.commons.net.ftp.FTPClient.login(FTPClient.java:1034)
at
org.wso2.carbon.connector.FileFtpOverProxy.ftpOverHttp(FileFtpOverProxy.java:151)
at
org.wso2.carbon.connector.FileFtpOverProxy.connect(FileFtpOverProxy.java:47)
at
org.wso2.carbon.connector.core.AbstractConnector.mediate(AbstractConnector.java:32)
at
org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:78)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at
org.apache.synapse.mediators.template.TemplateMediator.mediate(TemplateMediator.java:97)
at
org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:129)
at
org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:78)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at
org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:185)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:317)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:363)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

I have attached a FileFtpOverProxy.java here.

[1] https://commons.apache.org/proper/commons-net/
[2] http://www.tecmint.com/configure-squid-server-in-linux/






*Thank youVivekananthan SivanayagamAssociate Software Engineer |
WSO2E:vivekanant...@wso2.com M:+94752786138
<%2B94752786138>*
package org.wso2.carbon.connector;

import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.impl.builder.StAXOMBuilder;
import org.apache.commons.lang.StringUtils;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import org.apache.commons.net.ftp.FTP;
import org.apache.commons.net.ftp.FTPClient;
import org.apache.commons.net.ftp.FTPConnectionClosedException;
import org.apache.commons.net.ftp.FTPHTTPClient;
import org.apache.commons.net.ftp.FTPReply;
import org.apache.synapse.MessageContext;
import org.apache.synapse.commons.json.JsonUtil;
import org.codehaus.jettison.json.JSONException;
import org.wso2.carbon.connector.core.AbstractConnector;
import org.wso2.carbon.connector.core.Connector;
import org.wso2.carbon.connector.core.util.ConnectorUtils;
import org.wso2.carbon.connector.util.FileConstants;
import org.wso2.carbon.connector.util.ResultPayloadCreate;

import javax.xml.stream.XMLStreamException;
import java.io.ByteArrayInputStream;
import java.io.IOException;
import java.io.InputStream;

public class FileFtpOverProxy extends AbstractConnector implements Connector {
private static final Log log = LogFactory.getLog(FileFtpOverProxy.class);

public void connect(MessageContext messageContext) {
String proxyHost = (String) ConnectorUtils.lookupTemplateParamater(messageContext,
FileConstants.PROXY_HOST);
String proxyPort = (String) ConnectorUtils.lookupTemplateParamater(messageContext,
FileConstants.PROXY_PORT);
String proxyUsername = (String) ConnectorUtils.lookupTemplateParamater(messageContext,
FileConstants.PROXY_USERNAME);
String proxyPassword = (String) ConnectorUtils.lookupTemplateParamater
(messageContext, FileConstants.PROXY_PASSWORD);
String ftpServer = (String) ConnectorUtils.lookupTemplateParamater
(messageContext, FileConstants.FTP_SERVER);
String ftpPort = (String) ConnectorUtils.lookupTemplateParamater(messageContext,
FileConstants.FTP_PORT);
String ftpUsername = (String) ConnectorUtils.lookupTemplateParamater(messageContext,
FileConstants.FTP_USERNAME);

Re: [Dev] [PET] Couldn't retrieve the endpoint template

2016-02-18 Thread Vivekananthan Sivanayagam

Hi Malaka ,

As we discussed in the meeting, I've changed the endpoint name as
"org.wso2.carbon.connector.salesforce.salesforceEndPoint" and now it finds
the endpoint template, but the problem is that it shows error like
"EndpointDefinitionFactory Endpoint timeout duration expected as a number
but was not a number".

[1] *salesforceEndPoint Template*


http://ws.apache.org/ns/synapse;>








$initialDuration

$progressionFactor
$maximumDuration


$duration
$responseAction





[2]*called within connector*


   
   
   
   
   



*Error*

ERROR - EndpointDefinitionFactory Endpoint timeout duration expected as a
number but was not a number
[2016-02-19 11:46:33,276]  INFO - LogMediator To:
/services/Salesforce_Create, MessageID:
urn:uuid:eb3880a6-1306-4a28-9906-e1fe43275eaf, Direction: request, MESSAGE
= Executing default 'fault' sequence, ERROR_CODE = 0, ERROR_MESSAGE =
Endpoint timeout duration expected as a number but was not a number,
Payload: {
  "username":"vsvivevi...@gmail.com",
  "password":"XXWeK49TGh8jNfAzBmww9Se97T",
  "loginUrl":"https://login.salesforce.com/services/Soap/u/27.0;,
  "sobject":"Account",
  "initialDuration":2,
  "progressionFactor":1.0,
  "maximumDuration":3000,
  "responseAction":"fault",
  "duration":60
}

On the other hand, I tested with hard coded value in endpoint template[3]
and called it within connector definition, It is working as we expected.

[3] *salesforceEndPoint Template*


http://ws.apache.org/ns/synapse;>








2000
1.0
3000


6
fault








*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Wed, Feb 17, 2016 at 10:07 PM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Hi Malaka,
>
> I debugged [1] and [2], it got deployed.
>
> [1]
> https://github.com/wso2/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/libraries/model/LibraryArtifact.java
>
> [2]
> https://github.com/wso2/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/deployers/LibraryArtifactDeployer.java
>
> I will debug that you mentioned above and update the status.
>
>
>
>
> *Thank youVivekananthan Sivanayagam*
>
> *Associate Software Engineer | WSO2*
>
> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
> *M:+94752786138 <%2B94752786138>*
>
> On Wed, Feb 17, 2016 at 9:35 PM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Vivekananthan try debugging [2] when you enable the connector. May be we
>> need to patch esb for this.
>>
>> Check updateStatus method.
>>
>> [1]
>> https://github.com/wso2/carbon-mediation/blob/master/components/mediation-admin/org.wso2.carbon.mediation.library/src/main/java/org/wso2/carbon/mediation/library/service/MediationLibraryAdminService.java
>>
>> On Wed, Feb 17, 2016 at 6:15 PM, Vivekananthan Sivanayagam <
>> vivekanant...@wso2.com> wrote:
>>
>>> (-) support-dev
>>> (+) dev
>>>
>>>
>>>
>>>
>>> *Thank youVivekananthan Sivanayagam*
>>>
>>> *Associate Software Engineer | WSO2*
>>>
>>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>>> *M:+94752786138 <%2B94752786138>*
>>>
>>> On Wed, Feb 17, 2016 at 6:12 PM, Vivekananthan Sivanayagam <
>>> vivekanant...@wso2.com> wrote:
>>>
>>>> Hi ,
>>>>
>>>> I am working on endpoint templates within the connector definition and
>>>> pass the parameters when calling connector operations.
>>>>
>>>> For that I created endpoint template[1] within connector and called it
>>>> within connector method[2]. When I called, I got these error[3].
>>>> I followed this doc[4]. Any suggestions?
>>>>
>>>> [1] salesforceEndPoint Template
>>>>
>>>> 
>>>> >>> xmlns="http://ws.apache.org/ns/synapse;>
>>>> 
>>>&g

Re: [Dev] [PET] Couldn't retrieve the endpoint template

2016-02-17 Thread Vivekananthan Sivanayagam

Hi Malaka,

I debugged [1] and [2], it got deployed.

[1]
https://github.com/wso2/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/libraries/model/LibraryArtifact.java

[2]
https://github.com/wso2/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/deployers/LibraryArtifactDeployer.java

I will debug that you mentioned above and update the status.




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Wed, Feb 17, 2016 at 9:35 PM, Malaka Silva <mal...@wso2.com> wrote:

> Vivekananthan try debugging [2] when you enable the connector. May be we
> need to patch esb for this.
>
> Check updateStatus method.
>
> [1]
> https://github.com/wso2/carbon-mediation/blob/master/components/mediation-admin/org.wso2.carbon.mediation.library/src/main/java/org/wso2/carbon/mediation/library/service/MediationLibraryAdminService.java
>
> On Wed, Feb 17, 2016 at 6:15 PM, Vivekananthan Sivanayagam <
> vivekanant...@wso2.com> wrote:
>
>> (-) support-dev
>> (+) dev
>>
>>
>>
>>
>> *Thank youVivekananthan Sivanayagam*
>>
>> *Associate Software Engineer | WSO2*
>>
>> *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
>> *M:+94752786138 <%2B94752786138>*
>>
>> On Wed, Feb 17, 2016 at 6:12 PM, Vivekananthan Sivanayagam <
>> vivekanant...@wso2.com> wrote:
>>
>>> Hi ,
>>>
>>> I am working on endpoint templates within the connector definition and
>>> pass the parameters when calling connector operations.
>>>
>>> For that I created endpoint template[1] within connector and called it
>>> within connector method[2]. When I called, I got these error[3].
>>> I followed this doc[4]. Any suggestions?
>>>
>>> [1] salesforceEndPoint Template
>>>
>>> 
>>> http://ws.apache.org/ns/synapse;>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> $initialDuration
>>> 
>>> $progressionFactor
>>> $maximumDuration
>>> 
>>> 
>>> $duration
>>> $responseAction
>>> 
>>> 
>>> 
>>> 
>>>
>>>
>>> [2]*INIT method*
>>>
>>> >>   xmlns="http://ws.apache.org/ns/synapse;>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>
>>> 
>>> >> name="org.wso2.carbon.connector.salesforce.SetupLoginParams"/>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> >> type="property"/>
>>> 
>>> >> name="uri.var.salesforce.url"/>
>>> >> value="urn:partner.soap.sforce.com/Soap/loginRequest"/>
>>> 
>>> 
>>> >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/;
>>>   
>>> xmlns:urn="urn:partner.soap.sforce.com">
>>> 
>>> 
>>> $1
>>> $2
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> >> value="text/xml"/>
>>> 
>>> 
>>> >> action="remove"/>
>>> 
>>>
>>> 
>>> 
>>> >> value="{ctx:salesforce.initialDuration}" />
>

Re: [Dev] [PET] Couldn't retrieve the endpoint template

2016-02-17 Thread Vivekananthan Sivanayagam

(-) support-dev
(+) dev




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>*
*M:+94752786138*

On Wed, Feb 17, 2016 at 6:12 PM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Hi ,
>
> I am working on endpoint templates within the connector definition and
> pass the parameters when calling connector operations.
>
> For that I created endpoint template[1] within connector and called it
> within connector method[2]. When I called, I got these error[3].
> I followed this doc[4]. Any suggestions?
>
> [1] salesforceEndPoint Template
>
> 
> http://ws.apache.org/ns/synapse;>
> 
> 
> 
> 
> 
> 
> 
> 
> $initialDuration
> $progressionFactor
> $maximumDuration
> 
> 
> $duration
> $responseAction
> 
> 
> 
> 
>
>
> [2]*INIT method*
>
>xmlns="http://ws.apache.org/ns/synapse;>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  name="uri.var.salesforce.url"/>
>  value="urn:partner.soap.sforce.com/Soap/loginRequest"/>
> 
> 
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/;
>   
> xmlns:urn="urn:partner.soap.sforce.com">
> 
> 
> $1
> $2
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  action="remove"/>
> 
>
> 
> 
>  value="{ctx:salesforce.initialDuration}" />
>  value="{ctx:salesforce.progressionFactor}" />
>  value="{ctx:salesforce.maximumDuration}" />
>  value="{ctx:salesforce.duration}" />
>  value="{ctx:salesforce.responseAction}" />
> 
> 
>
> 
>  expression="$func:blocking"/>
>  expression="$func:duration"/>
>  expression="$func:progressionFactor"/>
>  expression="$func:maximumDuration"/>
>  expression="$func:duration"/>
>  expression="$func:responseAction"/>
>
>  expression="//ns:loginResponse/ns:result/ns:sessionId/text()"
>   name="salesforce.sessionId" scope="operation" 
> type="STRING"
>   xmlns:ns="urn:partner.soap.sforce.com"/>
>  expression="//ns:loginResponse/ns:result/ns:serverUrl/text()"
>   name="salesforce.serviceUrl" scope="operation" 
> type="STRING"
>   xmlns:ns="urn:partner.soap.sforce.com"/>
>type="STRING" value="true"/>
> 
> 
>  type="property"/>
> 
> 
>  type="property"/>
> 
> 
> 
> 
> 
> 
>
> [3] *Error*
>
> INFO - LogMediator Connection = Login to Salesforce .
> [2016-02-17 17:59:19,164]  WARN - *TemplateEndpoint Couldn't retrieve the
> endpoint template with the key:salesforceEndPoint*
> [2016-02-17 17:59:19,164]  INFO - LogMediator To:
> https://login.salesforce.com/services/Soap/u/27.0, WSAction: urn:
> partner.soap.sforce.com/Soap/login

Re: [Dev] Error Adding File Connector v2 to Developer Studio

2016-01-11 Thread Vivekananthan Sivanayagam

Hi Isuru,

Please find the updated connector in the store[1].

[1]
https://store.wso2.com/store/assets/esbconnector/aec1554a-29ea-4dbb-b8c5-5d529a853aa2

Thanks.




*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com *
*M:+94752786138*

On Mon, Jan 11, 2016 at 5:13 PM, Rajjaz Mohammed  wrote:

> Hi isure,
> yes, error is correct directory name should be
> fileconnector-connector-1.0.0 because file name given as filleconnector so
> according to format ‘name-connector-1.0.0’directory name will come as
> 'fileconnector-connector-2.0.0'. check file connector name[1]
>
> [1]
> https://github.com/wso2/esb-connectors/blob/master/fileconnector/fileconnector-2.0.0/org.wso2.carbon.connector/pom.xml
>
> On Mon, Jan 11, 2016 at 4:45 PM, Isuru Udana  wrote:
>
>> Hi,
>>
>> I am getting following error when importing the File connector ver 2.0 to
>> the ESB Config project.
>>
>> "Connector directory name file-connector-2.0.0 doesn’t match with the
>> connector name fileconnector valid connector should have
>> ‘name-connector-1.0.0’ format"
>>
>> It looks like name mismatch in file name and connector.xml (In
>> connector.xml we have "fileconnector" as the component name).
>>
>> Thanks.
>>
>> --
>> *Isuru Udana*
>> Associate Technical Lead
>> WSO2 Inc.; http://wso2.com
>> email: isu...@wso2.com cell: +94 77 3791887
>> blog: http://mytecheye.blogspot.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thank you
> Best Regards
>
> *Rajjaz HM*
> Associate Software Engineer
> WSO2 Inc. 
> lean | enterprise | middleware
> Mobile | +94752833834
> Email   | raj...@wso2.com
> LinkedIn | Blogger | WSO2 Profile
> 
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Cannot import some connectors to Developer studio.

2015-09-09 Thread Vivekananthan Sivanayagam

Hi Malaka,

It has been uploaded.






*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com *
*M:+94752786138*

On Wed, Sep 9, 2015 at 12:43 PM, Malaka Silva  wrote:

> Hi Viraj,
>
> As we discussed this has not followed the proper structure as other
> connectors. However we can't fix this properly since there are existing
> integration done using the connector.
>
> Will be fixing this in next version. Will discuss more on version aspect
> on architecture mail. [1] will fix the current issue.
>
> @Vivekananthan - pls talk to kathees and build a new version of the
> connector and upload to the store.
>
> [1]
> https://github.com/wso2/esb-connectors/commit/0928fea83c8fa08fa2a3c8a1582b13869e429109
>
> On Wed, Sep 9, 2015 at 10:33 AM, Viraj Rajaguru  wrote:
>
>> Hi Malaka/Elimantha,
>>
>> Issue is with deserialization. To reproduce this issue, we can add a File
>> connector operation in to a sequence or proxy. Then go to the source view
>> and do any change in the source view and switch back to the graphical view.
>> We can see it's not allowing us to switch to the graphical view.
>>
>> Is there any possibility to introduce a new attribute called 'version'
>> into 'component' element in the component.xml to handle multiple version of
>> connectors scenarios without adding the version into name attribute ?
>>
>> We can have a hangout to discuss this.
>>
>> Thanks,
>> Viraj.
>>
>> On Wed, Sep 9, 2015 at 9:03 AM, Elilmatha Sivanesan 
>> wrote:
>>
>>> Hi Malaka
>>>
>>> Yes I have tested file connector, There are no issues now.
>>>
>>> Thank you.
>>>
>>>
>>>
>>> On Wed, Sep 9, 2015 at 7:05 AM, Malaka Silva  wrote:
>>>
 Hi Viraj,

 I tried to reproduce the issue with the latest devs, and it does seems
 to be working fine. May be I missed something.

 Can we have a hangout to discuss this in the morning?

 However we should only focus on component.xml. Reason for that is we
 need to start with multiple version of the connectors.

 eg:-
 linkedin-connector-1.0.0.zip -> 

 linkedin-connector-2.0.0.zip -> >>> "org.wso2.carbon.connector" >

 @Elilmatha I think we tested one by one in [1] with devs? There can't
 be any issues?
 [1] https://wso2.org/jira/browse/ESBCONNECT-63

 On Wed, Sep 9, 2015 at 12:05 AM, Viraj Rajaguru  wrote:

> Hi Connector team,
>
> There is a trivial issue in File connector.
>
> According to the current implementation in DevS, connector needs a
> file name which comply with the 'component name' in the connector.xml. For
> an example "googlecalendar-connector-1.0.0.zip" connector's component name
> should be "googlecalendar" & "linkedin-connector-1.0.0.zip"
> connector's component name should be "linkedin". Almost all the connectors
> follow this rule. But "file-connector-1.0.0.zip" connector's 'component
> name' is "fileconnector". Due to this issue DevS is having issues after
> importing File connector. Can we fix this ?
>
> Thanks,
> Viraj.
>
> On Mon, Jun 1, 2015 at 12:15 PM, Viraj Rajaguru 
> wrote:
>
>> Hi Keerthika,
>>
>> Wordpress connector is working properly now.
>>
>> Thanks,
>> Viraj.
>>
>>
>>
>> On Sun, May 31, 2015 at 10:01 AM, Keerthika Mahendralingam <
>> keerth...@wso2.com> wrote:
>>
>>> Hi Viraj,
>>> Wordpress connector is updated with the correct icons in Connector
>>> store. Please check now.
>>>
>>>
>>> Thanks,
>>>
>>> On Thu, May 28, 2015 at 2:40 PM, Keerthika Mahendralingam <
>>> keerth...@wso2.com> wrote:
>>>
 Will check and let you know.

 On Thu, May 28, 2015 at 2:34 PM, Malaka Silva 
 wrote:

> Connector team,
>
> Please check this.
>
> On Thu, May 28, 2015 at 2:32 PM, Viraj Rajaguru 
> wrote:
>
>> Hi connector team,
>>
>> Following two connectors cannot be imported to Developer Studio
>> due to missing/corrupted icons inside the connector[1]. Can you 
>> please have
>> a look ?
>>
>> 1. You tube connector
>> 2. Wordpress connector
>>
>> Thanks,
>> Viraj.
>>
>> [1] - https://wso2.org/jira/browse/ESBCONNECT-47
>>
>> --
>> Viraj Rajaguru
>> Senior Software Engineer
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 77 3683068
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>

[Dev] Load testing for the File connector

2015-08-11 Thread Vivekananthan Sivanayagam

I need to do the load testing for the operations(decompress file,read
content inside compressed file and add file inside compressed folder) of
the file connector. How can I do that? Any suggestion?





*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com e%3avivekanant...@wso2.com*


*M:+94752786138*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Load test for File Connector

2015-08-11 Thread Vivekananthan Sivanayagam

Hi Malaka,

Thank you.






*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com e%3avivekanant...@wso2.com*
*M:+94752786138*

On Tue, Aug 11, 2015 at 12:01 PM, Malaka Silva mal...@wso2.com wrote:

 You can use soap ui or jmeter for this purpose.

 You can use console for monitoring [2]

 [1] http://www.soapui.org/Getting-Started/load-testing.html
 [2]
 http://docs.oracle.com/javase/6/docs/technotes/guides/management/jconsole.html

 On Tue, Aug 11, 2015 at 11:43 AM, Vivekananthan Sivanayagam 
 vivekanant...@wso2.com wrote:

 Hi,
 I need to do the load testing for the operations(decompress file,read
 content inside compressed file and add file inside compressed folder) of
 the file connector. How can I do that? Any suggestion?






 *Thank youVivekananthan Sivanayagam*

 *Associate Software Engineer | WSO2*

 *E:vivekanant...@wso2.com e%3avivekanant...@wso2.com*
 *M:+94752786138 %2B94752786138*




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print this
 email only if it is absolutely necessary.

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Load test for File Connector

2015-08-11 Thread Vivekananthan Sivanayagam

Hi,
I need to do the load testing for the operations(decompress file,read
content inside compressed file and add file inside compressed folder) of
the file connector. How can I do that? Any suggestion?






*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com e%3avivekanant...@wso2.com*
*M:+94752786138*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Load test for File Connector

2015-08-11 Thread Vivekananthan Sivanayagam

Hi Viraj,

Thank you







*Thank youVivekananthan Sivanayagam*

*Associate Software Engineer | WSO2*

*E:vivekanant...@wso2.com e%3avivekanant...@wso2.com*
*M:+94752786138*

On Tue, Aug 11, 2015 at 8:17 PM, Viraj Senevirathne vir...@wso2.com wrote:

 hi Vivek,

 This is a nice tutorial [1] about jmeter which I used to learn jmeter.
 Hope this help you too.

 [1] http://www.guru99.com/jmeter-performance-testing.html

 Thanks,

 On Tue, Aug 11, 2015 at 12:07 PM, Vivekananthan Sivanayagam 
 vivekanant...@wso2.com wrote:

 Hi Malaka,

 Thank you.






 *Thank youVivekananthan Sivanayagam*

 *Associate Software Engineer | WSO2*

 *E:vivekanant...@wso2.com e%3avivekanant...@wso2.com*
 *M:+94752786138 %2B94752786138*

 On Tue, Aug 11, 2015 at 12:01 PM, Malaka Silva mal...@wso2.com wrote:

 You can use soap ui or jmeter for this purpose.

 You can use console for monitoring [2]

 [1] http://www.soapui.org/Getting-Started/load-testing.html
 [2]
 http://docs.oracle.com/javase/6/docs/technotes/guides/management/jconsole.html

 On Tue, Aug 11, 2015 at 11:43 AM, Vivekananthan Sivanayagam 
 vivekanant...@wso2.com wrote:

 Hi,
 I need to do the load testing for the operations(decompress file,read
 content inside compressed file and add file inside compressed folder) of
 the file connector. How can I do that? Any suggestion?






 *Thank youVivekananthan Sivanayagam*

 *Associate Software Engineer | WSO2*

 *E:vivekanant...@wso2.com e%3avivekanant...@wso2.com*
 *M:+94752786138 %2B94752786138*




 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 http://wso2.com/about/team/malaka-silva/

 Save a tree -Conserve nature  Save the world for your future. Print
 this email only if it is absolutely necessary.



 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Viraj Senevirathne
 Software Engineer; WSO2, Inc.

 Mobile : +94 71 818 4742 %2B94%20%280%29%20773%20451194
 Email : vir...@wso2.com thili...@wso2.com

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

56 matches

Mail list logo